Agent Checkout
REMOTE · AGENTCHECKOUTAPI.COM
AI shopping gateway for product search, inventory, carts, and merchant-hosted checkout.
Available components
Last scanned (18 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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 fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 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
- 1 Oct 26 0
- Stability: 0.97 → pass security
- 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
- 25 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
- 2 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_checkout” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 1 Sept 26 0
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 21 Nov 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 | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | fd342282b2ba4a7132ee958779f1c8e |
| 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. | DS published | 19718 | 13 | Verified |
| agentcheckoutapi.com. | No DS | 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 |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | – |
| quantity | integer | – | – |
| site_slug | string | yes | – |
| variant_id | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site_slug | string | yes | – |
| variant_id | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| quantity | integer | – | – |
| site_slug | string | yes | – |
| variant_id | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | – |
| site_slug | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | – |
| site_slug | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | – |
| site_slug | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| first | integer | – | – |
| query | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| first | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
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
claude mcp add --transport http com-agentcheckoutapi-agent-checkout 'https://agentcheckoutapi.com/mcp'
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 70 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Agent Checkout MCP server?
VerifyMCP ran 11 checks on Agent Checkout, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Agent Checkout: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.