Pin Payments MCP by usefulapi
Server Details
Read Pin Payments charges, refunds, balances, transfers and subscriptions without moving money.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 35 tools
Most tools target clearly distinct resources and actions, and the get/list/search verb split is easy to follow. Some boundaries are slightly fuzzy where broad list tools overlap with search tools (e.g. list_charges vs search_charges) or with per-parent list tools (e.g. list_refunds vs list_charge_refunds), but descriptions usually clarify the intended use.
All tools consistently use the pinpayments_ prefix followed by a predictable verb_noun pattern such as get_charge, list_customers, and search_transfers. There is no mixing of camelCase, vague verbs, or inconsistent conventions.
At 35 tools this is a heavy surface, inflated by many per-parent list endpoints (customer cards, customer charges, customer subscriptions, plan subscriptions, recipient transfers, charge refunds) that could often be expressed as filters on broader list tools. Although each tool maps to a real API endpoint, the set is larger than necessary for a well-scoped MCP surface.
The server exposes only read-only GET operations, so it covers retrieval well but omits the core mutating payment lifecycle: creating charges, capturing authorisations, issuing refunds, creating customers, plans, subscriptions, recipients, and transfers. These gaps mean an agent cannot complete many primary Pin Payments tasks.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read Checkout.com payments, disputes, reports and payouts.
Read MoonClerk payment forms, customers (plans with subscriptions) and payments. Read-only.
Read Kisi places, doors, users, groups, access rights and access logs (no unlocking).
Read Gift Up! gift cards, orders, items, promotions and transactions (read-only, codes masked).
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables read-only querying of payments and billing data via the full official REST API, covering customers, charges, payment intents, subscriptions, invoices, refunds, and more.MIT
- AlicenseNot gradedqualityCmaintenanceRead-only access to Stripe data including customers, charges, subscriptions, balance, and invoices.103 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables reading customer, subscription, transaction, and adjustment data from the Paddle Billing API to inspect billing and recurring-revenue state.90 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only access to customer and recurring-billing state from Recurly, including accounts, subscriptions, invoices, and payment outcomes.90 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.