Pin Payments MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

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

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

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

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

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

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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}.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 61 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 35 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 32466 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 32466 个服务器的 97% 更新
• 基础检查结果等于或优于此分类中其他 32466 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{