Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Pin Payments MCP by usefulapi

by m190version 1.6.3i★ –iRuns in the cloud
Registry nameio.usefulapi/pin-payments

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 3 of 3 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • Can do 35 things (tools) pinpayments_get_balance, pinpayments_list_charges, pinpayments_search_charges, pinpayments_get_charge …
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://pin-payments.usefulapi.io/mcp

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://pin-payments.usefulapi.io/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

  • 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_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

  • 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_get_charge

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

  • pinpayments_list_charge_refunds

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

  • 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_get_refund

    One refund by token (rf_...). GET /refunds/{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_get_authorisation

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

  • 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_get_customer

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

  • pinpayments_list_customer_charges

    Charges made by one customer. GET /customers/{token}/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_subscriptions

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

  • pinpayments_list_deposits

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

  • pinpayments_get_deposit

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

  • 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_transfers

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

  • pinpayments_get_transfer

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

  • 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_recipients

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

  • pinpayments_get_recipient

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

  • pinpayments_list_recipient_transfers

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

  • pinpayments_list_disputes

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

  • pinpayments_search_disputes

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

  • 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_list_plans

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

  • pinpayments_get_plan

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

  • pinpayments_list_plan_subscriptions

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

  • pinpayments_list_subscriptions

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

  • 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_list_events

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

  • pinpayments_get_event

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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 61 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 35 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

  • More stars than 0% of the other 32464 servers in this category
  • Published to the registry more recently than 97% of the other 32464 servers in this category
  • Basic checks equal to or better than 100% of the other 32464 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Pin Payments MCP by usefulapi safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.6.3) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, yontu

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

yontu

by senrecep

Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Pin Payments MCP by usefulapi

Read payment records at https://pin-payments.usefulapi.io/mcp.

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://pin-payments.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http pin-payments https://pin-payments.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
{

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

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Pin Payments credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/pin-payments/

Use your Pin Payments secret API key and select its live or test environment. Pin Payments has no read-only API key: the secret can create charges, refunds and bank transfers if misused. This server only sends GET requests and exposes no money-moving tools. Requested payment and customer records pass to your chosen AI client and its LLM provider. Revoke or replace the key in Pin Payments to stop vendor access. Rotating the key starts a new usage and billing identity.

Tools

ToolTypeWhat it does
pinpayments_get_balancereadGet balance
pinpayments_list_chargesreadList charges
pinpayments_search_chargesreadSearch charges
pinpayments_get_chargereadGet charge
pinpayments_list_charge_refundsreadList refunds of a charge
pinpayments_list_refundsreadList refunds
pinpayments_get_refundreadGet refund
pinpayments_list_authorisationsreadList authorisations
pinpayments_get_authorisationreadGet authorisation
pinpayments_list_customersreadList customers
pinpayments_get_customerreadGet customer
pinpayments_list_customer_chargesreadList a customer's charges
pinpayments_list_customer_cardsreadList a customer's cards
pinpayments_list_customer_subscriptionsreadList a customer's subscriptions
pinpayments_list_depositsreadList deposits
pinpayments_get_depositreadGet deposit
pinpayments_list_transfersreadList transfers
pinpayments_search_transfersreadSearch transfers
pinpayments_get_transferreadGet transfer
pinpayments_list_transfer_line_itemsreadList transfer line items
pinpayments_list_recipientsreadList recipients
pinpayments_get_recipientreadGet recipient
pinpayments_list_recipient_transfersreadList a recipient's transfers
pinpayments_list_disputesreadList disputes
pinpayments_search_disputesreadSearch disputes
pinpayments_get_disputereadGet dispute
pinpayments_get_dispute_activityreadGet dispute activity
pinpayments_list_plansreadList plans
pinpayments_get_planreadGet plan
pinpayments_list_plan_subscriptionsreadList a plan's subscriptions
pinpayments_list_subscriptionsreadList subscriptions
pinpayments_get_subscriptionreadGet subscription
pinpayments_get_subscription_ledgerreadGet subscription ledger
pinpayments_list_eventsreadList events
pinpayments_get_eventreadGet event
pinpayments_usage_statusmetaUsage status (free-tier meter)
pinpayments_request_featuremetaRequest a missing feature
pinpayments_upgrademetaUpgrade to Pro or Pro+
pinpayments_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro (per API key and environment)$9/mo or $90/yr (2 months free)Unlimited*

\*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to support@usefulapi.io.

Pro covers this server only. Subscribe with pinpayments_upgrade (it returns a Stripe Checkout link). Cancel any time with pinpayments_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running pinpayments_upgrade before then undoes the cancel. Or write to support@usefulapi.io.

License

Independent integration by usefulapi. See Terms and Privacy.

Ask PopNx