Which MCP Endpoint Should I Use?

Code Mode vs managed wallet vs local signer vs bring-your-own-signer — pick the right indie.money MCP connection.

Written By Philippe

Last updated 2 days ago

Which MCP Endpoint Should I Use?

indie.money speaks MCP — the open standard Claude, Cursor, and other AI assistants use to talk to external tools. There are four ways to connect (the difference is how tools are composed and who holds your signing key) and four role namespaces (the difference is what you're trying to do). This page helps you pick both, then sends you to the right how-to.

Which connection style?

Recommended for most assistants: Code Mode — one URL, all namespaces, no multi-server setup.

Style	URL	Who holds your key	Best for
Code Mode (recommended)	`https://mcp.indie.money`	Platform-managed wallet signs when you use buyer/maker/credentials namespaces	Fastest one-endpoint setup — Claude, Cursor, opencode, VS Code
Platform-managed wallet (`wallet-mcp`)	`https://wallet-mcp.indie.money/wallet-mcp/{mount}`	We hold an encrypted key and sign for you	Direct raw mount access; requires a second `api-mcp/public` server for discovery
Local signer (`x402-proxy`)	`https://api-mcp.indie.money/api-mcp/{mount}` (proxy signs locally)	You — the key stays on your machine	Production with a desktop AI client — your key never leaves your side
Bring your own signer (`api-mcp` / direct x402)	`https://api-mcp.indie.money/api-mcp/{mount}`	You — your own app or agent signs in code	Autonomous agents and apps — maximum programmatic control

Whichever you pick, agents can only spend what you fund, and only when you (or your code) approve — there's no standing charge and no open-ended access to your wallet.

Code Mode is the one-endpoint default: connect once to https://mcp.indie.money, ask in plain English, and your assistant composes calls across public, buyer, maker, and credentials namespaces through a single outer code tool. No second server for discovery. Code Mode is stateless — retain the keyId from create_wallet yourself. See Connect Claude, Cursor & ChatGPT to indie.money.

Platform-managed wallet (raw mounts) is the direct path to individual MCP servers: point your assistant at wallet-mcp/{mount}, create a wallet in chat, and the assistant signs each purchase or run for you. You must also add api-mcp/public for browse/search tools. Ideal when you need raw mount semantics without Code Mode composition.

Local signer keeps your key material entirely on your machine: a small proxy runs alongside your desktop AI client and signs each payment locally. See Bring Your Own Wallet.

Bring your own signer is for when you're writing code and want your app to enforce its own rules: it inspects the x402 payment challenge, signs it with its own wallet, and retries. See Pay-Per-Run From Your Own Code.

Which namespace or mount?

Whatever connection style you pick, you target a namespace (Code Mode) or mount (raw servers).

Namespace / mount	Use it to
`public`	Browse, search, and read agent details — no key needed
`buyer`	Buy, fund, run, and monitor agents
`maker`	Publish, price, update, and boost your own agents
`credentials`	Connect API keys / OAuth (stored in the Secure Vault) for an agent you own

Code Mode composes all four namespaces at https://mcp.indie.money — clients register one server, not four.

Raw mounts: api-mcp/{buyer|maker|credentials} automatically includes all public discovery tools — one URL is enough. wallet-mcp/{buyer|maker|credentials} does not — add https://api-mcp.indie.money/api-mcp/public as a second MCP server to browse or search.

Endpoint URLs

indie.money runs on Base (chain 8453) with real stablecoin.

Connection style	URL	Includes `public` discovery?
Code Mode (recommended)	`https://mcp.indie.money`	Yes — all four namespaces in one endpoint
Platform-managed (`wallet-mcp`)	`https://wallet-mcp.indie.money/wallet-mcp/{mount}`	No — add `https://api-mcp.indie.money/api-mcp/public` too
Bring your own signer (`api-mcp`)	`https://api-mcp.indie.money/api-mcp/{mount}`	Yes
Local signer (`x402-proxy`)	`https://api-mcp.indie.money/api-mcp/{mount}` (x402-proxy signs locally, forwards here)	Yes

Replace {mount} with buyer, maker, or credentials on raw-mount rows. Code Mode needs no mount suffix.

Staging Code Mode: https://mcp-staging.indie.money.

Still not sure?

Just want it to work, chatting with Claude → Code Mode (https://mcp.indie.money).

Need direct raw MCP mounts with platform signing → platform-managed wallet (wallet-mcp + api-mcp/public).

Real money, desktop AI client, your key stays local → local signer (x402-proxy).

Writing your own agent or app in code → bring your own signer / direct x402.