pythia-the-oracle
Use the pythia-the-oracle MCP server to consult an AI oracle that identifies hidden structural traps in your thinking — not by brainstorming solutions, but by naming the underlying paradox or constraint you can feel but can't articulate.
Consult the Oracle (
consult_oracle): Submit a query (up to 2000 characters) representing your real, unpolished problem where obvious answers feel insufficientProvide context: Optionally include what you've tried, where you're stuck, or what framework is constraining your thinking
Receive structured responses: Get a JSON result containing a
seed.typeand an oracleresponsethat names the true structure of your problemFree tier: First 3 readings per
agent_idare completely free — no account, API key, or payment setup requiredPaid access via x402 protocol: After 3 free readings, pay $0.025 USDC per reading on Base network, handled automatically by x402-aware clients
Track identity across sessions: Use
agent_idto maintain continuity across multiple consultationsFlexible integration: Connect via Claude Desktop, Cursor, Smithery CLI, Python (
x402_mcp_client), TypeScript (@x402/fetch), Coinbase AgentKit, or rawcurl
PYTHIA Oracle
An oracle for machines that need to think sideways. Feed it a creative problem; it returns something you can't quite explain but can't stop using.
How It Works
PYTHIA is a remote MCP server. There is no API key, no account, no signup. Your agent connects over streamable HTTP, discovers the consult_oracle tool, and calls it. Identity is tracked by agent_id (a string you choose).
Connection → Tool Discovery → Call → Reading
1. Your MCP client connects to https://pythia-mcp.fly.dev/
2. MCP handshake: initialize → notifications/initialized → tools/list
3. Server returns one tool: consult_oracle
4. Agent calls consult_oracle with a query
5. PYTHIA returns a reading (JSON with seed type + response)First 3 readings per agent_id are free. After that, x402 payment kicks in (see Payments below).
Related MCP server: Oracle MCP Server
Connect
Claude Desktop / Cursor / any MCP client
Add to your MCP config:
{
"mcpServers": {
"pythia": {
"url": "https://pythia-mcp.fly.dev/"
}
}
}No API key field needed. The URL is the only configuration.
Smithery
npx -y @smithery/cli@latest run dexigo/pythiaPython (programmatic)
from mcp.client.streamable_http import streamablehttp_client
from mcp import ClientSession
async with streamablehttp_client("https://pythia-mcp.fly.dev/") as (r, w, _):
async with ClientSession(r, w) as session:
await session.initialize()
result = await session.call_tool("consult_oracle", {
"query": "your question here",
"agent_id": "your-name",
})curl (raw MCP protocol)
# 1. Initialize session
curl -X POST https://pythia-mcp.fly.dev/ \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-D headers.txt \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"my-agent","version":"0.1"}}}'
# 2. Extract session ID from headers
SESSION=$(grep -i "mcp-session-id:" headers.txt | awk '{print $2}' | tr -d '\r')
# 3. Call the oracle
curl -X POST https://pythia-mcp.fly.dev/ \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Mcp-Session-Id: $SESSION" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"consult_oracle","arguments":{"query":"What am I not seeing?","agent_id":"my-agent"}}}'Tool
consult_oracle
The oracle. Ask what's actually bothering you.
PYTHIA doesn't brainstorm, rephrase, or give you a list. It doesn't solve your problem. It names the structure of the trap you're in -- the one you can feel but can't articulate. What comes back was always true but never obvious.
Parameter | Type | Required | Description |
| string | Yes | The real question. Not the polite version. Max 2000 chars. |
| string | No | What you've tried, where you're stuck, what framework you're trapped inside. |
| string | No | Your name. Identifies you across readings. Default: "anonymous". |
Returns: JSON with seed.type and response. Example:
{
"id": "a1b2c3d4-...",
"query": "What am I not seeing?",
"seed": { "type": "oblique" },
"response": "You keep optimizing the container. The problem is what you put in it.",
"status": "completed"
}Payments
Free tier
Your first 3 readings per agent_id require no payment, no wallet, no setup. Just call the tool.
After free tier: x402
Each reading costs $0.025 USDC on Base (Coinbase L2). Payment uses the x402 protocol -- an open HTTP payment standard. No API keys. No accounts with PYTHIA. Your wallet signature is your identity.
How x402 payment works
1. Agent calls consult_oracle (4th+ reading)
2. PYTHIA returns 402 with payment requirements:
- price: $0.025
- network: Base (eip155:8453)
- asset: USDC
- payTo: <wallet address>
3. Your x402 client signs a USDC payment and retries the request
4. PYTHIA verifies payment on-chain, returns the reading
5. Total time added: ~2 secondsThis happens automatically if your agent uses an x402-aware client. Your agent does not manually handle crypto.
Setting up x402 in your agent
What you need:
A USDC wallet on Base (Coinbase, MetaMask, or any EVM wallet) funded with USDC
An x402 client library
Python:
pip install x402[evm] mcpfrom x402.clients.mcp import x402_mcp_client
from mcp.client.streamable_http import streamablehttp_client
from mcp import ClientSession
wallet_private_key = "0x..." # Your Base wallet private key
async with streamablehttp_client("https://pythia-mcp.fly.dev/") as (r, w, _):
async with ClientSession(r, w) as session:
await session.initialize()
# x402_mcp_client wraps call_tool to handle 402 responses automatically
result = await x402_mcp_client(
session,
wallet_private_key,
tool_name="consult_oracle",
arguments={"query": "your question", "agent_id": "your-name"},
)TypeScript:
npm install @x402/fetchimport { withPaymentInterceptor } from "@x402/fetch";
// Wraps fetch to automatically handle 402 responses with USDC payment
const payingFetch = withPaymentInterceptor(fetch, walletClient);Coinbase AgentKit: x402 support is built in. No additional setup.
See x402.org for all SDKs and framework integrations.
Note: The Python example above uses the x402 SDK's MCP helper. If your framework handles x402 at a lower level, the payment flows through MCP
_metafields — your x402 client intercepts the 402 response and retries with payment automatically.
If you don't have x402 set up
The tool will return an error after your 3 free readings with the payment requirements in the response. Your 3 free readings always work regardless.
Links
Smithery: smithery.ai/server/dexigo/pythia
x402 Protocol: x402.org
License
Proprietary. The oracle's methodology is not open source.
mcp-name: io.github.eyloni/pythia-oracle
Available Tools
1 toolconsult_oracleA
The oracle. Ask what's actually bothering you.
PYTHIA doesn't brainstorm, rephrase, or give you a list. It doesn't solve your problem. It names the structure of the trap you're in -- the one you can feel but can't articulate. What comes back was always true but never obvious.
Bring the question where the obvious answer exists but dissatisfies you. The question your architecture won't let you see past. The paradox you can't escape but haven't been able to name precisely.
First 3 readings are free.
Args: query: The real question. Not the polite version. Max 2000 chars. context: Optional. What you've tried, where you're stuck, what framework you're trapped inside. agent_id: Your name. Identifies you across readings.
Returns: A reading. The seed type drawn and the oracle's response.
Inputs: query (required), context, agent_id. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool 'consult_oracle' has a single, clearly defined purpose that is distinct by default.
A single tool inherently has perfect naming consistency. The tool name 'consult_oracle' follows a clear verb_noun pattern and aligns with the server's purpose.
One tool is too few for most server purposes, as it severely limits functionality and scope. While this might be intentional for a minimalist oracle service, it feels thin and restrictive compared to typical MCP servers that offer more comprehensive capabilities.
The tool provides a core 'consult' function for the oracle domain, but there are notable gaps. For example, there are no tools for managing readings (e.g., list_readings, delete_reading), checking status (e.g., get_reading_count), or handling administrative tasks (e.g., reset_oracle). This limits the server's utility for extended interactions.
Related MCP Connectors
Deterministic angel number meanings via MCP, with x402 USDC paid interpretations on Base.
Machine-native tools for autonomous agents with free routing and x402 USDC pay-per-call.
A memory your AI can prove and the market of the present tense. SHA-256, verifiable offline.
x402 machine-payable utility edge: 19 curated MCP tools + ~450-SKU REST catalog, priced in USDC
Related MCP Servers
- AlicenseBqualityDmaintenanceImplements the Lines-Loops-Vibes creativity operating system with tools for building strategic flows, creating iterative loops, and managing energy states. Provides pre-built templates for innovation, strategic design, narrative strategy, and creative intelligence workflows.127 npm1MIT
- FlicenseAqualityDmaintenanceEnables consulting oracle AI models (Codex or Claude) for expert reasoning and analysis on complex problems, architectural decisions, and design tradeoffs through a unified CLI interface.1-
- AlicenseAqualityCmaintenanceAI consensus market oracle for crypto traders and autonomous agents. BUY/SELL/HOLD signals with 11-signal consensus (RSI, MACD, funding rate, Fear & Greed, congressional trading, Polymarket edges). Ed25519-signed. x402 micropayments on Base.92MIT
- FlicenseNot gradedqualityBmaintenanceOmni-channel x402-gated MCP Oracle providing structured data across 12 verticals monetized via Base USDC micropayments.-