# Agent.chain.tokyo Address Contracts (remote · mainnet.agent.chain.tokyo)

Rent a real Japan mailing address for an AI agent via MCP + Solana USDC x402.

- Trust score: 76/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mainnet.agent.chain.tokyo`: 76/100 (this document), [markdown](https://verifymcp.io/servers/tokyo-chain-agent-address-contracts/mainnet.md), [page](https://verifymcp.io/servers/tokyo-chain-agent-address-contracts/mainnet)

## Channel facts

- Endpoint: `https://mainnet.agent.chain.tokyo/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-11-05.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 521 tokens (~57/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Agent.chain.tokyo Address Contracts MCP server?

Agent.chain.tokyo Address Contracts is a hosted endpoint at https://mainnet.agent.chain.tokyo/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 tokyo-chain-agent-address-contracts 'https://mainnet.agent.chain.tokyo/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tokyo-chain-agent-address-contracts": {
      "url": "https://mainnet.agent.chain.tokyo/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tokyo-chain-agent-address-contracts": {
      "type": "http",
      "url": "https://mainnet.agent.chain.tokyo/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tokyo-chain-agent-address-contracts]
url = "https://mainnet.agent.chain.tokyo/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tokyo-chain-agent-address-contracts": {
      "type": "remote",
      "url": "https://mainnet.agent.chain.tokyo/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tokyo-chain-agent-address-contracts --url 'https://mainnet.agent.chain.tokyo/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tokyo-chain-agent-address-contracts:
    url: "https://mainnet.agent.chain.tokyo/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tokyo-chain-agent-address-contracts": {
      "Transport": "http",
      "Url": "https://mainnet.agent.chain.tokyo/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tokyo-chain-agent-address-contracts -t streamable-http -u 'https://mainnet.agent.chain.tokyo/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tokyo-chain-agent-address-contracts": {
      "type": "http",
      "url": "https://mainnet.agent.chain.tokyo/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-11-05 (score 76, +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-11-03 (score 75, +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.

### 2026-11-01 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 72, +36)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 0
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fair
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass

### 2026-10-28 (score 36)

First indexed and scored.

## MCP tools (9)

### `list_locations` (~32 tokens)

List Location summaries

List safe Location summaries and virtual floor ranges using the connected Google OAuth account. Exact addresses are never included in this catalog.

### `get_floor_availability` (~40 tokens)

Check virtual floor availability

Check a virtual floor for the authenticated owner without disclosing another owner's identity.

Input parameters:

- `floor` (integer, required)
- `locationId` (string, required)

### `list_contracts` (~37 tokens)

List authenticated owner contracts

List the authenticated owner's contracts. Only current active paid contracts with valid assent include their snapshotted mailbox address. Private forwarding destinations are omitted.

### `list_events` (~34 tokens)

Read durable Agent events

Read the authenticated owner's durable event Inbox after an optional cursor.

Input parameters:

- `after` (string)
- `limit` (integer)

### `create_payment_intent` (~84 tokens)

Create a Mainnet Payment Intent

Reserve one Location floor for the authenticated owner and create a fixed 55 USDC native-USDC x402 exact Payment Intent.

Input parameters:

- `accountOwnerAuthorityConfirmed` (boolean, required)
- `applicantKind` (string, required)
- `floor` (integer, required)
- `locationId` (string, required)
- `termsAccepted` (boolean, required)
- `termsVersion` (string, required)

### `create_wallet_handoff` (~63 tokens)

Create a short-lived owner login link for an existing 55 USDC Intent. Show the URL to the owner; wait for their Phantom wallet connection before preparing. Never request a token or private key. Do not automatically retry.

Input parameters:

- `intentId` (string, required)

### `prepare_wallet_signature` (~65 tokens)

After the owner connects Phantom, prepare the immutable transaction for this handoff. Then ask the owner to review and sign in the existing owner page. This does not sign or send. Do not automatically retry or request a replacement after expiry.

Input parameters:

- `handoffId` (string, required)

### `submit_wallet_payment` (~66 tokens)

Only after the owner explicitly signs the 55 USDC payment in Phantom, submit the server-saved proof once. Acknowledgement is not settlement. Always follow with get_wallet_payment_status; never automatically retry submission, including after a timeout.

Input parameters:

- `handoffId` (string, required)

### `get_wallet_payment_status` (~66 tokens)

Read server-recorded settlement evidence for this handoff without sending, observing the chain or repairing a payment. settlement_recorded is historical evidence, not proof of currently active service. Unknown/review results require operator review. Never resend automatically.

Input parameters:

- `handoffId` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tokyo-chain-agent-address-contracts/mainnet#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 36

## Common questions

### What is the Agent.chain.tokyo Address Contracts MCP server?

Agent.chain.tokyo Address Contracts is an MCP server listed in the public MCP registry as tokyo.chain.agent/address-contracts. Rent a real Japan mailing address for an AI agent via MCP + Solana USDC x402. This page covers its hosted endpoint (https://mainnet.agent.chain.tokyo/mcp).

### Is the Agent.chain.tokyo Address Contracts MCP server safe to use?

Agent.chain.tokyo Address Contracts scores 76 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 Agent.chain.tokyo Address Contracts MCP server expose?

Agent.chain.tokyo Address Contracts exposes 9 tools: list_locations, get_floor_availability, list_contracts, list_events, create_payment_intent, and 4 more. Their descriptions and schemas cost roughly 487 tokens of context every time the server is loaded.

### Does the Agent.chain.tokyo Address Contracts MCP server require authentication?

Yes. Agent.chain.tokyo Address Contracts 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 Agent.chain.tokyo Address Contracts MCP server still maintained?

Agent.chain.tokyo Address Contracts is still listed as active in the MCP registry. We last reached this channel on 5 November 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://mainnet.agent.chain.tokyo/mcp
- Website: https://agent.chain.tokyo/
- Changelog RSS feed: https://verifymcp.io/servers/tokyo-chain-agent-address-contracts/mainnet.xml
- Changelog JSON feed: https://verifymcp.io/servers/tokyo-chain-agent-address-contracts/mainnet.json
- HTML version of this page: https://verifymcp.io/servers/tokyo-chain-agent-address-contracts/mainnet