MCP server for minia2a.uk — discover and call 1,600+ x402 pay-per-call APIs with USDC payments.
Nothing to run from here
Pin Payments MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
35
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read Pin Payments charges, refunds, balances, transfers and subscriptions without moving money.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http pin-payments-mcp-by-usefulapi https://pin-payments.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# pinpayments_get_balance, pinpayments_list_charges, pinpayments_search_charges and 32 more
Pin Payments MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 598 servers
usefulapi598 servers
25 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http pin-payments-mcp-by-usefulapi https://pin-payments.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
35 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Text to match. |
| start_date | string | no | Created on or after this date, yyyy-mm-dd. |
| end_date | string | no | Created before this date, yyyy-mm-dd. |
| sort | string | no | Sort field (default created_at). |
| direction | string | no | Sort direction (default asc). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
One charge by token (ch_...), with fees, refunds total, settlement transfer state and chargeback flag. GET /charges/{token}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| charge_token | string | yes | Charge token, e.g. ch_lfUYEBK14zotCTykezJkfg. |
All refunds issued against one charge. GET /charges/{token}/refunds.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| charge_token | string | yes | Charge token (ch_...). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
List all refunds, 25 per page: amount (in the currency's base unit), currency, charge token, status_message, error_message, created_at. GET /refunds.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
One refund by token (rf_...). GET /refunds/{token}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| refund_token | string | yes | Refund token, e.g. rf_ERCQy--Ay6o-NKGiUVcKKA. |
List card authorisations (held funds, not yet captured; they expire after seven days) with amount, amount_captured, amount_remaining and expired flags. GET /authorisations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
One authorisation by token (auth_...). GET /authorisations/{token}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| authorisation_token | string | yes | Authorisation token, e.g. auth_NRzYklT8z3p0yiozsXEAIg. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
One customer by token (cus_...). GET /customers/{token}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_token | string | yes | Customer token, e.g. cus_XZg1ULpWaROQCOT5PdwLkQ. |
Charges made by one customer. GET /customers/{token}/charges.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_token | string | yes | Customer token (cus_...). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_token | string | yes | Customer token (cus_...). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
Subscriptions of one customer: state, plan, next billing date, active interval, cancellation time. GET /customers/{token}/subscriptions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_token | string | yes | Customer token (cus_...). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
List deposits made to the account (amount, currency, bank narration, available_at). GET /deposits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
One deposit by token (dpo_...). GET /deposits/{token}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deposit_token | string | yes | Deposit token, e.g. dpo_Ts3YECK14zotCTykezRspu. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
Search transfers by token, description, amount or recipient details and/or a created-date range. GET /transfers/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Text to match. |
| start_date | string | no | Created on or after this date, yyyy-mm-dd. |
| end_date | string | no | Created before this date, yyyy-mm-dd. |
| sort | string | no | Sort field (the only option is paid_at, also the default). |
| direction | string | no | Sort direction (default asc). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
One transfer by token (tfer_...). GET /transfers/{token}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transfer_token | string | yes | Transfer token, e.g. tfer_lfUYEBK14zotCTykezJkfg. |
The ledger line items that make up one transfer (charge entitlements, fees, refunds, chargebacks). GET /transfers/{token}/line_items.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transfer_token | string | yes | Transfer token (tfer_...). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
List transfer recipients (name, email, masked bank account). GET /recipients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
One recipient by token (rp_...). GET /recipients/{token}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| recipient_token | string | yes | Recipient token, e.g. rp_a98a4fafROQCOT5PdwLkQ. |
Transfers paid to one recipient. GET /recipients/{token}/transfers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| recipient_token | string | yes | Recipient token (rp_...). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
List chargeback disputes: category, status, amount, the disputed charge, evidence_required_by and the relevant evidence types. GET /disputes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sort | string | no | Sort field. |
| direction | string | no | Sort direction (default asc). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
Search disputes by status or exact charge token, optionally filtered by status. GET /disputes/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Text to match (status, or an exact charge token); at least 3 characters. |
| status | string | no | Dispute status, e.g. evidence_required. |
| sort | string | no | Sort field. |
| direction | string | no | Sort direction (default asc). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
One dispute by token (dis_...). GET /disputes/{token}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dispute_token | string | yes | Dispute token, e.g. dis_JRs6Xgk4jMyF33yGijQ7Nw. |
The activity feed of one dispute (status changes, ledger entries such as chargeback fees and recoveries). GET /disputes/{token}/activity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dispute_token | string | yes | Dispute token (dis_...). |
List subscription plans: name, amount, currency, interval, trial and setup amounts, subscription counts by state. GET /plans.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
One plan by token (plan_...). GET /plans/{token}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_token | string | yes | Plan token, e.g. plan_ZyDee4HNeUHFHC4SpM2idg. |
Subscriptions to one plan. GET /plans/{token}/subscriptions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_token | string | yes | Plan token (plan_...). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
List all subscriptions: state (trial, active, cancelling, cancelled), plan, customer, next_billing_date, active interval, cancelled_at. GET /subscriptions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
One subscription by token (sub_...). GET /subscriptions/{token}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subscription_token | string | yes | Subscription token, e.g. sub_bZWXhTzHooKpk9FZjQfzqQ. |
The ledger entries (credits and debits) of one subscription. GET /subscriptions/{token}/ledger.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subscription_token | string | yes | Subscription token (sub_...). |
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
The account's event log (charge.captured, refund.created, dispute.updated, ...), each with the affected record (cards masked). GET /events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1); 25 results per page. Pass the previous reply's next_page. |
One event by token (evt_...). GET /events/{token}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_token | string | yes | Event token, e.g. evt_12K4fafROQsdI5PdwLkX. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Pin Payments MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.7.2 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest32a852cfb309570f68d98494599d0cf9f4a5d8a18d37ae8269177daeb56562a3
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| pinpayments_get_balance | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_charges | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_search_charges | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_charge | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_charge_refunds | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_refunds | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_refund | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_authorisations | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_authorisation | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_customers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_customer | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_customer_charges | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_customer_cards | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_customer_subscriptions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_deposits | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_deposit | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_transfers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_search_transfers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_transfer | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_transfer_line_items | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_recipients | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_recipient | external-sinkuntrusted-input | external-sink: parameter "recipient"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_recipient_transfers | external-sinkuntrusted-input | external-sink: parameter "recipient"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_disputes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_search_disputes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_dispute | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_dispute_activity | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_plans | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_plan | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_plan_subscriptions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_subscriptions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_subscription | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_subscription_ledger | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_list_events | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pinpayments_get_event | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest32a852cfb309570f
Scanned2026-11-07
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.7.2.
1.7.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Pin Payments MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.