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.

Checkout Guard — pre-purchase check for shops, payment links and paid APIs

REMOTE · ANGEL.OROBOROS-DESIGN.COM

Pre-purchase check for any shop, checkout or payment link, paid API or x402 endpoint.

+3 this week 65 Trust /100

Last scanned (12 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

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 Security63
Transport & Reachability100
Schema Quality & AI Usability52
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 826 tokens (~413/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 79% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

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.

  • 20 Nov 26 +1
    • Tool “preflight” rewrote its description, which is the text the model reads security
    • “preflight” added an optional parameter “agent” cosmetic
  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “buy_pack_with_card” rewrote its description, which is the text the model reads security
    • Tool “preflight” rewrote its description, which is the text the model reads security
    • Schema quality: 335 → 386 ▼ functional
    • Tool coverage: 67% → 77% ▲ functional
    • “preflight” added an optional parameter “budget” cosmetic
    • “preflight” added an optional parameter “currency” cosmetic
    • “preflight” added an optional parameter “need” cosmetic
    • “preflight” added an optional parameter “region” cosmetic
    • “buy_pack_with_card” reworded the description of “email” cosmetic
    • “preflight” reworded the description of “bundle_token” cosmetic
    • “preflight” reworded the description of “payer_address” cosmetic
    • “preflight” reworded the description of “url” cosmetic
    • “preflight” made “url” optional cosmetic
    • Tool “buy_pack_with_card” changed its title: TradeSignal: pack by card → Angel: 5,000 calls by card cosmetic
    • Tool “preflight” changed its title: Pre-purchase check for any shop, checkout link, payment page, API or x402 endpoint → Pre-purchase check for any shop, checkout link, payment page, API or x402 endpoint — or for a need: find the offer and check it cosmetic
  • 18 Nov 26 +1

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

  • 16 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “buy_pack_with_card” rewrote its description, which is the text the model reads security
    • Tool “preflight” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 62

    First indexed and scored.

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 21 Nov 2026 · Probed https://angel.oroboros-design.com/mcp/checkout-guard

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.oroboros-design.com CN=YR2,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 RSA 2048 SHA256-RSA 5c407b368cf93bd9f2f03db9f58a77f6c9f
SANs: *.oroboros-design.com, oroboros-design.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of angel.oroboros-design.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
oroboros-design.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
Header Value
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://angel.oroboros-design.com/mcp/checkout-guard Verified 200
http (plaintext) http://angel.oroboros-design.com/mcp/checkout-guard HTTPS enforced 308 https://angel.oroboros-design.com/mcp/checkout-guard
MCP tools · 2 exposed · ~673 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
buy_pack_with_card ~118

For businesses without USDC: 5,000 calls €9.00, one-time, 90 days, businesses only, paid in EUR by card or Link. Returns checkout_url for a person to open; the checkout asks for the company or freelance name. After payment the success page (Accept: application/json) returns the key, and it is e-mailed. After: any tool with bundle_token.

NameTypeReqDescription
callsinteger––
emailstring–Where the key is sent (optional; Stripe asks otherwise).

No output schema declared.

No examples provided.

preflight ~555

Before an agent buys, pays or hires: send url (shop, checkout, payment link, API or x402 endpoint), need (what to buy in plain words; Angel takes the pick from the open sea at mareliberum.dev and checks it) or agent (mare:… resident: its trust score). One unpaid request each: TLS, domain age, look-alikes, redirects, payment provider, card fields, text aimed at agents and, for x402, USDC contract, payTo and price traps. Verdict pay, caution or do_not_pay, risk_score, reasons. Free with a key (500 calls) or 5 calls a day without one; then 0.02 USDC per call via x402, or 1 call from a key. After: input-guard on the page text you will act on (the result's next field has the exact call).

NameTypeReqDescription
agentstring–instead of a url: a resident of the open sea (mareliberum.dev) you want to pay or hire; Angel returns its trust score 0-100 from its work, notes, seals and own endpoint
budgetnumber–with need: highest price
bundle_tokenstring–Your key instead of paying per call: free (500 calls, POST /key) or bought by card. The connection header X-Bundle-Token works too.
currencystring–with need: currency of the budget
max_price_usdnumber––
methodstring––
needstring–instead of a url: what your user wants to buy, in plain words (sizes, budget, place included), e.g. "trail running shoes size 44 under 150 EUR, ships to Germany". Angel takes the pick from the open s…
partner_linkboolean–default true: on verdict pay for a shop with an affiliate program, the answer adds partner_link (same merchant, disclosed: Angel may earn a commission, merchant sets the price); false omits it
payer_addressstring–Wallet you pay from (optional; the x402 price is the same for every address).
payment_txstring–Hash of a USDC transfer on Base to payTo (≥ the price, ≤ 72 h old) instead of an x402 signature.
regionstring–with need: country code or name
urlstring–the shop, checkout or payment link, API or x402 endpoint to check (public https domain, port 443). Send url or need.

No output schema declared.

No examples provided.

Install

How do I install the Checkout Guard — pre-purchase check for shops, payment… MCP server?

Checkout Guard — pre-purchase check for shops, payment… is a hosted endpoint at https://angel.oroboros-design.com/mcp/checkout-guard, 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 · angel.oroboros-design.com

# add to Claude Code
claude mcp add --transport http com-oroboros-design-angel-checkout-guard 'https://angel.oroboros-design.com/mcp/checkout-guard'
Common questions

What is the Checkout Guard — pre-purchase check for shops, payment… MCP server?

Checkout Guard — pre-purchase check for shops, payment… is an MCP server listed in the public MCP registry as com.oroboros-design.angel/checkout-guard. Pre-purchase check for any shop, checkout or payment link, paid API or x402 endpoint. This page covers its hosted endpoint (https://angel.oroboros-design.com/mcp/checkout-guard).

Is the Checkout Guard — pre-purchase check for shops, payment… MCP server safe to use?

Checkout Guard — pre-purchase check for shops, payment… scores 65 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 Checkout Guard — pre-purchase check for shops, payment… MCP server expose?

Checkout Guard — pre-purchase check for shops, payment… exposes 2 tools: preflight, buy_pack_with_card. Their descriptions and schemas cost roughly 673 tokens of context every time the server is loaded.

Does the Checkout Guard — pre-purchase check for shops, payment… MCP server require authentication?

No. We connected to Checkout Guard — pre-purchase check for shops, payment… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Checkout Guard — pre-purchase check for shops, payment… MCP server still maintained?

Checkout Guard — pre-purchase check for shops, payment… 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 Checkout Guard — pre-purchase check for shops, payment… MCP server?

VerifyMCP ran 12 checks on Checkout Guard — pre-purchase check for shops, payment…, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Checkout Guard — pre-purchase check for shops, payment…: Authorization. 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.