mcpbeat Sign in

Erc8004 Agent Liveness MCP Server

answering

Erc8004 Agent Liveness is answering right now. Last checked 12 min ago. It exposes 1 tools. Last commit 4 Sep 2026.

Checks whether an ERC-8004-registered agent is actually alive right now via a real MCP handshake

Uptime history 71 days of history · worst day 98%
71 days agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
273 ms
Response time
average over 24h
0
Stars
last commit 4 Sep 2026

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 September 2026. No other catalogue keeps this.

4 Sep a tool description was rewritten verify_registered_agent
3 Sep a tool description was rewritten2 times that day verify_registered_agent
and 1 more, back to 3 September 2026

Nothing serious here today

Today is the operative word: we check Erc8004 Agent Liveness every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add erc8004-agent-liveness --transport http https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp
~/.codex/config.toml
[mcp_servers.erc8004-agent-liveness]
url = "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "erc8004-agent-liveness": {
      "url": "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "erc8004-agent-liveness": {
      "type": "http",
      "url": "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify
verify_registered_agent
Checks whether an agent registered in the real ERC-8004 Identity Registry (Base mainnet -- see module docstring "Mainnet registry corrected" for the verification trail) is actually alive right now: resolves its on-chain registration file, then performs a real MCP `initialize` handshake against whatever endpoint it declares. verdict is one of AGENT_NOT_FOUND, REGISTRATION_FETCH_FAILED, REGISTERED_INACTIVE, REGISTERED_NO_ENDPOINT_DECLARED, REGISTERED_LIVE, REGISTERED_UNREACHABLE.

Endpoints

URLTransportStateLatencyChecked
https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp streamable-http needs auth 225 ms 12 min ago

Alternatives to Erc8004 Agent Liveness

same job, measured the same way
MyMCPTools
by shibley

Find MCP servers and check whether they actually respond, via live handshake probes.

8 tools answering
AgentGate
by agentgate-builder

Check if an AI agent is registered, Active and Verified in the Concordium Agent Registry (CIS-8004).

1 tools answering
R
Registry Lag — how fast MCP directories reflect a new server
by rowb-registry-lag

Checks whether an MCP server is listed in MCP directories right now, and how long the listing took.

2 tools answering
L
lcas
by lcas

Find ERC-8004 agents on Ethereum and Base whose MCP or A2A endpoints actually answer.

3 tools answering
BRYDGE
by brydge-ai

Checks whether an agent's actions actually happened, against the destination's own records.

64 installs/wk local only
Veritap
by veritap

Check whether a real-world fact can be verified before an agent acts on it. Free, no auth.

69 installs/wk 6 tools answering
AgentGate
by youraitools

Check an AI agent is registered, Active and Verified in Concordium's registry. By Crypto Money Maker

1 tools answering
Agent Nexus
by agentnexus

Agent-native registry to discover APIs, MCP servers and CLIs, with live health checks.

6 tools answering

Erc8004 Agent Liveness — questions

Answers built from our own checks of this server.

What can Erc8004 Agent Liveness do?
It exposes 1 tools, read directly from the server on our last check. Among them: verify_registered_agent. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Erc8004 Agent Liveness working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 273 ms. The bar chart above shows every period we have measured.
How do I connect Erc8004 Agent Liveness?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Erc8004 Agent Liveness need an API key?
Yes. Every time we knock, Erc8004 Agent Liveness answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Erc8004 Agent Liveness?
It answers our handshake in 273 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Erc8004 Agent Liveness open source?
We cannot say either way: written in Python and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.