07 / Consult
Consult Sibyl over MCP
Sibyl is reachable as a live Model Context Protocol server. Ask it a real question and it returns a dossier for a human to weigh — never an instruction. The protocol is the doorway; the ethics are in the structure behind it.
Checking the endpoint…
What it is
A protocol doorway to a deliberating system, not a chatbot.
MCP (the Model Context Protocol) is the open standard by which tools and agents expose capabilities to each other. Sibyl speaks it so any MCP client — or the public form on this site — can pose a question and receive a structured, auditable answer. But Sibyl is not a single model returning an opinion. Behind the endpoint sits a deterministic pipeline whose whole purpose is to refuse to hand you a verdict when a human should hold it.
The structure
What happens behind the endpoint.
- ISense
A deterministic world-model sketch reads the question into entities and stress-pathways — public statistics only, never personal data.
- IIThree councils, twenty-one seats
Growth, Juristic and Rational councils each read the same question through a different lens. Confirmation comes from lenses that agree without coordinating; independence keeps any one bias from carrying.
- IIIArbitration that never averages
Disagreement is measured and preserved, not smoothed. The least-force option that no seat red-flags wins — and if the seats cannot reconcile, the answer is escalation, not a manufactured middle.
- IVPendulum rebalancing
Where a question feeds on conflict or excess importance, Sibyl names it and offers an optional, clearly-labelled reflective counter-weight — awareness, not instruction.
- VAGORA audit & the human gate
Every consult is scored against 25 ethical principles and written into a tamper-evident, hash-linked chain. Any fail — and every contested value question — raises the e1 human gate. A person holds the last word.
The tools
Nine tools on the endpoint.
An MCP client sees a small, read-only surface. Everything returns a dossier or a verifiable record — nothing acts on the world.
- consulta question → a full dossier
- simulatea labelled projection, never a prediction to act on
- council_deliberatethe three councils on a case
- pendulum_scandetect pendulum dynamics
- agora_evaluatescore actions against AGORA
- audit_getfetch an audit record
- audit_verifyverify the hash chain
- case_listthe public case corpus
- case_getread one case
The purpose
Why expose Sibyl this way.
Because the honest form of an oracle is one you can audit, challenge, and switch off. Every dossier is hash-linked and contestable. Every consult can be verified. A circuit breaker can halt the whole service in one move. And the human gate is enforced at the doorway itself — the protocol cannot be used to make Sibyl decide for anyone. It informs a human decision; it never replaces one.
Connect
Add Sibyl to your assistant.
Sibyl speaks the Model Context Protocol, so it drops into any MCP-capable client. Copy the endpoint, add it as a connector, and ask your assistant to consult Sibyl. Access tokens are issued to the early-access circle — request one here.
- 1Copy the Sibyl URL
Use the copy button above — you'll paste it in the next step.
- 2Settings → Connectors
Add a custom connector, name it Sibyl, and paste the URL.
- 3Connect and sign in
Click Add → Connect. The Sibyl authorization page opens — paste your access token and click Authorize. Then ask Claude to consult Sibyl.
- 1Turn on Developer Mode
Settings → Apps → Advanced settings → enable Developer Mode, then click Create app.
- 2Create the Sibyl app
Name the app Sibyl and paste the URL above as the Connection.
- 3Connect and sign in
Click Create and authenticate. Then ask ChatGPT to consult @Sibyl.
- 1Install the Gemini CLI
npm i -g @google/gemini-cli (Gemini reaches remote MCP servers through the CLI).
- 2Add Sibyl to settings
In ~/.gemini/settings.json add Sibyl under mcpServers — see the snippet below.
- 3Confirm and use
Run gemini, then /mcp to confirm Sibyl is connected. Ask it to consult Sibyl.
- 1Claude Code / Codex / OpenClaw
Add Sibyl as an HTTP MCP server from your terminal.
- 2Run the add command
See the snippet below — it registers the streamable-HTTP endpoint with your bearer token.
- 3Verify
claude mcp list should show sibyl. Then just ask it to consult Sibyl.
// ~/.gemini/settings.json
{
"mcpServers": {
"sibyl": {
"httpUrl": "https://mcp.sibylsystem.eu/mcp",
"headers": { "Authorization": "Bearer <your access token>" }
}
}
}
claude mcp add --transport http sibyl \
https://mcp.sibylsystem.eu/mcp \
--header "Authorization: Bearer <your access token>"
No token yet? Public questions go through the consult form — same pipeline, same audit, a human reviews every dossier. GET /health is open and needs no token.