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.

Checkbooth

REMOTE · CHECKBOOTH.DEV

Independent signed math checks for AI agents: PASS or FAIL plus a link anyone can open. Free beta.

Available components

+3 this week 70 Trust /100

Last scanned (18 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Testing and QA

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • 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
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 850 tokens (~70/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 10% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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 (13)

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

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

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 10 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 65

    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://checkbooth.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=checkbooth.dev CN=WE1,O=Google Trust Services,C=US 8 Nov 2026 7 Feb 2027 ECDSA 256 ECDSA-SHA256 64f47c06c34f067b13dca16baec1280b
SANs: checkbooth.dev
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 checkbooth.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
checkbooth.dev. 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
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://checkbooth.dev/mcp Verified 200
http (plaintext) http://checkbooth.dev/mcp HTTPS enforced 301 https://checkbooth.dev/mcp
MCP tools · 12 exposed · ~793 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
audit_text_rounding ~59

Paste text (up to 8,000 characters). We find every inline "arithmetic = number" claim and recompute it at the stated digits. Signed receipt. We keep only hashes of your text.

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

discover_capabilities ~81

List the whole Checkbooth tool chest with honest status tags (BUILT, COMING, ON REQUEST). Filter by words, family or status. Free.

NameTypeReqDescription
familystring––
include_stagedboolean–Default false: only tools you can call right now.
querystring––
statusstring––

No output schema declared.

No examples provided.

issue_sandbox_key ~31

Get a free capped beta key (cb_test_...). Shown once; we keep only its hash.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

quote ~27

Exact credit price of any capability before you spend anything. Free.

NameTypeReqDescription
capabilitystringyes–

No output schema declared.

No examples provided.

request_capability ~47

Vote for a COMING capability, or describe one we do not list. Free; helps decide what opens next.

NameTypeReqDescription
capabilitystringyes–
use_casestring––

No output schema declared.

No examples provided.

run_chain ~71

Run up to 8 checks or formulas in one call and get ONE signed bundle receipt. Each step is either a verify_math_or_tolerance argument object or {formula, inputs}. Planning and math verification check only — not a licensed professional engineering review, stamp, or sign-off.

NameTypeReqDescription
stepsarrayyes–

No output schema declared.

No examples provided.

run_formula ~104

Run one of our built-in physics formulas (sound speed, echo range, drop shock, field magnitude, thermal, timing and more) on YOUR inputs. Find formula codes and their input names with discover_capabilities. Every formula reproduces its own reference example before it is listed. Each result carries its limits. Planning and math verification check only — not a licensed professional engineering review, stamp, or sign-off.

NameTypeReqDescription
formulastringyes–
inputsobjectyes–

No output schema declared.

No examples provided.

seal_bundle_receipt ~53

Verify 2 to 20 of your Checkbooth receipts and seal them into ONE signed design-review bundle with a single /check link.

NameTypeReqDescription
review_titlestring––
tokensarrayyes–

No output schema declared.

No examples provided.

verify_claims_against_receipts ~105

Paste a README, PR description, spec or memo plus the Checkbooth results it relies on. We check every number in the text against those signed results and flag overclaim phrases (for example "verified across all conditions", "guaranteed", "certified"). Deterministic, no AI. Signed receipt.

NameTypeReqDescription
resultsarrayyesFull Checkbooth results exactly as returned (each carries its receiptToken).
textstringyes–

No output schema declared.

No examples provided.

verify_math_or_tolerance ~81

Independent, signed recompute of your numbers: formula, worst-case tolerance stack, power budget, Nyquist sampling, or rated range. Returns PASS/FAIL/INVALID and a receipt a second party can check at /check. Planning and math verification check only — not a licensed professional engineering review, stamp, or sign-off.

NameTypeReqDescription
check–yes–

No output schema declared.

No examples provided.

verify_report_receipt ~35

Check that a Checkbooth receipt is genuine and unchanged. Free, no key needed.

NameTypeReqDescription
tokenstringyes–

No output schema declared.

No examples provided.

verify_trig_expression ~99

Recompute a formula that uses trig (sin, cos, tan, asin, acos, atan; degree forms sind, cosd, tand, asind, acosd, atand) and compare it to a target. Signed receipt. Planning and math verification check only — not a licensed professional engineering review, stamp, or sign-off.

NameTypeReqDescription
expectobjectyes–
expressionstringyes–
valuesobject––

No output schema declared.

No examples provided.

Install

How do I install the Checkbooth MCP server?

Checkbooth is a hosted endpoint at https://checkbooth.dev/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 · checkbooth.dev

# add to Claude Code
claude mcp add --transport http dev-checkbooth-checkbooth 'https://checkbooth.dev/mcp'
Common questions

What is the Checkbooth MCP server?

Checkbooth is an MCP server listed in the public MCP registry as dev.checkbooth/checkbooth. Independent signed math checks for AI agents: PASS or FAIL plus a link anyone can open. Free beta. This page covers its hosted endpoint (https://checkbooth.dev/mcp).

Is the Checkbooth MCP server safe to use?

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

Checkbooth exposes 12 tools: discover_capabilities, verify_math_or_tolerance, run_formula, run_chain, quote, and 7 more. Their descriptions and schemas cost roughly 793 tokens of context every time the server is loaded.

Does the Checkbooth MCP server require authentication?

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

Is the Checkbooth MCP server still maintained?

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

VerifyMCP ran 13 checks on Checkbooth, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.