Skip to main content
Glama

Agent.chain.tokyo Address Contracts

Server Details

Rent a real Japan mailing address for an AI agent acting for an individual owner. Pay 55 USDC per location x virtual floor x 30 days on Solana Mainnet via x402 v2. OAuth 2.0 with owner Google consent (dynamic client registration supported).

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 9 tools

Disambiguation4/5

The nine tools split into clear groups: catalog reads (list_locations, list_contracts, list_events, get_floor_availability) and a linear payment flow (create_payment_intent, create_wallet_handoff, prepare_wallet_signature, submit_wallet_payment). The payment steps are sequential rather than overlapping, but create_payment_intent vs create_wallet_handoff and submit vs get_wallet_payment_status could still be momentarily confused without reading the long descriptions.

Naming Consistency5/5

Every tool follows a strict snake_case verb_noun pattern (create_*, get_*, list_*, prepare_*, submit_*). Action verbs map predictably to intent: list/get for reads, create/prepare/submit for mutations.

Tool Count5/5

Nine tools is well within the ideal 3-15 range and maps neatly onto the two sub-domains (address/location catalog and the x402 wallet payment handshake). No tool appears redundant or filler.

Completeness3/5

The payment flow is end-to-end, but there are notable dead ends: no cancel/abandon payment intent (or floor release), no get_contract or get_location detail beyond list summaries, and no way to revoke or refresh an expired handoff. Agents can work around some of these, but lifecycle coverage is partial.

Available Tools

9 tools
create_payment_intentCreate a Mainnet Payment IntentCInspect

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

Inputs: floor (required), locationId (required), termsVersion (required), applicantKind (required), +2 more.

create_wallet_handoffA
Destructive
Inspect

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.

Inputs: intentId (required).

get_floor_availabilityCheck virtual floor availabilityCInspect

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

Inputs: floor (required), locationId (required).

get_wallet_payment_statusB
Read-onlyIdempotent
Inspect

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.

Inputs: handoffId (required).

list_contractsList authenticated owner contractsAInspect

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

Inputs: no named parameters.

list_eventsRead durable Agent eventsBInspect

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

Inputs: after, limit.

list_locationsList Location summariesAInspect

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

Inputs: no named parameters.

prepare_wallet_signatureB
Destructive
Inspect

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.

Inputs: handoffId (required).

submit_wallet_paymentA
Destructive
Inspect

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.

Inputs: handoffId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes deadline-driven Japanese public-sector business opportunity data (tenders, subsidies, sanctions) to AI agents, with per-call payment via the x402 protocol.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to commission real-world errands in Japan — shopping, stock checks, on-site photography, restaurant phone reservations, queue standing, and package pickup/forwarding — through instant itemised quotes, operator review, and status messaging. Returns standardised evidence packages for completed tasks, with a test mode that runs the full flow without payment.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources