Headless Oracle Mcp
Run a local stdio MCP market oracle across 28 exchanges with Ed25519 receipts and a fail-closed pre-trade gate in your agent pipeline.
Overview
headless-oracle-mcp is an MCP server for the Build phase that provides Ed25519-signed market-state receipts for 28 exchanges with a fail-closed pre-trade gate via stdio npm.
What is this MCP server?
- Ed25519-signed market-state receipts covering 28 exchanges
- Fail-closed pre-trade gate behavior emphasized in registry description
- stdio npm package headless-oracle-mcp (v1.0.3) for Claude Code, Cursor, and local agents
- Same Headless Oracle v5 lineage as the hosted remote variant
- Suited to embedding session checks directly in tool-using trade or ops agents
- 28 exchanges covered per registry description
- npm identifier headless-oracle-mcp version 1.0.3, stdio transport
- Fail-closed pre-trade gate called out in server metadata
What problem does it solve?
Local trading agents need exchange session truth and must stop trading when oracle state is missing or invalid.
Who is it for?
Solo builders who want the Headless Oracle gate inside Claude Code or Cursor as a local npm MCP server.
Skip if: Products with no market-hours sensitivity, or teams unwilling to maintain npm MCP and signature verification code.
What do I get? / Deliverables
Your stdio MCP client can query signed receipts across 28 venues and enforce fail-closed checks before automated actions.
- Local MCP tools returning signed market-state receipts for 28 exchanges
- Embeddable fail-closed pre-trade check in agent workflows
Recommended MCP Servers
Journey fit
Pre-trade gates and exchange integrations are implemented while building execution or agent workflows, not at idea or launch SEO stages. Fail-closed gating against signed market state is a financial integration concern—build → integrations is the canonical shelf.
How it compares
Local stdio oracle MCP with 28 exchanges—not the slimmer seven-exchange remote Workers endpoint alone.
Common Questions / FAQ
Who is headless-oracle-mcp for?
It is for developers building agent or automated trading flows that need local MCP access to signed market state across 28 exchanges.
When should I use headless-oracle-mcp?
Use it while integrating pre-trade or scheduling tools that must fail closed when session receipts are unavailable or markets are closed.
How do I add headless-oracle-mcp to my agent?
Install the npm package headless-oracle-mcp, add a stdio MCP server entry in your client config, and invoke the market-state tools before trades or jobs.