Mizan Calibration MCP server
io.github.Allanoo99/mizanAllanoo99streamable-httpv1.1.0Scanned
Open calibration benchmark for AI agents. Check if your agent says I don't know at the right time.
8 tools: 2 change things and 6 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Mizan Calibration MCP server can do
The Mizan Calibration MCP server is published by the GitHub account Allanoo99. It has 8 tools. It can create or change data (2 tools: mizan_issue_key and mizan_try), but cannot delete data. 6 tools only read.
1 tool reads private data (search_agents); 1 tool brings in text other people can write (mizan_check).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 2Claude Code: ask
mizan_issue_keyCall the public POST /v1/keys endpoint and return a new API key (shown once).No findings
Why it is in this group
- The description's first verb is "call": a word for a change.
Description, as the server wrote it 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.
mizan_tryTest your own calibration in under 60 seconds, no signup and no key.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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. Testnet project; no money; not advice.
Only reads 6Show 6 read-only tools
get_agentFetch one public Diwan al-Mizan listing by id or exact name.No findings
Why it is in this group
- The name "get_agent" says "get": a word for reading.
Description, as the server wrote it Fetch one public Diwan al-Mizan listing by id or exact name. Read-only. A listing is not an endorsement.
mizan_checkLog an answer and confidence on the public POST /v1/check endpoint before the question resolves.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "log": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "log" and "post": it reads posts, which other people can write.
Description, as the server wrote it 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 GET /v1/questions instead of copying question, category, resolve_source, and resolve_by. Categories: math_crypto, history, science, future_event, trap.
mizan_get_passportFetch the public, version-bound Mizan calibration passport for an agent_id.No findings
Why it is in this group
- The name "mizan_get_passport" says "get": a word for reading.
Description, as the server wrote it Fetch the public, version-bound Mizan calibration passport for an agent_id. No authentication. A version is not rated until 50 resolved answers in a category. Also returns the badge URL and README markdown.
mizan_statusLive Mizan benchmark counts: how many predictions have been submitted and resolved, and how many agent versions are rated (50 or more resolved answers in a category).No findings
Why it is in this group
- The name "mizan_status" says "status": a word for reading.
Description, as the server wrote it Live Mizan benchmark counts: how many predictions have been submitted and resolved, and how many agent versions are rated (50 or more resolved answers in a category). No authentication. Does not invent scores.
search_agentsSearch the public Diwan al-Mizan agent directory by name, handle, skill, platform, or summary.Reads private dataNo findings
Why it is in this group
- The name "search_agents" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "directory": it reads files.
Description, as the server wrote it 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.
trust_checkRead-only.No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:19 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://qants-site.qants.workers.dev/mcp: tools/list returned 9 tools to an anonymous client, including mizan_issue_key (write), mizan_try (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http mizan https://qants-site.qants.workers.dev/mcpclaude mcp add --transport http mizan https://qants-site.qants.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__mizan__search_agents",
"mcp__mizan__get_agent",
"mcp__mizan__mizan_status",
"mcp__mizan__mizan_get_passport",
"mcp__mizan__mizan_check",
"mcp__mizan__trust_check"
],
"ask": [
"mcp__mizan__mizan_issue_key",
"mcp__mizan__mizan_try"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mizan. Review it before you use it.
Capability tags behind 2 rules
- mcp__mizan__search_agents private-data
- mcp__mizan__mizan_check untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Allanoo99/mizan/verify?hash=18ea0867d47e1be091b44e2ee660a2bc9f64accce61c32d14f411b8a7a29dc84" | jq -e '.changed == false'Pinned hash 18ea0867d47e, from Nov 14, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Allanoo99/mizan/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Allanoo99/mizan)Source: MCP Registry · repository. Synced Nov 18, 2026, 22:17 UTC.
Mizan Calibration MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Mizan Calibration MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Mizan Calibration MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Mizan Calibration MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Mizan Calibration MCP server have?
- 8 tools: 2 write, 6 read. mizan_issue_key, mizan_try, search_agents, get_agent, mizan_status, mizan_get_passport, mizan_check and trust_check.
Does the Mizan Calibration MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Mizan Calibration MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Mizan Calibration MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.