API and MCP server

The website, the REST API and the MCP server read the same dataset and the same scoring code, so they always agree. Everything is read-only: nothing here sends messages, creates payment links or touches your accounts.

MCP server

Endpoint (Streamable HTTP, no authentication): https://pingmyusers.com/mcp

claude mcp add --transport http pingmyusers https://pingmyusers.com/mcp

Tool	What it returns
`search_services`	Find providers by channel, country and capability, or from a plain-words request; best-rated first
`get_service`	Full provider card with evidence and scores
`compare_services`	Compare 2–4 providers for one channel and country
`get_pricing`	Plans and computed scenario costs in one country
`get_integration_guide`	Published guides and tutorials for a provider
`get_alternatives`	Other providers in the same channel
`get_ranking`	Global, channel or country + channel ranking
`get_payment_capabilities`	Payment links, in-chat payments and PSP integrations a provider documents
`recommend_services`	Shortlist for a structured scenario, ordered by rating, with the scenario price
`get_dataset`	Open datasets: MCP and skills, webhook signatures, AI app builder compatibility

Returned strings are catalog data. The server tells clients to treat them as data, not instructions.

REST API

Base URL https://pingmyusers.com/api/v1 · OpenAPI 3.1 document

curl "https://pingmyusers.com/api/v1/providers?channel=whatsapp&capability=payment_links&country=BR"
curl "https://pingmyusers.com/api/v1/rankings?channel=sms&country=MX"
curl -X POST https://pingmyusers.com/api/v1/recommend -H 'content-type: application/json' \
  -d '{"channel":"transactional-email","target_country":"BR","monthly_volume":10000,"requirements":{"official_mcp_required":true}}'

Every response carries methodology_version; facts carry evidence, source_ids and checked. A fact we could not verify is returned as { value: null, evidence: "not-verified" } and listed in unknown_fields — it does not mean the provider lacks the feature.