Pin Payments MCP by usefulapi
REMOTE · PIN-PAYMENTS.USEFULAPI.IO
Read Pin Payments charges, refunds, balances, transfers and subscriptions without moving money.
Available components
Last scanned (9 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: fail → pass ▲ functional
- New prompt “check_available_and_pending_balances” functional
- New prompt “inspect_a_subscription_and_its_ledger” functional
- New prompt “reconcile_a_transfer_with_its_ledger_entries” functional
- New prompt “review_charges_and_their_refunds” functional
- New prompt “review_disputes_and_their_activity” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.2.0 → 1.4.0 functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.2 → 1.1.0 functional
- 30 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://pin-payments.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pin-payments.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pin-payments.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/pin-payments/ |
| http (plaintext) | http://pin-payments.usefulapi.io/mcp | Inconclusive | 302 | http://pin-payments.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pinpayments_get_authorisation Get authorisation ~60
One authorisation by token (auth_...). GET /authorisations/{token}.
| Name | Type | Req | Description |
|---|---|---|---|
| authorisation_token | string | yes | Authorisation token, e.g. auth_NRzYklT8z3p0yiozsXEAIg. |
No output schema declared.
No examples provided.
pinpayments_get_balance Get balance ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pinpayments_get_charge Get charge ~67
One charge by token (ch_...), with fees, refunds total, settlement transfer state and chargeback flag. GET /charges/{token}.
| Name | Type | Req | Description |
|---|---|---|---|
| charge_token | string | yes | Charge token, e.g. ch_lfUYEBK14zotCTykezJkfg. |
No output schema declared.
No examples provided.
pinpayments_get_customer Get customer ~55
One customer by token (cus_...). GET /customers/{token}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_token | string | yes | Customer token, e.g. cus_XZg1ULpWaROQCOT5PdwLkQ. |
No output schema declared.
No examples provided.
pinpayments_get_deposit Get deposit ~57
One deposit by token (dpo_...). GET /deposits/{token}.
| Name | Type | Req | Description |
|---|---|---|---|
| deposit_token | string | yes | Deposit token, e.g. dpo_Ts3YECK14zotCTykezRspu. |
No output schema declared.
No examples provided.
pinpayments_get_dispute Get dispute ~61
One dispute by token (dis_...). GET /disputes/{token}.
| Name | Type | Req | Description |
|---|---|---|---|
| dispute_token | string | yes | Dispute token, e.g. dis_JRs6Xgk4jMyF33yGijQ7Nw. |
No output schema declared.
No examples provided.
pinpayments_get_dispute_activity Get dispute activity ~58
The activity feed of one dispute (status changes, ledger entries such as chargeback fees and recoveries). GET /disputes/{token}/activity.
| Name | Type | Req | Description |
|---|---|---|---|
| dispute_token | string | yes | Dispute token (dis_...). |
No output schema declared.
No examples provided.
pinpayments_get_event Get event ~54
One event by token (evt_...). GET /events/{token}.
| Name | Type | Req | Description |
|---|---|---|---|
| event_token | string | yes | Event token, e.g. evt_12K4fafROQsdI5PdwLkX. |
No output schema declared.
No examples provided.
pinpayments_get_plan Get plan ~55
One plan by token (plan_...). GET /plans/{token}.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_token | string | yes | Plan token, e.g. plan_ZyDee4HNeUHFHC4SpM2idg. |
No output schema declared.
No examples provided.
pinpayments_get_recipient Get recipient ~55
One recipient by token (rp_...). GET /recipients/{token}.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_token | string | yes | Recipient token, e.g. rp_a98a4fafROQCOT5PdwLkQ. |
No output schema declared.
No examples provided.
pinpayments_get_refund Get refund ~56
One refund by token (rf_...). GET /refunds/{token}.
| Name | Type | Req | Description |
|---|---|---|---|
| refund_token | string | yes | Refund token, e.g. rf_ERCQy--Ay6o-NKGiUVcKKA. |
No output schema declared.
No examples provided.
pinpayments_get_subscription Get subscription ~56
One subscription by token (sub_...). GET /subscriptions/{token}.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_token | string | yes | Subscription token, e.g. sub_bZWXhTzHooKpk9FZjQfzqQ. |
No output schema declared.
No examples provided.
pinpayments_get_subscription_ledger Get subscription ledger ~78
The ledger entries (credits and debits) of one subscription. GET /subscriptions/{token}/ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
| subscription_token | string | yes | Subscription token (sub_...). |
No output schema declared.
No examples provided.
pinpayments_get_transfer Get transfer ~56
One transfer by token (tfer_...). GET /transfers/{token}.
| Name | Type | Req | Description |
|---|---|---|---|
| transfer_token | string | yes | Transfer token, e.g. tfer_lfUYEBK14zotCTykezJkfg. |
No output schema declared.
No examples provided.
pinpayments_list_authorisations List authorisations ~78
List card authorisations (held funds, not yet captured; they expire after seven days) with amount, amount_captured, amount_remaining and expired flags. GET /authorisations.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_charge_refunds List refunds of a charge ~73
All refunds issued against one charge. GET /charges/{token}/refunds.
| Name | Type | Req | Description |
|---|---|---|---|
| charge_token | string | yes | Charge token (ch_...). |
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_charges List charges ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_customer_cards List a customer's cards ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_token | string | yes | Customer token (cus_...). |
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_customer_charges List a customer's charges ~71
Charges made by one customer. GET /customers/{token}/charges.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_token | string | yes | Customer token (cus_...). |
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_customer_subscriptions List a customer's subscriptions ~85
Subscriptions of one customer: state, plan, next billing date, active interval, cancellation time. GET /customers/{token}/subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_token | string | yes | Customer token (cus_...). |
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_customers List customers ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_deposits List deposits ~66
List deposits made to the account (amount, currency, bank narration, available_at). GET /deposits.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_disputes List disputes ~94
List chargeback disputes: category, status, amount, the disputed charge, evidence_required_by and the relevant evidence types. GET /disputes.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
| sort | string | – | Sort field. |
No output schema declared.
No examples provided.
pinpayments_list_events List events ~72
The account's event log (charge.captured, refund.created, dispute.updated, ...), each with the affected record (cards masked). GET /events.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_plan_subscriptions List a plan's subscriptions ~71
Subscriptions to one plan. GET /plans/{token}/subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
| plan_token | string | yes | Plan token (plan_...). |
No output schema declared.
No examples provided.
pinpayments_list_plans List plans ~68
List subscription plans: name, amount, currency, interval, trial and setup amounts, subscription counts by state. GET /plans.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_recipient_transfers List a recipient's transfers ~74
Transfers paid to one recipient. GET /recipients/{token}/transfers.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
| recipient_token | string | yes | Recipient token (rp_...). |
No output schema declared.
No examples provided.
pinpayments_list_recipients List recipients ~60
List transfer recipients (name, email, masked bank account). GET /recipients.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_refunds List refunds ~79
List all refunds, 25 per page: amount (in the currency's base unit), currency, charge token, status_message, error_message, created_at. GET /refunds.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_subscriptions List subscriptions ~75
List all subscriptions: state (trial, active, cancelling, cancelled), plan, customer, next_billing_date, active interval, cancelled_at. GET /subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_list_transfer_line_items List transfer line items ~89
The ledger line items that make up one transfer (charge entitlements, fees, refunds, chargebacks). GET /transfers/{token}/line_items.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
| transfer_token | string | yes | Transfer token (tfer_...). |
No output schema declared.
No examples provided.
pinpayments_list_transfers List transfers ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
pinpayments_search_charges Search charges ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| end_date | string | – | Created before this date, yyyy-mm-dd. |
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
| query | string | – | Text to match. |
| sort | string | – | Sort field (default created_at). |
| start_date | string | – | Created on or after this date, yyyy-mm-dd. |
No output schema declared.
No examples provided.
pinpayments_search_disputes Search disputes ~125
Search disputes by status or exact charge token, optionally filtered by status. GET /disputes/search.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
| query | string | – | Text to match (status, or an exact charge token); at least 3 characters. |
| sort | string | – | Sort field. |
| status | string | – | Dispute status, e.g. evidence_required. |
No output schema declared.
No examples provided.
pinpayments_search_transfers Search transfers ~142
Search transfers by token, description, amount or recipient details and/or a created-date range. GET /transfers/search.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| end_date | string | – | Created before this date, yyyy-mm-dd. |
| page | integer | – | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
| query | string | – | Text to match. |
| sort | string | – | Sort field (the only option is paid_at, also the default). |
| start_date | string | – | Created on or after this date, yyyy-mm-dd. |
No output schema declared.
No examples provided.
How do I install the Pin Payments MCP by usefulapi server?
Pin Payments MCP by usefulapi is a hosted endpoint at https://pin-payments.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pin-payments.usefulapi.io
claude mcp add --transport http io-usefulapi-pin-payments 'https://pin-payments.usefulapi.io/mcp'
What is the Pin Payments MCP by usefulapi server?
Pin Payments MCP by usefulapi is listed in the public MCP registry as io.usefulapi/pin-payments. Read Pin Payments charges, refunds, balances, transfers and subscriptions without moving money. This page covers its hosted endpoint (https://pin-payments.usefulapi.io/mcp).
Is the Pin Payments MCP by usefulapi server safe to use?
Pin Payments MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Pin Payments MCP by usefulapi server expose?
Pin Payments MCP by usefulapi exposes 35 tools: pinpayments_get_balance, pinpayments_list_charges, pinpayments_search_charges, pinpayments_get_charge, pinpayments_list_charge_refunds, and 30 more. Their descriptions and schemas cost roughly 2,685 tokens of context every time the server is loaded.
Does the Pin Payments MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Pin Payments MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Pin Payments MCP by usefulapi server still maintained?
Pin Payments MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Pin Payments MCP by usefulapi server?
VerifyMCP ran 4 checks on Pin Payments MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Pin Payments MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.