Troubleshooting

"It says it's working, but no providers show up"

Before anything else: confirm your agent actually called polymitapay_search rather than just describing it from its schema — see step 2 of Verify & test your install. This is the single most common false alarm.

If it really did call it and got nothing back, check these in order — each one has actually caused this, once each, while building this MCP.

1. The provider isn't approved yet

GET /v1/catalog only returns providers with status === "APPROVED". Every new provider registration starts as PENDING and needs a review pass before it appears anywhere public. If you just registered a provider, this is the most likely cause — check with whoever manages your PolyPay account.

2. Network mismatch

The catalog filters by network too — a provider registered on mainnet will never show up when your MCP is configured for testnet, and vice versa. Check POLYPAY_NETWORK in your client's config against the network the provider was actually registered under.

3. Wrong POLYPAY_API_URL

If you're pointing at a self-hosted or local copy of the backend (POLYPAY_API_URL set to anything other than the default), confirm the provider you're expecting was actually registered against that instance, not https://api.polymitapay.com. A provider approved in production won't appear if your MCP is querying localhost.

Confirm directly, skip the agent entirely

curl "{POLYPAY_API_URL}/v1/catalog?network={POLYPAY_NETWORK}"

Swap in your actual POLYPAY_API_URL (default https://api.polymitapay.com) and POLYPAY_NETWORK (default testnet). An empty array confirms the problem is the catalog itself, not the MCP — work through cases 1–3 above. A non-empty array but still no results in your agent points back at the MCP process itself; check its logs (see Verify & test your install).

The process exits immediately

Check the log for missing required env var POLYPAY_WALLET_SEED — the wallet seed is the one setting with no default. See Configuration reference.