Skip to content

Checkout.com MCP by usefulapi

io.usefulapi/checkoutcomusefulapi.iostreamable-httpv1.40.4Scanned

Read Checkout.com payments, disputes, reports and payouts.

18 tools: 6 can delete or cancel things, 1 do something that can't be undone and 11 change things.

Tools: 6 delete, 1 irreversible, 11 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • 12 findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

18 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Checkout.com MCP by usefulapi can do

The Checkout.com MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 18 tools. It can delete or cancel things (6 tools: checkout_create_payment, checkout_capture_payment, checkout_refund_payment, checkout_void_payment and 2 more), do things that cannot be undone, such as sending, paying or publishing (checkout_list_disputes) and create or change data (11 tools: checkout_get_payment, checkout_list_payments, checkout_search_payments, checkout_get_payment_actions and 7 more). None of its tools only reads.

1 tool can send data out of your system (checkout_list_disputes).

The fixed checks matched 12 findings (annotation-conflict). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

18 tools

Deletes or cancels 6Claude Code: deny
  • checkout_capture_paymentCAPTURES a previously authorized payment — this MOVES MONEY: it settles the (full or partial) authorized amount.No findings

    Why it is in this group

    • The name "checkout_capture_payment" says "checkout": a word for a change.
    • The name "checkout_capture_payment" also says "capture": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    CAPTURES a previously authorized payment — this MOVES MONEY: it settles the (full or partial) authorized amount. Checkout.com: POST /payments/{id}/captures.

    Annotations the server declares

    • title: Capture payment
    • destructiveHint: true
  • checkout_create_customerCREATES a customer record (which saved instruments and future payments can be attached to).No findings

    Why it is in this group

    • The name "checkout_create_customer" says "checkout": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    CREATES a customer record (which saved instruments and future payments can be attached to). This ADDS data to your account. Checkout.com: POST /customers.

    Annotations the server declares

    • title: Create customer
    • destructiveHint: true
  • checkout_create_paymentCREATES a payment (request an authorization, or an immediate capture) — this MOVES MONEY: it charges a card / payment source.No findings

    Why it is in this group

    • The name "checkout_create_payment" says "checkout": a word for a change.
    • The input carries an amount (input.amount) and a currency, so it moves money.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    CREATES a payment (request an authorization, or an immediate capture) — this MOVES MONEY: it charges a card / payment source. Checkout.com: POST /payments. Provide `amount` (minor units), `currency`, and a `source` object such as { type: 'token', token: 'tok_...' }, { type: 'id', id: 'src_...' } (a saved instrument), or { type: 'customer', id: 'cus_...' }.

    Annotations the server declares

    • title: Create payment
    • destructiveHint: true
  • checkout_refund_paymentREFUNDS a captured payment — this MOVES MONEY BACK to the customer (full or partial).No findings

    Why it is in this group

    • The name "checkout_refund_payment" says "checkout": a word for a change.
    • The name "checkout_refund_payment" also says "refund": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    REFUNDS a captured payment — this MOVES MONEY BACK to the customer (full or partial). Checkout.com: POST /payments/{id}/refunds.

    Annotations the server declares

    • title: Refund payment
    • destructiveHint: true
  • checkout_void_paymentVOIDS (cancels) a payment that has been authorized but not yet captured — this releases the hold on the customer's funds.No findings

    Why it is in this group

    • The name "checkout_void_payment" says "checkout": a word for a change.
    • The description's first verb is "void": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    VOIDS (cancels) a payment that has been authorized but not yet captured — this releases the hold on the customer's funds. Checkout.com: POST /payments/{id}/voids.

    Annotations the server declares

    • title: Void payment
    • destructiveHint: true
Can't be undone 1Claude Code: ask
  • checkout_list_disputesList disputes (chargebacks) against your business, most-recently-modified first, with optional filters.Can send data out1 finding

    Why it is in this group

    • The name "checkout_list_disputes" says "checkout": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "checkout_list_disputes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true}; The name "checkout_list_disputes" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    List disputes (chargebacks) against your business, most-recently-modified first, with optional filters. Checkout.com: GET /disputes.

    Annotations the server declares

    • title: List disputes
    • readOnlyHint: true
