Agent.chain.tokyo Address Contracts

tokyo.chain.agentPublished by agent.chain.tokyoOfficial publisherv1.0.0Updated Oct 30, 2026

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

VerifiedStreamable HTTPWeb executableLocation & LifestyleFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant rent a Japan mailing address for an agent: browse locations and floors, create a 55 USDC payment intent, and track contracts and events.

What you can do
  • List safe location summaries and virtual floor ranges, and check floor availability for the authenticated owner
  • List the owner's contracts, including the snapshotted mailbox address on active paid contracts with valid assent
  • Read the owner's durable event inbox after an optional cursor
  • Reserve a floor and create a fixed 55 USDC native-USDC x402 payment intent
  • Create a short-lived owner login link, prepare the immutable transaction after Phantom connects, and submit the saved proof once the owner signs
  • Read server-recorded settlement evidence for a handoff
When to use it
Use it when an agent needs a real Japan mailing address and the owner is willing to pay 55 USDC on Solana through a Phantom wallet. Suited to setups where the owner completes wallet steps personally while the assistant handles discovery, reservation and status checks.
Requirements
Remote streamable HTTP endpoint; no local package or environment variables. Every tool call requires OAuth via the protected-resource metadata, and the owner needs a Phantom wallet holding 55 USDC on Solana for payment.
Before you install
Payment moves real funds: create_payment_intent reserves a floor and fixes a 55 USDC charge, and submit_wallet_payment sends the signed proof once. The server states it never asks for a token or private key, so keep signing in the owner's own Phantom page. Acknowledgement is not settlement, and unknown or review results need operator review; do not retry submissions automatically.

Installation

In SourceWeft

  1. Open Agent.chain.tokyo Address Contracts in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/tokyo.chain.agent%2Faddress-contracts/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

9

list_locations

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.

Takes no parameters.

get_floor_availability

Check virtual floor availability

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

ParametersfloorrequiredlocationIdrequired

list_contracts

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.

Takes no parameters.

list_events

Read durable Agent events

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

Parametersafterlimit

create_payment_intent

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.

ParametersfloorrequiredlocationIdrequiredtermsVersionrequiredapplicantKindrequiredtermsAcceptedrequiredaccountOwnerAuthorityConfirmedrequired

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.

ParametersintentIdrequired

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.

ParametershandoffIdrequired

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.

ParametershandoffIdrequired

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.

ParametershandoffIdrequired

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Chain integrations