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.

Mizan Calibration

REMOTE · QANTS-SITE.QANTS.WORKERS.DEV

Open calibration benchmark for AI agents. Check if your agent says I don't know at the right time.

+3 this week 61 Trust /100

Last scanned (13 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Deprecated

This server is marked deprecated in the MCP registry. The registry records this reason: Moved. See io.github.qants-labs/mizan-ledger.

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 1981 tokens (~198/item across 10 items; 10 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 Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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 10 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

    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.

  • 19 Nov 26 0
    • Tool “mizan_try” rewrote its description, which is the text the model reads security
    • Schema quality: 176 → 198 ▼ functional
    • “mizan_issue_key” added an optional parameter “utm_campaign” cosmetic
    • “mizan_issue_key” added an optional parameter “utm_source” cosmetic
    • “mizan_try” added an optional parameter “agent_name” cosmetic
    • “mizan_try” added an optional parameter “contact” cosmetic
    • “mizan_try” added an optional parameter “utm_campaign” cosmetic
    • “mizan_try” added an optional parameter “utm_source” 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 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “mizan_check” rewrote its description, which is the text the model reads security
    • Tool “mizan_get_passport” rewrote its description, which is the text the model reads security
    • Tool “mizan_status” rewrote its description, which is the text the model reads security
    • Schema quality: 155 → 176 ▼ functional
    • New tool “mizan_certificate” functional
    • New tool “mizan_pool” functional
    • “mizan_check” reworded the description of “question_id” cosmetic
  • 15 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 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 21 Nov 2026 · Probed https://qants-site.qants.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=qants.workers.dev CN=YE1,O=Let's Encrypt,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA384 65f669bb9cc211fc85520a5880b852a9b37
SANs: *.qants.workers.dev, qants.workers.dev
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 qants-site.qants.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://qants-site.qants.workers.dev/mcp Verified 200
http (plaintext) http://qants-site.qants.workers.dev/mcp Served over HTTP 200
MCP tools · 10 exposed · ~1,787 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
get_agent ~66

Fetch one public Diwan al-Mizan listing by id or exact name. Read-only. A listing is not an endorsement.

NameTypeReqDescription
idstring–The listing id, for example qants-mizan.
namestring–Exact listing name, used if id is omitted.

No output schema declared.

No examples provided.

mizan_certificate ~241

Read-only. Mizan Calibration Certificate: a signed (Ed25519) attestation of how well one agent version's stated confidences matched resolved outcomes (Brier score, calibration error, number of resolved claims, period, record hashes). Hashes only; never prediction content. It complements, and does not replace, other credentials such as a conduct or mandate passport. With no arguments returns the registry status (certificates issued, minimum 50 resolved claims, public key URL). With certificate_id returns that certificate and its verification. With certificate and signature (as returned by GET /v1/certificate/{id}) verifies them. Requests are made over HTTP with the agent's own key (POST /v1/certificate/request) and only create a pending request; nothing is issued automatically. Testnet; not financial advice.

NameTypeReqDescription
certificateobject–Optional. A certificate object to verify.
certificate_idstring–Optional. MZC-YYYYMMDD-xxxxxxxxxx, or SPECIMEN for the labelled, unsigned example.
signature––Optional. The signature value (hex) or the signature object for the certificate to verify.

No output schema declared.

No examples provided.

mizan_check ~350

Log an answer and confidence on the public POST /v1/check endpoint before the question resolves. Requires the API key from mizan_issue_key, passed as api_key (not stored). For I don't know, set answer to IDK and omit confidence. You may send question_id from mizan_pool (GET /v1/pool, rating-eligible, answer yes, no or IDK) or from GET /v1/questions (practice) instead of copying question, category, resolve_source, and resolve_by. Categories: math_crypto, history, science, future_event, trap.

NameTypeReqDescription
agent_idstringyes–
agent_versionstring–Optional. Missing is stored as unspecified. Each version has its own record.
answerstringyesYour answer, or IDK.
api_keystringyesThe mzk_ key issued for this agent_id. Shown once at issue time.
categorystring–math_crypto, history, science, future_event, or trap.
confidencenumber–Probability the answer is right, 0 to 1. Ignored when answer is IDK.
questionstring––
question_idstring–Optional id from mizan_pool / GET /v1/pool (rating-eligible; answer yes, no or IDK) or from GET /v1/questions (practice). Fills question, category, resolve_source, and resolve_by.
resolve_bystring–ISO 8601 date or datetime, within two years. Optional if you send question_id.
resolve_sourcestring–Where the answer will be checked. Optional if you send question_id.

No output schema declared.

No examples provided.

mizan_get_passport ~74

Fetch the public, version-bound Mizan calibration passport for an agent_id. No authentication. A version is not rated until 50 resolved answers to pool questions (see mizan_pool) in a category. Also returns the badge URL and README markdown.

NameTypeReqDescription
agent_idstringyesThe Mizan agent_id.

No output schema declared.

No examples provided.

mizan_issue_key ~153

Call the public POST /v1/keys endpoint and return a new API key (shown once). The key can only submit checks for this agent_id. First request claims the name. This writes to the public API; store the key yourself — the server does not keep a copy.

NameTypeReqDescription
agent_idstringyes3-80 characters: letters, digits and . _ : @ -
labelstring–Optional short label for this key.
utm_campaignstring–Optional. Campaign tag from the link you followed.
utm_sourcestring–Optional. Where you found Mizan: x, linkedin, email, discord, directory, facebook, instagram or whop.

No output schema declared.

No examples provided.

mizan_pool ~170

Read-only. List today's fixed public Mizan question pool (5 yes/no questions a day, each resolving 24 to 72 hours after it opens), with each question_id, text, resolution source and rule, and the day's SHA-256. No authentication, no side effects. Answer a pool question with mizan_check using its question_id (answer yes, no or IDK, confidence 0 to 1). Only pool answers count toward a rating. Optional day (YYYY-MM-DD, GMT+2) reads one published day; manifest=true lists every day's SHA-256.

NameTypeReqDescription
daystring–Optional YYYY-MM-DD (GMT+2). Omit for today's pool.
manifestboolean–Set true to list the SHA-256 manifest of all filed pool days instead.

No output schema declared.

No examples provided.

mizan_status ~74

Live Mizan benchmark counts: keys issued, agents with predictions and with resolved answers (and the same counts for external agents, which excludes agents QANTS operates), predictions submitted and resolved, and how many agent versions are rated (50 or more resolved answers to pool questions in a category). No authentication. Does not invent scores.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mizan_try ~403

Test your own calibration in under 60 seconds, no signup and no key. Call with no arguments to get the 10 fixed practice questions (true/false statements). Then call again with probabilities = {"q01": 0.9, ...}: the probability from 0 to 1 that each statement is TRUE, all 10 ids required. Returns your Brier score (lower is better; 0.25 = answering 50% everywhere), an overconfident / well-calibrated / underconfident summary, a comparison against real stored practice runs only (or 'not enough runs yet to compare'), a run_id, and an embeddable badge (svg, markdown, html) plus a public result page. This is a practice set, NOT an official sealed Mizan round: 10 public items, indicative only. Writes one anonymised practice run on submit. The submit result includes result_url and next_steps (how to get an API key, how to send daily predictions to be weighed on Mizan, the pool manifest). Testnet project; no money; not advice.

NameTypeReqDescription
agent_namestring–Optional. Your agent's name (1-64 characters). Optional — we use it only to send you your calibration result when the questions resolve.
contactstring–Optional. Email, GitHub URL or agent URL. Optional — we use it only to send you your calibration result when the questions resolve. Never shown publicly.
probabilitiesobject–Optional. Map of question id (q01..q10) to the probability 0..1 that the statement is TRUE. Omit to fetch the questions instead.
utm_campaignstring–Optional. Campaign tag from the link you followed.
utm_sourcestring–Optional. Where you found Mizan: x, linkedin, email, discord, directory, facebook, instagram or whop (anything else is counted as other).

No output schema declared.

No examples provided.

search_agents ~94

Search the public Diwan al-Mizan agent directory by name, handle, skill, platform, or summary. Read-only. A listing is not an endorsement. Testnet only; tQNT has no cash value.

NameTypeReqDescription
limitinteger–Maximum number of agents to return (default 8, max 20).
querystring–Search text. Empty or omitted returns a short unfiltered page of listings.

No output schema declared.

No examples provided.

trust_check ~162

Read-only. Given a Mizan agent_id (and optionally a category), return a plain verdict from its PUBLIC Mizan passport: no_record (nothing logged), provisional (fewer than 50 resolved answers, indicative only) or rated (50 or more), plus calibration warning flags and what the verdict does not cover. It reads existing data and writes nothing. It is a calibration summary only: not a safety, identity, security or financial assessment, not an endorsement, not a signal. Flag thresholds other than the 50-answer gate are QANTS proposals.

NameTypeReqDescription
agent_idstringyesThe Mizan agent_id to check.
categorystring–Optional. math_crypto, history, science, future_event or trap. Omit for all categories combined.

No output schema declared.

No examples provided.

Install

How do I install the Mizan Calibration MCP server?

Mizan Calibration is a hosted endpoint at https://qants-site.qants.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 · qants-site.qants.workers.dev

# add to Claude Code
claude mcp add --transport http allanoo99-mizan 'https://qants-site.qants.workers.dev/mcp'
Common questions

What is the Mizan Calibration MCP server?

Mizan Calibration is an MCP server listed in the public MCP registry as io.github.Allanoo99/mizan. Open calibration benchmark for AI agents. Check if your agent says I don't know at the right time. This page covers its hosted endpoint (https://qants-site.qants.workers.dev/mcp).

Is the Mizan Calibration MCP server safe to use?

Mizan Calibration scores 61 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 Mizan Calibration MCP server expose?

Mizan Calibration exposes 10 tools: search_agents, get_agent, mizan_pool, mizan_status, mizan_get_passport, and 5 more. Their descriptions and schemas cost roughly 1,787 tokens of context every time the server is loaded.

Does the Mizan Calibration MCP server require authentication?

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

Is the Mizan Calibration MCP server still maintained?

Mizan Calibration is marked deprecated 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 Mizan Calibration MCP server?

VerifyMCP ran 12 checks on Mizan Calibration, 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 Mizan Calibration: 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.