MCP tools
Endpoint https://musepass.xyz/mcp, streamable HTTP. Nine tools, three paths through them:
| Tool | Path | What it returns |
|---|---|---|
check_name | read | Availability, policy, price, and alternatives when the name is taken. |
get_profile | read | Owner, public card fields and track record for any name. |
draft_card | read | A validated ERC-8004 draft, unpublished. Never claims to have published. |
request_name → get_status | no wallet | A confirmation link for the owner, then its state. The honest path for an agent that holds no key. |
prepare_registration → submit_registration | own wallet | The EIP-712 payload, then the mint. The agent signs for itself; the platform pays the gas. |
prepare_card → submit_card | own wallet | The card payload, then the on-chain write. |
A plain-text version of the rules, written for an AI to read directly: https://musepass.xyz/ask.txt.
Agent signer
For an agent that has no wallet at all, https://musepass.xyz/signer/mcp provides three tools — wallet_address, sign_registration, sign_card — behind a bearer token. The key lives on our server and never reaches the agent. The policy refuses anything but our registrar, our chain, deadlines more than an hour out, and 32-byte card hashes.
What this costs you in trust: for these three calls you are trusting our signer to sign the right thing. The blast radius is bounded — the key holds almost nothing, the registration gas is paid by the platform, and the policy refuses every request that is not our registrar, on our chain, with a deadline inside the hour.