Changes things 11Claude Code: ask
  • checkout_get_customerGet a customer's details (email, name, phone, saved instruments) by id 'cus_...' or by email.1 finding

    Why it is in this group

    • The name "checkout_get_customer" says "checkout": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "checkout_get_customer" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "checkout_get_customer" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Get a customer's details (email, name, phone, saved instruments) by id 'cus_...' or by email. Checkout.com: GET /customers/{id}.

    Annotations the server declares

    • title: Get customer
    • readOnlyHint: true
  • checkout_get_disputeGet all the details of a single dispute (reason code, amount, deadline, evidence status) by id 'dsp_...'.1 finding

    Why it is in this group

    • The name "checkout_get_dispute" says "checkout": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "checkout_get_dispute" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "checkout_get_dispute" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Get all the details of a single dispute (reason code, amount, deadline, evidence status) by id 'dsp_...'. Checkout.com: GET /disputes/{id}.

    Annotations the server declares

    • title: Get dispute
    • readOnlyHint: true
  • checkout_get_forex_ratesGet the indicative foreign-exchange rates Checkout.com uses (e.g.1 finding

    Why it is in this group

    • The name "checkout_get_forex_rates" says "checkout": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "checkout_get_forex_rates" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "checkout_get_forex_rates" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Get the indicative foreign-exchange rates Checkout.com uses (e.g. for card payouts). Checkout.com: GET /forex/rates.

    Annotations the server declares

    • title: Get forex rates
    • readOnlyHint: true
  • checkout_get_instrumentGet the details of a saved payment instrument (tokenized card / bank account) by id 'src_...'.1 finding

    Why it is in this group

    • The name "checkout_get_instrument" says "checkout": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "checkout_get_instrument" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "checkout_get_instrument" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Get the details of a saved payment instrument (tokenized card / bank account) by id 'src_...'. Checkout.com: GET /instruments/{id}.

    Annotations the server declares

    • title: Get instrument
    • readOnlyHint: true
  • checkout_get_paymentGet the full details of a payment (or payment session) by its id, e.g.1 finding

    Why it is in this group

    • The name "checkout_get_payment" says "checkout": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "checkout_get_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "checkout_get_payment" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Get the full details of a payment (or payment session) by its id, e.g. 'pay_...'. Checkout.com: GET /payments/{id}.

    Annotations the server declares

    • title: Get payment
    • readOnlyHint: true
  • checkout_get_payment_actionsList all the actions (authorization, capture, refund, void, etc.) associated with a payment, latest first.1 finding

    Why it is in this group

    • The name "checkout_get_payment_actions" says "checkout": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "checkout_get_payment_actions" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "checkout_get_payment_actions" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    List all the actions (authorization, capture, refund, void, etc.) associated with a payment, latest first. Checkout.com: GET /payments/{id}/actions.

    Annotations the server declares

    • title: Get payment actions
    • readOnlyHint: true
  • checkout_get_reportGet the metadata of a specific report (including its downloadable files) by id 'rpt_...'.1 finding

    Why it is in this group

    • The name "checkout_get_report" says "checkout": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "checkout_get_report" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "checkout_get_report" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Get the metadata of a specific report (including its downloadable files) by id 'rpt_...'. Checkout.com: GET /reports/{id}.

    Annotations the server declares

    • title: Get report
    • readOnlyHint: true
  • checkout_list_paymentsList your business's payments that match a given reference.1 finding

    Why it is in this group

    • The name "checkout_list_payments" says "checkout": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "checkout_list_payments" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "checkout_list_payments" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    List your business's payments that match a given reference. Checkout.com: GET /payments (query parameters). For richer filtering use checkout_search_payments.

    Annotations the server declares

    • title: List payments by reference
    • readOnlyHint: true
  • checkout_list_reportsList the reports available on your account (settlement, payments, etc.) and their details.1 finding

    Why it is in this group

    • The name "checkout_list_reports" says "checkout": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "checkout_list_reports" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "checkout_list_reports" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    List the reports available on your account (settlement, payments, etc.) and their details. Checkout.com: GET /reports.

    Annotations the server declares

    • title: List reports
    • readOnlyHint: true
  • checkout_search_paymentsSearch payments using flexible query filters (this is a READ — it queries, it does not mutate).1 finding

    Why it is in this group

    • The name "checkout_search_payments" says "checkout": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "checkout_search_payments" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "checkout_search_payments" says "checkout": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Search payments using flexible query filters (this is a READ — it queries, it does not mutate). Checkout.com: POST /payments/search. Pass a `query` filter object and/or paging fields.

    Annotations the server declares

    • title: Search payments
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:34 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 18 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://checkoutcom.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://checkoutcom.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

12 warn
  • The server marks "checkout_get_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_get_payment" says "checkout": a word for a change.

    What this check looks for
  • The server marks "checkout_list_payments" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_list_payments" says "checkout": a word for a change.

    What this check looks for
  • The server marks "checkout_search_payments" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_search_payments" says "checkout": a word for a change.

    What this check looks for
  • The server marks "checkout_get_payment_actions" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_get_payment_actions" says "checkout": a word for a change.

    What this check looks for
  • The server marks "checkout_get_payment_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_get_payment_link" says "checkout": a word for a change.

    What this check looks for
  • The server marks "checkout_get_customer" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_get_customer" says "checkout": a word for a change.

    What this check looks for
Show 6 more findings
  • The server marks "checkout_get_instrument" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_get_instrument" says "checkout": a word for a change.

    What this check looks for
  • The server marks "checkout_list_disputes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_list_disputes" says "checkout": a word for a change.

    What this check looks for
  • The server marks "checkout_get_dispute" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_get_dispute" says "checkout": a word for a change.

    What this check looks for
  • The server marks "checkout_list_reports" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_list_reports" says "checkout": a word for a change.

    What this check looks for
  • The server marks "checkout_get_report" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_get_report" says "checkout": a word for a change.

    What this check looks for
  • The server marks "checkout_get_forex_rates" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "checkout_get_forex_rates" says "checkout": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 18 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://checkoutcom.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://checkoutcom.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__checkoutcom__checkout_get_payment",
      "mcp__checkoutcom__checkout_list_payments",
      "mcp__checkoutcom__checkout_search_payments",
      "mcp__checkoutcom__checkout_get_payment_actions",
      "mcp__checkoutcom__checkout_get_payment_link",
      "mcp__checkoutcom__checkout_get_customer",
      "mcp__checkoutcom__checkout_get_instrument",
      "mcp__checkoutcom__checkout_list_disputes",
      "mcp__checkoutcom__checkout_get_dispute",
      "mcp__checkoutcom__checkout_list_reports",
      "mcp__checkoutcom__checkout_get_report",
      "mcp__checkoutcom__checkout_get_forex_rates"
    ],
    "deny": [
      "mcp__checkoutcom__checkout_create_payment",
      "mcp__checkoutcom__checkout_capture_payment",
      "mcp__checkoutcom__checkout_refund_payment",
      "mcp__checkoutcom__checkout_void_payment",
      "mcp__checkoutcom__checkout_create_payment_link",
      "mcp__checkoutcom__checkout_create_customer"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as checkoutcom. Review it before you use it.

Capability tags behind 1 rule
  • mcp__checkoutcom__checkout_list_disputes outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/checkoutcom/verify?hash=6539c3d709eee354c0691f16efdc2ca924979071948f41303bce37dac9e0a311" | jq -e '.changed == false'

Pinned hash 6539c3d709ee, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/checkoutcom/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/checkoutcom
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/checkoutcom.svg)](https://radar.anlyon.com/servers/io.usefulapi/checkoutcom)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Checkout.com MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Checkout.com MCP by usefulapi safe?

No scan can promise that. What its definitions show: 18 tools, 18 of which can change, send or delete something, and 12 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Checkout.com MCP by usefulapi delete data?

Yes. 6 tools can delete, cancel or revoke something: checkout_create_payment, checkout_capture_payment, checkout_refund_payment, checkout_void_payment, checkout_create_payment_link and checkout_create_customer.

Can the Checkout.com MCP by usefulapi do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: checkout_list_disputes.

What tools does the Checkout.com MCP by usefulapi have?

18 tools: 6 destructive, 1 irreversible, 11 write. checkout_create_payment, checkout_capture_payment, checkout_refund_payment, checkout_void_payment, checkout_create_payment_link, checkout_create_customer, checkout_list_disputes, checkout_get_payment and 10 more.

Does the Checkout.com MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Checkout.com MCP by usefulapi send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): checkout_list_disputes.

Has the Checkout.com MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.