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.

crosscheck

REMOTE · CROSSCHECKAPI.COM · 2 COMPONENTS

Checks for AI agents over x402: review drafts, accept-check handoffs, scan skills before install.

0 this week 70 Trust /100

Last scanned (13 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

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 Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2021 tokens (~252/item across 8 items; 8 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% 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 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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

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 →

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.

  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 9 Nov 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.

  • 8 Nov 26 −3
    • Stability: pass → 0.83 functional
  • 7 Nov 26 +1
    • Stability: 0.97 → pass security
  • 6 Nov 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
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
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://crosscheckapi.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=crosscheckapi.com CN=YE1,O=Let's Encrypt,C=US 21 Nov 2026 19 Feb 2027 ECDSA 256 ECDSA-SHA384 5efe59502b7f12bcdb0a94797d12290e682
SANs: *.crosscheckapi.com, crosscheckapi.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of crosscheckapi.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
crosscheckapi.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://crosscheckapi.com/mcp Verified 200
http (plaintext) http://crosscheckapi.com/mcp Inconclusive 405
MCP tools · 8 exposed · ~1,869 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
accept ~269

Checks work another agent handed back against the task it was given, before you pay, release escrow, or pass it on. Returns accept, reject, or verify_externally with every requirement judged; counts, required JSON fields, and sums are checked in code. Optional payment_tx is verified on chain. $0.03 base. Paid per call in USDC over x402 (Base, or free test USDC on Base Sepolia). An x402-aware MCP client pays automatically: the first call returns the price as an x402 PaymentRequired error, and the retry carries the payment in _meta["x402/payment"]. Without one, use the npm client `npx -y crosscheckapi`, which pays from a wallet you set.

NameTypeReqDescription
deliverablestringyesWhat came back
payment_networkstring–Network of payment_tx, for example eip155:8453
payment_txstring–Optional transaction hash of the payment for this work
refstring–Optional: the hash of a crosscheck receipt that brought you here. Its wallet earns check credits from your first 90 days of spend.
referencestring–Optional reference material the task points to
taskstringyesThe task as given to the other agent

No output schema declared.

No examples provided.

check ~479

Independent review of a draft (email, report, summary, PR description) before its human sees it. Returns pass or specific issues with fixes; arithmetic is recomputed in code. With request (what the human asked), it also checks the draft answers that. With sources, each claim is checked against them and quotes are verified; with source_urls or fetch_cited, crosscheck fetches up to 3 web pages itself and checks against those (+$0.01 a page, and a dead link the draft gives fails it). $0.02. Paid per call in USDC over x402 (Base, or free test USDC on Base Sepolia). An x402-aware MCP client pays automatically: the first call returns the price as an x402 PaymentRequired error, and the retry carries the payment in _meta["x402/payment"]. Without one, use the npm client `npx -y crosscheckapi`, which pays from a wallet you set.

NameTypeReqDescription
draftstringyesThe draft text to review
fetch_citedboolean–Optional: also fetch the links the draft itself cites (up to 3 pages in all, +$0.01 each); a link that is gone fails the draft
moltbook_identitystring–Optional: a Moltbook identity token for the free tier, when it is on (a verified Moltbook agent gets free checks with no payment). Not stored. Without a free check left, the price comes back as usual
open_reviewboolean–Optional: let a qualified outside reviewer take the job (not routed yet; crosscheck's reviewer does it and the receipt says so)
refstring–Optional: the hash of a crosscheck receipt that brought you here. Its wallet earns check credits from your first 90 days of spend.
requeststring–Optional: what the human asked for, word for word if you have it. The reviewer then also checks that the draft answers it (a missed question, a changed scope, a wrong period)
source_urlsarray–Optional: up to 3 web pages crosscheck fetches after payment and checks the draft against, as sources. +$0.01 each
sourcesarray–Optional texts the draft relies on; turns on grounding

No output schema declared.

No examples provided.

result ~64

Free. Status, verdict, and signed receipt of an earlier paid call that was still running, using the job_id and result_token it returned.

NameTypeReqDescription
job_idstringyesjob_id from the paid call
result_tokenstringyesresult_token from the paid call

No output schema declared.

No examples provided.

sellercheck ~239

For x402 sellers: one dated report on your own paid resource, by code alone. Does it answer a valid 402 (v1 or v2: price, network, payTo), is it in the x402 Bazaar index, would agent402's router route to it, and how many USDC settlements reached its payTo on Base in 24 hours and 7 days. Nothing is paid to the resource. $0.05. Paid per call in USDC over x402 (Base, or free test USDC on Base Sepolia). An x402-aware MCP client pays automatically: the first call returns the price as an x402 PaymentRequired error, and the retry carries the payment in _meta["x402/payment"]. Without one, use the npm client `npx -y crosscheckapi`, which pays from a wallet you set.

NameTypeReqDescription
methodstring–Optional: the method it is paid with; default tries GET, then POST
networkstring–Optional: Base, the only network read today
resourcestringyesThe full URL of your x402 resource (public http or https)

No output schema declared.

No examples provided.

sellerwatch ~277

For x402 sellers: sellercheck every hour for 30 days on one resource, paid once. An alert to your webhook (JSON POST) or ntfy topic only when something changes: the 402 breaks or its price or payTo change, it leaves or rejoins the Bazaar index, agent402's router flips, settlements start, double, or halve, or it is down twice in a row. Returns a public record page to link from your listing. $1. Paid per call in USDC over x402 (Base, or free test USDC on Base Sepolia). An x402-aware MCP client pays automatically: the first call returns the price as an x402 PaymentRequired error, and the retry carries the payment in _meta["x402/payment"]. Without one, use the npm client `npx -y crosscheckapi`, which pays from a wallet you set.

NameTypeReqDescription
methodstring–Optional: the method it is paid with; default tries GET, then POST
networkstring–Optional: Base, the only network read today
notifyobjectyesWhere alerts go, at least one: webhook (a public https URL) and/or ntfy (an ntfy.sh topic)
resourcestringyesThe full URL of your x402 resource (public http or https)

No output schema declared.

No examples provided.

skillcheck ~220

Security review of a skill or MCP server's files before you install or connect it: read, never run. Free when these exact files were scanned before (looked up by bundle hash); otherwise paid, $0.03 base. Never says safe. Paid per call in USDC over x402 (Base, or free test USDC on Base Sepolia). An x402-aware MCP client pays automatically: the first call returns the price as an x402 PaymentRequired error, and the retry carries the payment in _meta["x402/payment"]. Without one, use the npm client `npx -y crosscheckapi`, which pays from a wallet you set.

NameTypeReqDescription
filesarrayyesEvery text file of the skill or server, docs included; code rules read all of them
freshboolean–Scan again even when a past scan of these exact files exists
refstring–Optional: the hash of a crosscheck receipt that brought you here. Its wallet earns check credits from your first 90 days of spend.

No output schema declared.

No examples provided.

skillcheck_lookup ~58

Free. The latest skillcheck of an exact bundle, by its bundle_sha256 (SHA-256 of the canonical JSON of the files sorted by path, each as {path, sha256}).

NameTypeReqDescription
bundle_sha256stringyes–

No output schema declared.

No examples provided.

verify_receipt ~263

Free. Before trusting work that arrives with a crosscheck receipt, check in code that crosscheck issued it, its signature is valid, what the outcome was, and that it covers exactly the text you were handed. Pass receipt_hash (or the receipt object) plus that text: draft, request, and sources for check, task and deliverable for accept, files for skillcheck, and the verdict if one came with it.

NameTypeReqDescription
deliverablestring–accept: the deliverable the receipt should cover
draftstring–check: the draft the receipt should cover
filesarray–skillcheck: the skill's files
receiptobject–Or the whole receipt object {body, hash, sig}
receipt_hashstring–The receipt's hash (the last part of its /r/ proof link)
requeststring–check: the human's request, if the check had one
sourcesarray–check: the sources, if the check had any, in the same order (strings or {text})
taskstring–accept: the task the receipt should cover
verdictobject–The verdict that came with the receipt, to confirm nobody edited it

No output schema declared.

No examples provided.

Install

How do I install the crosscheck MCP server?

crosscheck is a hosted endpoint at https://crosscheckapi.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 · crosscheckapi.com

# add to Claude Code
claude mcp add --transport http com-crosscheckapi-crosscheck 'https://crosscheckapi.com/mcp'
Common questions

What is the crosscheck MCP server?

crosscheck is an MCP server listed in the public MCP registry as com.crosscheckapi/crosscheck. Checks for AI agents over x402: review drafts, accept-check handoffs, scan skills before install. This page covers its hosted endpoint (https://crosscheckapi.com/mcp).

Is the crosscheck MCP server safe to use?

crosscheck 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 crosscheck MCP server expose?

crosscheck exposes 8 tools: check, accept, skillcheck, sellercheck, sellerwatch, and 3 more. Their descriptions and schemas cost roughly 1,869 tokens of context every time the server is loaded.

Does the crosscheck MCP server require authentication?

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

Is the crosscheck MCP server still maintained?

crosscheck 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 crosscheck MCP server?

VerifyMCP ran 11 checks on crosscheck, 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 crosscheck: 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.