List the connector#
Distribution is the whole of phase one: a wallet nobody can find is a wallet nobody funds. This is the listing kit, the same copy for every directory, and the steps for each one. Nothing here needs code; the site build already emits the manifest.
The listing, once#
Use these words everywhere, so the connector reads as one product:
- Name: mechawallet
- One line: The wallet for agents. Pay any x402 endpoint from a wallet you fund. No gas, no keys.
- Longer: Give your agent a wallet, fund it with USDC on Base or
Solana, and ask it to buy what it needs. One API key, a budget you set,
and a burner you throw away when the job is done.
search_endpointslists what it can buy with verified prices;pay_x402(url)buys it and returns the goods with a receipt. A thousand payments a month are free; the rest of the price list is at mechawallet.com/docs/reference/costs/. - MCP URL:
https://api.mechawallet.com/mcp(streamable HTTP) - Auth: OAuth (one approval in Claude), or
Authorization: Bearer mw_live_… - Connect command:
claude mcp add --transport http mechawallet https://api.mechawallet.com/mcp
- Icons:
https://mechawallet.com/static/brand/icon.svgand the PNG sizes under/static/brand/. - Categories: payments, finance, agent tools, commerce.
- Website:
https://mechawallet.com. Docs:https://mechawallet.com/docs/. - Privacy policy and support contact: the owner supplies both; every directory below asks for them.
Preflight, two minutes#
The manifest the build emits, at the site root and at the well-known path:
curl -s https://mechawallet.com/.well-known/server.json
The server answers an MCP initialize without any credential:
curl -s https://api.mechawallet.com/mcp -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"preflight","version":"1"}}}'
and tools/list needs no auth and shows search_endpoints, pay_x402
and the rest.
The official MCP Registry#
The registry (registry.modelcontextprotocol.io) is what Claude, Cursor and the other clients read first. The commands below are from its README; check them against the current README the day you publish, the CLI is young.
- Install the publisher:
brew install mcp-publisher(or the release binary from the registry's GitHub). - The manifest is already written:
server.jsonat the site root, with the namecom.mechawallet/mechawallet(reverse DNS of the domain, then the product). - Prove the namespace. Either a DNS TXT record on
mechawallet.com, or HTTP: the registry fetcheshttps://mechawallet.com/.well-known/mcp-registry-authwith the public key the login step prints. DNS is the one that survives a site rebuild:
mcp-publisher login dns --domain mechawallet.com --private-key <key>
- Publish from the directory that holds
server.json:
mcp-publisher publish
- Verify: search the registry API for the name and confirm the remote URL:
curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=mechawallet"
The directories#
Each takes the listing above. Submit in this order; the first two feed the others.
- Smithery (smithery.ai): add a remote server with the MCP URL; it
reads
server.jsonwhen present. Needs the icon and the one line. - PulseMCP (pulsemcp.com): the submit form; name, URL, one line, the longer description, the docs link.
- Glama (glama.ai/mcp/servers): the submit form or a pull request to their list; they crawl the manifest and score the README, so the docs link matters.
- The Claude connector directory: Anthropic's submission form for
remote MCP servers. Needs the privacy policy URL, the support contact,
the OAuth flow working from a fresh Claude account (it is), and a short
demo: connect,
search_endpoints("weather"),pay_x402on the test checkout.
After listing#
- Watch
/blargdash: new accounts, active wallets and the funnel say whether a listing sends anyone. - The connect command and the MCP URL in this guide are the ones the site
quotes; if either changes, change it in
docs/guides/connect-claude.mdfirst and this page follows.