Pin Payments MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Pin Payments MCP by usefulapi is answering right now. Last checked 1 min ago. It exposes 35 tools. Last commit 1 Nov 2026.

Read Pin Payments charges, refunds, balances, transfers and subscriptions without moving money.

Uptime history 38 hours of history

38 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

232 ms

Response time

average over 24h

Stars

last commit 1 Nov 2026

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 31 October 2026. No other catalogue keeps this.

31 Oct a tool changed version4 times that day

and 3 more, back to 31 October 2026

Nothing serious here today

Today is the operative word: we check Pin Payments MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add pin-payments --transport http https://pin-payments.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://pin-payments.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.pin-payments]
url = "https://pin-payments.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "pin-payments": {
      "url": "https://pin-payments.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "pin-payments": {
      "type": "http",
      "url": "https://pin-payments.usefulapi.io/mcp"
    }
  }
}

Available tools 35

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

pinpayments

pinpayments_get_authorisation

One authorisation by token (auth_...). GET /authorisations/{token}.

pinpayments_get_balance

The current Pin Payments account balance: available (ready to transfer) and pending (available plus estimated funds from charges that have not settled yet), per currency, in the currency's base unit (cents for AUD). GET /balance.

pinpayments_get_charge

One charge by token (ch_...), with fees, refunds total, settlement transfer state and chargeback flag. GET /charges/{token}.

pinpayments_get_customer

One customer by token (cus_...). GET /customers/{token}.

pinpayments_get_deposit

One deposit by token (dpo_...). GET /deposits/{token}.

pinpayments_get_dispute

One dispute by token (dis_...). GET /disputes/{token}.

pinpayments_get_dispute_activity

The activity feed of one dispute (status changes, ledger entries such as chargeback fees and recoveries). GET /disputes/{token}/activity.

pinpayments_get_event

One event by token (evt_...). GET /events/{token}.

pinpayments_get_plan

One plan by token (plan_...). GET /plans/{token}.

pinpayments_get_recipient

One recipient by token (rp_...). GET /recipients/{token}.

pinpayments_get_refund

One refund by token (rf_...). GET /refunds/{token}.

pinpayments_get_subscription

One subscription by token (sub_...). GET /subscriptions/{token}.

pinpayments_get_subscription_ledger

The ledger entries (credits and debits) of one subscription. GET /subscriptions/{token}/ledger.

pinpayments_get_transfer

One transfer by token (tfer_...). GET /transfers/{token}.

pinpayments_list_authorisations

List card authorisations (held funds, not yet captured; they expire after seven days) with amount, amount_captured, amount_remaining and expired flags. GET /authorisations.

pinpayments_list_charge_refunds

All refunds issued against one charge. GET /charges/{token}/refunds.

pinpayments_list_charges

