Payments MCP server
Planos, assinaturas, links de pagamento e métricas
B77/100grade B
Adoption
New
Little public usage data yet
Reviews
Write oneNobody has reviewed Payments yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Payments tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it
1 low
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 385ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenanceno repository listed3/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
Findings (1)
- lowNo source repository listed
maint.no-repo
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
How Payments compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
Install Payments in Claude Code, Cursor or VS Code
claude mcp add --transport http payments https://payments.worker.myinfrastructure.click/mcp/{project_id}Payments: common questions
- Is Payments MCP server safe?
- Mostly: it is graded B (77/100). Read the Payments safety report
- How do I install Payments?
- It runs remotely at payments.worker.myinfrastructure.click. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Payments need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Payments maintained?
- The latest release is v1.0.1.