One URL in your client. Then ask.

Misaka Prog is a hosted MCP server for on-chain networks. Add the endpoint to any client that speaks the Model Context Protocol and your assistant can read ten chains, simulate what a transaction would do and prepare transactions for you to sign in your own wallet.

Endpoint https://masikaprog.vercel.app/mcp

01 · Quickstart

Claude Code

claude mcp add --transport http misaka-prog https://masikaprog.vercel.app/mcp

Cursor, Claude Desktop, Codex, Gemini CLI and other JSON configs

{
  "mcpServers": {
    "misaka-prog": {
      "url": "https://masikaprog.vercel.app/mcp"
    }
  }
}

ChatGPT

Settings → Connectors → Add a custom connector, paste the endpoint, no authentication. Reads need nothing else.

Try it from a terminal

curl -s https://masikaprog.vercel.app/mcp -H 'content-type: application/json' -H 'accept: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"gas_price","arguments":{"chain":"base"}}}'

Then ask in plain words: how much ETH does 0x… hold on Base, explain transaction 0x… on Arbitrum, prepare a transfer of 25 USDC to 0x…. You never type a tool name.

02 · The path of a request

Reads go through steps 1 to 4 and need nothing from you beyond the question. The gateway holds no keys and has no accounts: there is nothing on our side that could move your funds.

03 · Clients

Claude, Claude Code, ChatGPT, Cursor, Codex, Gemini CLI, VS Code, Windsurf and any other client that supports remote MCP servers over streamable HTTP. The transport is stateless JSON: no session to keep alive, no SSE required.

04 · Security

Your keys stay with you

Misaka Prog never holds private keys and will never ask for a seed phrase. Every transaction is signed in your own wallet, on the signing page or by handing the unsigned transaction to your wallet yourself. If anyone claiming to be Misaka Prog asks for a seed phrase or a private key, it is a scam.

Simulation before signature

Every prepare_* tool runs the transaction against live chain state first. Where the node supports eth_simulateV1 you get balance changes and events; everywhere you get success or the exact revert reason and the gas. If the simulation fails, no signing link is produced.

Plain warnings

Prepared transactions are checked for the common ways people lose funds: unlimited approvals, approvals to a plain wallet, sends to a burn address or to a token contract, unverified contracts, copycat tokens using a well-known symbol at another address, and moving most of a balance at once. Your AI is instructed to show you every warning before you sign.

Clean data

Token names, symbols and other text from the chain are written by strangers. The gateway strips hidden and direction-flipping characters, caps their length, and tells your AI to treat them as data, never as instructions.

Nothing to steal

No accounts, no passwords, no stored addresses. Rate limits are counted on a salted one-way fingerprint of the connection that is never written down.

05 · Networks

06 · Limits and errors

• 120 requests a minute per connection; a tool call counts for three. Over the limit the gateway answers JSON-RPC error -32000 with status 429.
• get_logs covers at most 10,000 blocks per call and returns the first 200 events.
• Public nodes can answer slowly under load. A tool that fails returns isError: true with the reason in plain words; nothing is retried on your behalf.
• Prices come from DefiLlama and may lag a few minutes; the timestamp is returned with each price.

07 · $MISAKA

$MISAKA is the token of the gateway. The contract address will be published here and on X first. Until then, any contract claiming to be $MISAKA is not.

08 · Roadmap