Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Agent Checkout

REMOTE · AGENTCHECKOUTAPI.COM · SCANNED SEP 28

AI shopping gateway for product search, inventory, carts, and merchant-hosted checkout.

+3 this week 69 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 694 tokens (~86/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Agent Checkout MCP server?

Agent Checkout is a hosted endpoint at https://agentcheckoutapi.com/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 · agentcheckoutapi.com

# add to Claude Code
claude mcp add --transport http com-agentcheckoutapi-agent-checkout 'https://agentcheckoutapi.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-agentcheckoutapi-agent-checkout": {
      "url": "https://agentcheckoutapi.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-agentcheckoutapi-agent-checkout": {
      "type": "http",
      "url": "https://agentcheckoutapi.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-agentcheckoutapi-agent-checkout]
url = "https://agentcheckoutapi.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-agentcheckoutapi-agent-checkout": {
      "type": "remote",
      "url": "https://agentcheckoutapi.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-agentcheckoutapi-agent-checkout --url 'https://agentcheckoutapi.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-agentcheckoutapi-agent-checkout:
    url: "https://agentcheckoutapi.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-agentcheckoutapi-agent-checkout": {
      "Transport": "http",
      "Url": "https://agentcheckoutapi.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-agentcheckoutapi-agent-checkout -t streamable-http -u 'https://agentcheckoutapi.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-agentcheckoutapi-agent-checkout": {
      "type": "http",
      "url": "https://agentcheckoutapi.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 28 Sept 2026 · Probed https://agentcheckoutapi.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentcheckoutapi.com CN=WE1,O=Google Trust Services,C=US 29 Aug 2026 27 Nov 2026 ECDSA 256 ECDSA-SHA256 40108e5cede8804013f0d4607ea2ad8c
SANs: agentcheckoutapi.com, *.agentcheckoutapi.com
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 agentcheckoutapi.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
agentcheckoutapi.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentcheckoutapi.com/mcp Verified 200
http (plaintext) http://agentcheckoutapi.com/mcp Inconclusive 405
MCP tools · 8 exposed · ~518 tokens

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 →

Tool Tokens
add_to_cart ~75

Add another selected product variant to an existing Agent Checkout cart. Use when the user explicitly wants another item or quantity added to an existing cart. This does not charge the buyer.

NameTypeReqDescription
cart_idstringyes–
quantityinteger––
site_slugstringyes–
variant_idstringyes–

No output schema declared.

No examples provided.

check_inventory ~52

Check whether a selected product variant is currently sellable and available. Use when availability matters or immediately before adding a selected variant to a cart.

NameTypeReqDescription
site_slugstringyes–
variant_idstringyes–

No output schema declared.

No examples provided.

create_cart ~75

Create a new Agent Checkout-attributed cart with a selected product variant. Use only after the user has chosen a specific product or clearly asked to add/buy it. This prepares the purchase but does not charge the buyer.

NameTypeReqDescription
quantityinteger––
site_slugstringyes–
variant_idstringyes–

No output schema declared.

No examples provided.

create_checkout ~83

Prepare the final buyer handoff by returning the merchant-hosted HTTPS checkout URL. Use when the user has a cart and clearly wants to proceed to checkout or purchase. Always surface checkoutUrl to the human buyer. Agent Checkout never collects raw card details and this tool does not itself charge the buyer.

NameTypeReqDescription
cart_idstringyes–
site_slugstringyes–

No output schema declared.

No examples provided.

get_cart ~49

Read the current Agent Checkout cart contents and totals. Use to review or confirm the cart before handing the buyer off to checkout.

NameTypeReqDescription
cart_idstringyes–
site_slugstringyes–

No output schema declared.

No examples provided.

get_product ~56

Get detailed product and variant information after search_products identifies a product and merchant. Use before purchase when the user needs details, options, price, or variant information.

NameTypeReqDescription
product_idstringyes–
site_slugstringyes–

No output schema declared.

No examples provided.

search_catalog ~45

Legacy alias for search_products. Search purchasable products across participating merchants. Prefer search_products for new shopping requests.

NameTypeReqDescription
firstinteger––
querystringyes–

No output schema declared.

No examples provided.

search_products ~83

Primary shopping entry point. Use when a user wants to find, browse, compare, recommend, price-check, check availability of, shop for, or buy a physical product. Searches purchasable products across merchants participating in the Agent Checkout network. The user does not need to mention Agent Checkout by name.

NameTypeReqDescription
firstinteger––
querystringyes–

No output schema declared.

No examples provided.

Common questions

What is the Agent Checkout MCP server?

Agent Checkout is an MCP server listed in the public MCP registry as com.agentcheckoutapi/agent-checkout. AI shopping gateway for product search, inventory, carts, and merchant-hosted checkout. This page covers its hosted endpoint (https://agentcheckoutapi.com/mcp).

Is the Agent Checkout MCP server safe to use?

Agent Checkout scores 69 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 Agent Checkout MCP server expose?

Agent Checkout exposes 8 tools: search_products, search_catalog, get_product, check_inventory, create_cart, and 3 more. Their descriptions and schemas cost roughly 518 tokens of context every time the server is loaded.

Does the Agent Checkout MCP server require authentication?

No. We connected to Agent Checkout without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Agent Checkout MCP server still maintained?

Agent Checkout is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.