List charges (card payments), 25 per page: amount (in the currency's base unit, e.g. cents for AUD), currency, description, payer email, status_message/success, total_fees, merchant_entitlement, amount_refunded, captured, settlement transfers, chargebacks flag, metadata. The card is shown only as scheme and last four digits. GET /charges.

pinpayments_list_customer_cards

Cards stored for one customer, each shown only as scheme, last four digits and issuing country (no token, expiry or address). GET /customers/{token}/cards.

pinpayments_list_customer_charges

Charges made by one customer. GET /customers/{token}/charges.

pinpayments_list_customer_subscriptions

Subscriptions of one customer: state, plan, next billing date, active interval, cancellation time. GET /customers/{token}/subscriptions.

pinpayments_list_customers

List stored customers, 25 per page: token, email, first_name, last_name, phone_number, company, notes and the primary card as scheme and last four digits. GET /customers.

pinpayments_list_deposits

List deposits made to the account (amount, currency, bank narration, available_at). GET /deposits.

pinpayments_list_disputes

List chargeback disputes: category, status, amount, the disputed charge, evidence_required_by and the relevant evidence types. GET /disputes.

pinpayments_list_events

The account's event log (charge.captured, refund.created, dispute.updated, ...), each with the affected record (cards masked). GET /events.

pinpayments_list_plan_subscriptions

Subscriptions to one plan. GET /plans/{token}/subscriptions.

pinpayments_list_plans

List subscription plans: name, amount, currency, interval, trial and setup amounts, subscription counts by state. GET /plans.

pinpayments_list_recipient_transfers

Transfers paid to one recipient. GET /recipients/{token}/transfers.

pinpayments_list_recipients

List transfer recipients (name, email, masked bank account). GET /recipients.

pinpayments_list_refunds

List all refunds, 25 per page: amount (in the currency's base unit), currency, charge token, status_message, error_message, created_at. GET /refunds.

pinpayments_list_subscriptions

List all subscriptions: state (trial, active, cancelling, cancelled), plan, customer, next_billing_date, active interval, cancelled_at. GET /subscriptions.

pinpayments_list_transfer_line_items

The ledger line items that make up one transfer (charge entitlements, fees, refunds, chargebacks). GET /transfers/{token}/line_items.

pinpayments_list_transfers

List transfers (payouts to bank accounts), 25 per page: status, amount, debits/credits, paid_at, reference, line item count, bank account (masked) and recipient. GET /transfers.

pinpayments_search_charges

Search charges by free text (description, email, metadata, cardholder name, currency, exact amount in the currency's base unit, exact charge/card/refund/customer token) and/or a created-date range. GET /charges/search.

pinpayments_search_disputes

Search disputes by status or exact charge token, optionally filtered by status. GET /disputes/search.

pinpayments_search_transfers

Search transfers by token, description, amount or recipient details and/or a created-date range. GET /transfers/search.

Endpoints

URL	Transport	State	Latency	Checked
https://pin-payments.usefulapi.io/mcp	streamable-http	answering	174 ms	1 min ago

Alternatives to Pin Payments MCP by usefulapi

same job, measured the same way

MoonClerk MCP by usefulapi

by usefulapi

Read MoonClerk payment forms, customers (plans with subscriptions) and payments. Read-only.

6 tools answering

Braintree MCP by usefulapi

by usefulapi

Search Braintree transactions, customers and payment methods, and refund or void charges.

7 tools answering

Chargebee MCP by usefulapi

by usefulapi

Read Chargebee customers, subscriptions, invoices, items, transactions, credit notes and coupons.

13 tools answering

Invoiced MCP by usefulapi

by usefulapi

Read Invoiced customers, invoices, payments, subscriptions; create customers, draft invoices, notes.

27 tools answering

ChargeOver MCP by usefulapi

by usefulapi

Read ChargeOver customers, invoices, transactions, subscriptions, reports; create customers, quotes.

25 tools answering

Recurpay MCP by usefulapi

by usefulapi

Read subscriptions, subscribers and orders; manage renewals, billing skips and payment links.

18 tools answering

Lago MCP by usefulapi

by usefulapi

Read Lago customers, subscriptions, invoices, usage and revenue analytics; write events.

24 tools answering

Orb MCP by usefulapi

by usefulapi

Read Orb customers, subscriptions, invoices, usage and costs; create or update customers.

26 tools answering

Pin Payments MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Pin Payments MCP by usefulapi do?

It exposes 35 tools, read directly from the server on our last check. Among them: pinpayments_get_authorisation, pinpayments_get_balance, pinpayments_get_charge, pinpayments_get_customer, pinpayments_get_deposit, pinpayments_get_dispute and 29 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Pin Payments MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 232 ms. The bar chart above shows every period we have measured.

How do I connect Pin Payments MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Pin Payments MCP by usefulapi need an API key?

No. Pin Payments MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 35 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Pin Payments MCP by usefulapi?

It answers our handshake in 232 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Pin Payments MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at pin-payments.usefulapi.io, which runs on its operator's own terms.