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 Verifier — Independent Number Verification

REMOTE · AGENT-VERIFIER.AGENT-VERIFIER.WORKERS.DEV

Verify totals in finished tables add up. Independent arithmetic audit for AI agents, signed receipt.

+3 this week 62 Trust /100

Last scanned (40 minutes ago)

Scores higher than 44% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Data and Analytics

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 Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 207 tokens (~207/item across 1 items; 1 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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 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.

  • 29 Oct 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.

  • 28 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 27 Oct 26 58

    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 5 Nov 2026 · Probed https://agent-verifier.agent-verifier.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agent-verifier.workers.dev CN=YE2,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 ECDSA 256 ECDSA-SHA384 54936d8be26f3de8b75c18574246ec90ced
SANs: *.agent-verifier.workers.dev, agent-verifier.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 agent-verifier.agent-verifier.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. 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://agent-verifier.agent-verifier.workers.dev/mcp Verified 200
http (plaintext) http://agent-verifier.agent-verifier.workers.dev/mcp Inconclusive 405
MCP tools · 1 exposed · ~176 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
verify_numbers ~176

Verify that the numbers in a finished table add up — before you deliver it. Use this when you have produced or received a table, spreadsheet, CSV/TSV or markdown table, a cost breakdown, invoice, quotation or budget, and need an independent check that row totals, column totals and subtotals are arithmetically consistent, or that a list of line items sums to a stated total. Returns every mismatched cell with the recomputed value and the difference, plus a signed verification receipt (verification ID, UTC time, SHA-256 content hash). Checks arithmetic consistency only; does not verify source data. Not a calculator — it does not evaluate expressions; it audits finished numbers.

NameTypeReqDescription
contentstringyesThe finished table (markdown, CSV or TSV) or the "name: value" breakdown text to audit.

No output schema declared.

No examples provided.

Install

How do I install the Agent Verifier — Independent Number Verification MCP server?

Agent Verifier — Independent Number Verification is a hosted endpoint at https://agent-verifier.agent-verifier.workers.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 · agent-verifier.agent-verifier.workers.dev

# add to Claude Code
claude mcp add --transport http zenoix888-agent-verifier 'https://agent-verifier.agent-verifier.workers.dev/mcp'
Common questions

What is the Agent Verifier — Independent Number Verification MCP server?

Agent Verifier — Independent Number Verification is an MCP server listed in the public MCP registry as io.github.zenoix888/agent-verifier. Verify totals in finished tables add up. Independent arithmetic audit for AI agents, signed receipt. This page covers its hosted endpoint (https://agent-verifier.agent-verifier.workers.dev/mcp).

Is the Agent Verifier — Independent Number Verification MCP server safe to use?

Agent Verifier — Independent Number Verification scores 62 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 Verifier — Independent Number Verification MCP server expose?

Agent Verifier — Independent Number Verification exposes 1 tool: verify_numbers. Their descriptions and schemas cost roughly 176 tokens of context every time the server is loaded.

Does the Agent Verifier — Independent Number Verification MCP server require authentication?

No. We connected to Agent Verifier — Independent Number Verification without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Agent Verifier — Independent Number Verification MCP server still maintained?

Agent Verifier — Independent Number Verification is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.