io.usefulapi/checkoutcom
REMOTE · CHECKOUTCOM.USEFULAPI.IO · SCANNED OCT 4
Read Checkout.com payments, disputes, reports and payouts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 429, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 429. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.usefulapi/checkoutcom MCP server?
io.usefulapi/checkoutcom is a hosted endpoint at https://checkoutcom.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · checkoutcom.usefulapi.io
claude mcp add --transport http io-usefulapi-checkoutcom 'https://checkoutcom.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-checkoutcom": {
"url": "https://checkoutcom.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-checkoutcom": {
"type": "http",
"url": "https://checkoutcom.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-checkoutcom] url = "https://checkoutcom.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-checkoutcom": {
"type": "remote",
"url": "https://checkoutcom.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-checkoutcom --url 'https://checkoutcom.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-checkoutcom:
url: "https://checkoutcom.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-checkoutcom": {
"Transport": "http",
"Url": "https://checkoutcom.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-checkoutcom -t streamable-http -u 'https://checkoutcom.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-checkoutcom": {
"type": "http",
"url": "https://checkoutcom.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Oct 26 −58
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Oct 26 +48
- Authorization: unverified → pass ▲ security
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 30 Sept 26 +10
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 29 Sept 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://checkoutcom.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of checkoutcom.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 429 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://checkoutcom.usefulapi.io/mcp | HTTP error | 429 | |
| http (plaintext) | http://checkoutcom.usefulapi.io/mcp | Inconclusive | 429 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
checkout_capture_payment Capture payment ~141
CAPTURES a previously authorized payment — this MOVES MONEY: it settles the (full or partial) authorized amount. Checkout.com: POST /payments/{id}/captures.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | – | Amount to capture in MINOR units (defaults to the full authorized amount). |
| id | string | yes | Payment id to capture, e.g. 'pay_...'. Required. |
| idempotency_key | string | – | Idempotency key — sent as the Cko-Idempotency-Key header. |
| metadata | object | – | Arbitrary key/value metadata to attach to the capture. |
| reference | string | – | Your reference for the capture. |
No output schema declared.
No examples provided.
checkout_create_customer Create customer ~162
CREATES a customer record (which saved instruments and future payments can be attached to). This ADDS data to your account. Checkout.com: POST /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| default | string | – | Id of the default instrument ('src_...') for this customer. |
| string | yes | Customer email address (required, must be unique on the account). | |
| idempotency_key | string | – | Idempotency key — sent as the Cko-Idempotency-Key header. |
| metadata | object | – | Arbitrary key/value metadata to attach to the customer. |
| name | string | – | Customer full name. |
| phone | object | – | Phone object, e.g. { country_code: '+1', number: '4155552671' }. |
No output schema declared.
No examples provided.
checkout_create_payment Create payment ~398
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_...' }.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | yes | Amount in the currency's MINOR units (e.g. 1000 = $10.00; 0 = card verification). Required. |
| capture | boolean | – | If true (default for card), capture immediately; if false, authorize only. |
| currency | string | yes | 3-letter ISO currency code, e.g. 'USD', 'GBP', 'EUR'. Required. |
| customer | object | – | Customer object to associate/create, e.g. { id:'cus_...' } or { email, name }. |
| description | string | – | Description shown on the customer's statement / for your records. |
| idempotency_key | string | – | Idempotency key — sent as the Cko-Idempotency-Key header to safely retry. |
| metadata | object | – | Arbitrary key/value metadata to attach to the payment. |
| payment_type | string | – | Payment type, e.g. 'Regular', 'Recurring', 'MOTO'. |
| processing_channel_id | string | – | Processing channel id ('pc_...') to route the payment through. |
| reference | string | – | Your reference for the payment (e.g. order id). |
| source | object | yes | Payment source object. Required. E.g. { type:'token', token:'tok_...' }, { type:'id', id:'src_...' }, or { type:'customer', id:'cus_...' }. |
No output schema declared.
No examples provided.
checkout_create_payment_link Create payment link ~268
CREATES a hosted Payment Link the customer can pay through — this sets up a way to COLLECT MONEY. Checkout.com: POST /payment-links. Returns a URL to share with the customer.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | yes | Amount in MINOR units (e.g. 1000 = $10.00). Required. |
| billing | object | – | Billing object, e.g. { address: { country: 'GB' } }. |
| currency | string | yes | 3-letter ISO currency code, e.g. 'USD'. Required. |
| customer | object | – | Customer object, e.g. { email, name }. |
| description | string | – | Description shown to the customer on the payment page. |
| expires_in | integer | – | Seconds until the link expires. |
| idempotency_key | string | – | Idempotency key — sent as the Cko-Idempotency-Key header. |
| metadata | object | – | Arbitrary key/value metadata to attach to the payment link. |
| products | array | – | Line items, each e.g. { name, quantity, unit_price }. |
| reference | string | – | Your reference for the payment link (e.g. order id). |
| return_url | string | – | URL the customer is returned to after paying. |
No output schema declared.
No examples provided.
checkout_get_customer Get customer ~61
Get a customer's details (email, name, phone, saved instruments) by id 'cus_...' or by email. Checkout.com: GET /customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Customer id ('cus_...') or the customer's email address. |
No output schema declared.
No examples provided.
checkout_get_dispute Get dispute ~67
Get all the details of a single dispute (reason code, amount, deadline, evidence status) by id 'dsp_...'. Checkout.com: GET /disputes/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Dispute id, e.g. 'dsp_...'. |
No output schema declared.
No examples provided.
checkout_get_forex_rates Get forex rates ~138
Get the indicative foreign-exchange rates Checkout.com uses (e.g. for card payouts). Checkout.com: GET /forex/rates.
| Name | Type | Req | Description |
|---|---|---|---|
| currency_pairs | string | yes | Comma-separated currency pairs, e.g. 'GBPEUR,USDNOK' (required, up to 20 pairs). |
| processing_channel_id | string | – | Processing channel id ('pc_...') to scope the rates. |
| product | string | – | Product the rates are for, e.g. 'card_payouts'. |
| source | string | yes | Rate source, e.g. 'visa' or 'mastercard' (required). |
No output schema declared.
No examples provided.
checkout_get_instrument Get instrument ~60
Get the details of a saved payment instrument (tokenized card / bank account) by id 'src_...'. Checkout.com: GET /instruments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instrument id, e.g. 'src_...'. |
No output schema declared.
No examples provided.
checkout_get_payment Get payment ~81
Get the full details of a payment (or payment session) by its id, e.g. 'pay_...'. Checkout.com: GET /payments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Payment id, e.g. 'pay_mbabizu24mvu3mela5njyhpit4' (or a 'sid_' payment session id). |
No output schema declared.
No examples provided.
checkout_get_payment_actions Get payment actions ~61
List all the actions (authorization, capture, refund, void, etc.) associated with a payment, latest first. Checkout.com: GET /payments/{id}/actions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Payment id, e.g. 'pay_...'. |
No output schema declared.
No examples provided.
checkout_get_payment_link Get payment link ~74
Retrieve the details and status of a Payment Link by its id, e.g. 'pl_...'. Checkout.com: GET /payment-links/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Payment Link id, e.g. 'pl_ok1itj8ykm3eyk1toywr6uwlwe'. |
No output schema declared.
No examples provided.
checkout_get_report Get report ~57
Get the metadata of a specific report (including its downloadable files) by id 'rpt_...'. Checkout.com: GET /reports/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Report id, e.g. 'rpt_...'. |
No output schema declared.
No examples provided.
checkout_list_disputes List disputes ~202
List disputes (chargebacks) against your business, most-recently-modified first, with optional filters. Checkout.com: GET /disputes.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_ids | string | – | Comma-separated sub-entity ids to filter by (for platforms). |
| from | string | – | Only disputes last modified on/after this ISO-8601 timestamp. |
| limit | integer | – | Maximum number of disputes to return (default 20). |
| payment_id | string | – | Filter to disputes for a specific payment id ('pay_...'). |
| skip | integer | – | Number of disputes to skip (pagination offset). |
| statuses | string | – | Comma-separated dispute statuses to filter by, e.g. 'evidence_required,arbitration'. |
| this_channel_only | boolean | – | If true, only return disputes for the authenticating channel. |
| to | string | – | Only disputes last modified on/before this ISO-8601 timestamp. |
No output schema declared.
No examples provided.
checkout_list_payments List payments by reference ~81
List your business's payments that match a given reference. Checkout.com: GET /payments (query parameters). For richer filtering use checkout_search_payments.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of payments to return. |
| reference | string | – | Return only payments with this reference. |
| skip | integer | – | Number of payments to skip (pagination offset). |
No output schema declared.
No examples provided.
checkout_list_reports List reports ~106
List the reports available on your account (settlement, payments, etc.) and their details. Checkout.com: GET /reports.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only reports created on/after this ISO-8601 timestamp. |
| created_before | string | – | Only reports created on/before this ISO-8601 timestamp. |
| entity_id | string | – | Filter reports to a specific entity id (for platforms). |
| limit | integer | – | Maximum number of reports to return. |
No output schema declared.
No examples provided.
checkout_refund_payment Refund payment ~138
REFUNDS a captured payment — this MOVES MONEY BACK to the customer (full or partial). Checkout.com: POST /payments/{id}/refunds.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | – | Amount to refund in MINOR units (defaults to the full captured amount). |
| id | string | yes | Payment id to refund, e.g. 'pay_...'. Required. |
| idempotency_key | string | – | Idempotency key — sent as the Cko-Idempotency-Key header. |
| metadata | object | – | Arbitrary key/value metadata to attach to the refund. |
| reference | string | – | Your reference for the refund. |
No output schema declared.
No examples provided.
checkout_search_payments Search payments ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results to return. |
| pagination | object | – | Cursor pagination object (e.g. { after, before }) as returned in previous responses. |
| query | object | – | Search filter object, e.g. { reference, id, status, currency, amount, from, to }. |
No output schema declared.
No examples provided.
checkout_void_payment Void payment ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Payment id to void, e.g. 'pay_...'. Required. |
| idempotency_key | string | – | Idempotency key — sent as the Cko-Idempotency-Key header. |
| metadata | object | – | Arbitrary key/value metadata to attach to the void. |
| reference | string | – | Your reference for the void. |
No output schema declared.
No examples provided.
What is the io.usefulapi/checkoutcom MCP server?
io.usefulapi/checkoutcom is an MCP server listed in the public MCP registry as io.usefulapi/checkoutcom. Read Checkout.com payments, disputes, reports and payouts. This page covers its hosted endpoint (https://checkoutcom.usefulapi.io/mcp).
Is the io.usefulapi/checkoutcom MCP server safe to use?
io.usefulapi/checkoutcom scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/checkoutcom MCP server expose?
io.usefulapi/checkoutcom exposes 18 tools: checkout_get_payment, checkout_list_payments, checkout_search_payments, checkout_get_payment_actions, checkout_get_payment_link, and 13 more. Their descriptions and schemas cost roughly 2,335 tokens of context every time the server is loaded.
Does the io.usefulapi/checkoutcom MCP server require authentication?
Its publisher declares no required credentials for io.usefulapi/checkoutcom. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.usefulapi/checkoutcom MCP server still maintained?
io.usefulapi/checkoutcom is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.