Anchor MCP Server

Most developer tooling work still happens through a UI a human drives. Anchor MCP server moves it into the conversation instead. 9-tool x402-paid MCP server on Base + Solana mainnet. Pay-per-call USDC, no API keys.

The short version

Clients that speak remote MCP natively take the url form above. For one that only launches stdio processes, bridge it:

The tools it exposes

The server publishes 14 tools. What each one is for:

• Recommended — generate a fresh wallet specifically for agent use. Top up periodically; don't reuse a wallet that holds significant funds
• Base — https://basescan.org/tx/<base.tx> — Input Data field contains the merkle root
• Solana — https://solscan.io/tx/<solana.tx> — Memo program data contains the same hex
• Status — ** https://anchor-x402.betteruptime.com
• anchor_hash — $0.005
• screen_wallet — $0.001
• attest_decision — $0.010
• decode_tx — $0.001
• resolve_name — $0.001
• token_price — $0.001
• decode_calldata — $0.001
• parse_datetime — $0.001

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: ANCHOR_WALLET_PRIVATE_KEY, ANCHOR_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Anchor's toolset — Recommended, Base, Solana and 11 more — is a fair guide to whether it matches your workflow. It is maintained by hypeprinter007-stack; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Anchor.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.