io.github.LembaGang/headless-oracle-mcp
headless-oracle
Is the io.github.LembaGang/headless-oracle-mcp MCP server down? No. It is up and needs network, probed 2026-10-27.
Ed25519-signed market-state receipts for 28 exchanges. Fail-closed pre-trade gate.
needs network probed 2026-11-15 · unchanged since 2026-10-27
MCP error -32603: Headless Oracle remote error: getaddrinfo EAI_AGAIN headlessoracle.com [headless-oracle-mcp] Remote error: getaddrinfo EAI_AGAIN headlessoracl
- Run it
- npx -y headless-oracle-mcp@1.0.3 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- headless-oracle 1.0.0
- Capabilities
- tools
- Repository
- https://github.com/LembaGang/headless-oracle-v5
- Registry
- active, updated 2026-04-05 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.LeandroPG19/cuba-memorys · crashed on start
- io.github.LeandroPG19/memory-industry · crashed on start
- io.github.LeassTaTT/servicenow-mcp-ai · alive
- Korea MCP io.github.Leegwangwoon/korea-mcp · alive
- io.github.Leonardo-Engineering/davincibets-mcp · needs env
- NeuroFlow MCP io.github.LeonardoCesca/neuroflow-mcp · crashed on start
- io.github.Leonhest/hivemind · alive
- io.github.LeonTing1010/haplane · crashed on start
Servers that mention headless.
- Crane Ledger ai.craneledger/crane-ledger · needs auth
- ai.uxbert/cms · needs auth
- shelf-smoke — url smoke / headless QA co.kymac.shelf/shelf-smoke · no DNS
- Dataddo Data to AI com.dataddo/mcp-data · needs auth
- com.makespdf/makespdf · alive
- WingmanProtocol Agent Gateway com.wingmanprotocol.agent/gateway · alive
- Ichabod dev.ichabod/ichabod · not found
- pendnt dev.pendnt/pendnt · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.