Agent.chain.tokyo Address Contracts MCP Server

by chain-agent Your server? Claim it

answering

Agent.chain.tokyo Address Contracts is answering right now. Last checked 6 min ago. It exposes 9 tools.

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

Uptime history 5 days of history

5 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

1189 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add address-contracts --transport http https://mainnet.agent.chain.tokyo/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mainnet.agent.chain.tokyo/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 9

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

wallet

create_wallet_handoff

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.

get_wallet_payment_status

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.

contracts

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

events

list_events

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

floor

get_floor_availability

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

locations

list_locations

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

payment

create_payment_intent

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

prepare

prepare_wallet_signature

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.

submit

submit_wallet_payment

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mainnet.agent.chain.tokyo/mcp	streamable-http	answering	804 ms	6 min ago

Alternatives to Agent.chain.tokyo Address Contracts

same job, measured the same way

CYRE Guardian

by milesdev888

Solana address risk grades and token scans for AI agents. Pay-per-call via x402 (USDC on Base).

3 tools answering

Magneta Contract Risk

by bosacks

Smart-contract risk reports for AI agents on 20 EVM chains, paid per call via x402 ($0.02 USDC).

4 tools answering

SolSigs MCP

by gra-kir

23 Solana on-chain data tools for AI agents via x402 micropayments + rug-screen token verdict

98 installs/wk local only

Clawswap

by wartech9

Cross-chain swaps between Solana and Base for AI agents paid for via via x402 micropayments.

63 installs/wk local only

Pythia Oracle

by eyloni

Oracle for AI agents. One tool, one reading. 3 free, then $0.025 USDC via x402.

33 installs/wk local only

x402 Tools

by foxxx009

Pay-per-call research tools for AI agents, paid via x402 USDC. Remote MCP, one free tool.

13 tools answering

Agent Browser

by scriptmasterlabs

A real Chromium browser agents pay for per action in USDC via x402 — hosted MCP, free local stdio.

6 tools answering

Asia Pulse

by asia-pulse

Korea & Japan market records for agents. x402 payment inside MCP, Base USDC.

10 tools answering

Agent.chain.tokyo Address Contracts — questions

Answers built from our own checks of this server.

What can Agent.chain.tokyo Address Contracts do?

It exposes 9 tools, read directly from the server on our last check. Among them: create_payment_intent, create_wallet_handoff, get_floor_availability, get_wallet_payment_status, list_contracts, list_events and 3 more. 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 Agent.chain.tokyo Address Contracts 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 1189 ms. The bar chart above shows every period we have measured.

How do I connect Agent.chain.tokyo Address Contracts?

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.

Does Agent.chain.tokyo Address Contracts need an API key?

No. Agent.chain.tokyo Address Contracts completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Agent.chain.tokyo Address Contracts?

It answers our handshake in 1189 ms on average, which is faster than 3% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.