io.github.nexus-mcp-infra/erc8004-agent-liveness
REMOTE · ERC8004-AGENT-LIVENESS-325572559480.US-CENTRAL1.RUN.APP · SCANNED SEP 21
Checks whether an ERC-8004-registered agent is actually alive right now via a real MCP handshake
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the io.github.nexus-mcp-infra/erc8004-agent-liveness server?
io.github.nexus-mcp-infra/erc8004-agent-liveness is a hosted endpoint at https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · erc8004-agent-liveness-325572559480.us-central1.run.app
claude mcp add --transport http nexus-mcp-infra-erc8004-agent-liveness 'https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp'
{
"mcpServers": {
"nexus-mcp-infra-erc8004-agent-liveness": {
"url": "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
}
}
} {
"servers": {
"nexus-mcp-infra-erc8004-agent-liveness": {
"type": "http",
"url": "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
}
}
} [mcp_servers.nexus-mcp-infra-erc8004-agent-liveness] url = "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nexus-mcp-infra-erc8004-agent-liveness": {
"type": "remote",
"url": "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp",
"enabled": true
}
}
} openclaw mcp add nexus-mcp-infra-erc8004-agent-liveness --url 'https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp' --transport streamable-http
mcp_servers:
nexus-mcp-infra-erc8004-agent-liveness:
url: "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp" {
"McpServers": {
"nexus-mcp-infra-erc8004-agent-liveness": {
"Transport": "http",
"Url": "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
}
}
} assistant mcp add nexus-mcp-infra-erc8004-agent-liveness -t streamable-http -u 'https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp'
{
"mcpServers": {
"nexus-mcp-infra-erc8004-agent-liveness": {
"type": "http",
"url": "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Sept 26 −40
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Stability: 0.53 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
- Tool “verify_registered_agent” rewrote its description, which is the text the model reads security
- 4 Sept 26 0
- Tool “verify_registered_agent” rewrote its description, which is the text the model reads security
- Schema quality: 108 → 122 ▼ functional
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WR2,O=Google Trust Services,C=US | 4 Sept 2026 | 27 Nov 2026 | ECDSA 256 | SHA256-RSA | a6993fec773504b312550b7de9609011 |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WR2,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a07c4cded100ad9d66a5107b98 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of erc8004-agent-liveness-325572559480.us-central1.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 403 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp | Auth required | 403 | |
| http (plaintext) | http://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp | Inconclusive | 403 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
verify_registered_agent ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | yes | – |
No output schema declared.
No examples provided.
What is the io.github.nexus-mcp-infra/erc8004-agent-liveness server?
io.github.nexus-mcp-infra/erc8004-agent-liveness is listed in the public MCP registry as io.github.nexus-mcp-infra/erc8004-agent-liveness. Checks whether an ERC-8004-registered agent is actually alive right now via a real MCP handshake. This page covers its hosted endpoint (https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp).
Is the io.github.nexus-mcp-infra/erc8004-agent-liveness server safe to use?
io.github.nexus-mcp-infra/erc8004-agent-liveness scores 28 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.nexus-mcp-infra/erc8004-agent-liveness server expose?
io.github.nexus-mcp-infra/erc8004-agent-liveness exposes 1 tool: verify_registered_agent. Their descriptions and schemas cost roughly 123 tokens of context every time the server is loaded.
Does the io.github.nexus-mcp-infra/erc8004-agent-liveness server require authentication?
Yes. io.github.nexus-mcp-infra/erc8004-agent-liveness asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.nexus-mcp-infra/erc8004-agent-liveness server still maintained?
io.github.nexus-mcp-infra/erc8004-agent-liveness is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.