io.github.fantasyce/agent-runtime-proof
Agent Runtime Proof
Is the Agent Runtime Proof MCP server down? Yes. It has given no valid answer since 2026-10-30: not found.
Verify whether a local Agent or MCP runtime matches an approved artifact.
not found down since 2026-10-30 · probed 2026-11-14 · unchanged since 2026-11-06
command not found: server/agent-runtime-proof-linux-amd64
- Bundle
- https://github.com/fantasyce/agent-runtime-proof/releases/download/v1.1.0/agent-runtime-proof_1.1.0.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/fantasyce/agent-runtime-proof
- Website
- https://fantasyce.github.io/agent-runtime-proof/
- Registry
- active, updated 2026-08-27 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- Jev Decision Gate by BPJ io.github.f-tiger/jev-decision-gate · crashed on start
- TradeCheck Local Invoice Review io.github.f-tiger/tradecheck · alive
- Agent Recall Trail io.github.fantasyce/agent-recall-trail · not found
- Agent Residue Evidence io.github.fantasyce/agent-residue-evidence · not found
- io.github.farmmer938-lgtm/af-databridge · alive
- io.github.farssaadeldin7-ux/code-to-visual-interpreter · alive
- io.github.farssaadeldin7-ux/customer-sales-support · alive
- io.github.farssaadeldin7-ux/diagnose-by-sound · alive
Servers that mention runtime.
- ai.boundaryai/boundaryai · needs auth
- Clawfight ai.clawfight/mcp · alive
- ai.kanonik/kanonik · needs auth
- ai.orgsdk/mcp · no DNS
- runx ai.runx/runx · alive
- ai.sealgate/gateway · needs auth
- ai.smithery/flight505-mcp_dincoder · not found
- 6DuckLearn MCP com.6ducklearn/mcp · 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
- No valid answer since 2026-10-30, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.