# io.github.nexus-mcp-infra/erc8004-agent-liveness (remote · erc8004-agent-liveness-325572559480.us-central1.run.app)

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

- Trust score: 28/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `erc8004-agent-liveness-325572559480.us-central1.run.app`: 28/100 (this document), [markdown](https://verifymcp.io/servers/nexus-mcp-infra-erc8004-agent-liveness/erc8004-agent-liveness-325572559480.md), [page](https://verifymcp.io/servers/nexus-mcp-infra-erc8004-agent-liveness/erc8004-agent-liveness-325572559480)

## Channel facts

- Endpoint: `https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http nexus-mcp-infra-erc8004-agent-liveness 'https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nexus-mcp-infra-erc8004-agent-liveness": {
      "url": "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nexus-mcp-infra-erc8004-agent-liveness": {
      "type": "http",
      "url": "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nexus-mcp-infra-erc8004-agent-liveness]
url = "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add nexus-mcp-infra-erc8004-agent-liveness --url 'https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nexus-mcp-infra-erc8004-agent-liveness:
    url: "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nexus-mcp-infra-erc8004-agent-liveness": {
      "Transport": "http",
      "Url": "https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nexus-mcp-infra-erc8004-agent-liveness -t streamable-http -u 'https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-09 (score 28, −40)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Authorization: unverified → fail
- [security regression] Stability: 0.53 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Transport: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-07 (score 68, +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.

### 2026-09-05 (score 67, +1)

- [security] Tool “verify_registered_agent” rewrote its description, which is the text the model reads

### 2026-09-04 (score 66, 0)

- [security] Tool “verify_registered_agent” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 108 → 122

### 2026-09-03 (score 66, +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.

### 2026-09-01 (score 65, +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.

### 2026-08-30 (score 64, +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.

### 2026-08-28 (score 63, +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.

## MCP tools (1)

### `verify_registered_agent` (~123 tokens)

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.

Input parameters:

- `agent_id` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nexus-mcp-infra-erc8004-agent-liveness/erc8004-agent-liveness-325572559480#diagnostics

## Score history

- 2026-09-21: 28
- 2026-09-20: 28
- 2026-09-19: 28
- 2026-09-18: 28
- 2026-09-17: 28
- 2026-09-16: 28
- 2026-09-15: 28
- 2026-09-14: 28
- 2026-09-13: 28
- 2026-09-12: 28
- 2026-09-11: 28
- 2026-09-10: 28
- 2026-09-09: 28
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 66
- 2026-09-03: 66
- 2026-09-02: 65
- 2026-09-01: 65
- 2026-08-31: 64
- 2026-08-30: 64
- 2026-08-29: 63
- 2026-08-28: 63
- 2026-08-27: 62
- 2026-08-26: 62
- 2026-08-25: 59
- 2026-08-24: 59
- 2026-08-23: 58

## Common questions

### 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.

## Links

- Remote endpoint: https://erc8004-agent-liveness-325572559480.us-central1.run.app/mcp
- Repository: https://github.com/nexus-mcp-infra/erc8004-agent-liveness
- Changelog RSS feed: https://verifymcp.io/servers/nexus-mcp-infra-erc8004-agent-liveness/erc8004-agent-liveness-325572559480.xml
- Changelog JSON feed: https://verifymcp.io/servers/nexus-mcp-infra-erc8004-agent-liveness/erc8004-agent-liveness-325572559480.json
- HTML version of this page: https://verifymcp.io/servers/nexus-mcp-infra-erc8004-agent-liveness/erc8004-agent-liveness-325572559480