Verify & test your install

1. Restart your client, then check its logs

Every real MCP client logs each server's own stderr output somewhere. On Claude Desktop (macOS), that's:

tail -f ~/Library/Logs/Claude/mcp-server-polymitapay.log

A healthy startup looks like this:

using wallet rJLbHtbeCXEzKGvZyQqT1twb9byBf3zinx
catalog: 1 approved provider(s) on testnet
discovered 2 tool(s), ready to search
polymitapay-wallet-mcp listening on stdio

If catalog: 0 approved provider(s) shows up, or the process exits before listening on stdio, jump to Troubleshooting.

2. Make your agent actually call the tools

Asking your agent something vague ("what can you do?") often makes it just describe the two tools from their schema, without ever calling them — the log will show a tools/list request but no tools/call. That's not a real test. Be explicit:

Use the polymitapay_search tool (don't just describe it, call it) with the
query "summarize", and paste me the JSON result it returns.

If that comes back with real matches, chain a real payment:

Take the "tool" id from that result and call it with polymitapay_call,
passing a short piece of text to summarize. Show me the full result,
including the _meta fields (x402/payment-made and x402/payment-response).

This is testnet-safe (free play money) as long as POLYPAY_NETWORK is testnet — see Configuration reference.

3. Confirm the catalog independently

You can check exactly what the MCP will see, without going through your agent at all:

curl "https://api.polymitapay.com/v1/catalog?network=testnet"

An empty array ([]) here means the problem is upstream of the MCP entirely — see Troubleshooting.