Agent.chain.tokyo Address Contracts

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

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

9 tools

• list_locations

  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

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

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

• list_events

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

• create_payment_intent

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

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

• 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_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.

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

Security scan

Recent checks