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

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. 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에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  61ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 35개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

기타 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 32455개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 32455개 중 97%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 32455개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

{