Remote MCP · Endpoint

Agent.chain.tokyo Address Contracts MCP server

No. Agent.chain.tokyo Address Contracts answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
tokyo.chain.agent/address-contracts
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
258 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Rent a real Japan mailing address for an AI agent via MCP + Solana USDC x402.
Listing
From the official MCP registry (active).
Recent checks of Agent.chain.tokyo Address Contracts
CheckedResultHandshake
9 hours agoHandshake completed258 ms
4 days agoHandshake completed225 ms
14 days agoHandshake completed229 ms
15 days agoHandshake completed257 ms
15 days agoHandshake completed230 ms
17 days agoHandshake completed213 ms
18 days agoHandshake completed228 ms
19 days agoHandshake completed222 ms
20 days agoHandshake completed212 ms
21 days agoHandshake completed225 ms
23 days agoCredentials required—

The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Agent.chain.tokyo Address Contracts and makes no claim about it beyond what these checks measured.