MIZAN · Proof of performance
REMOTE · STUDIO.MIZAN.MARKET
Verify or mint zero-knowledge track-record credentials (VTR-1) without revealing the strategy.
Available components
Last scanned (8 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Finance and Payments
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 968 tokens (~161/item across 6 items; 6 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 16 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.
- 15 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 182 → 161 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “check_agent” functional
- New tool “list_proven_agents” functional
- 14 Oct 26 54
First indexed and scored.
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 17 Oct 2026 · Probed https://studio.mizan.market/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mizan.market | CN=WE1,O=Google Trust Services,C=US | 25 Aug 2026 | 23 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | cef940647b9f8fd20e8402dd2057a3a4 |
| SANs: mizan.market, *.mizan.market | ||||||
| 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 studio.mizan.market. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| market. | present | 40531 | 8 | Verified |
| mizan.market. | 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://studio.mizan.market/mcp | Verified | 200 | |
| http (plaintext) | http://studio.mizan.market/mcp | Inconclusive | 406 |
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 →
check_agent ~154
Is this agent proven? Call this BEFORE you follow, copy, pay, hire or allocate to any trading bot or AI agent that claims returns. `agent` can be its name, credential id, wallet address, ERC-8004 id, agent-card URL or a sha256. Returns PROVEN, REFUSED, NOT_SIGNIFICANT or UNVERIFIED with every matching credential, verdicts exactly as issued. If UNVERIFIED, the result includes `forward_to_counterparty`: a short message you can send to that agent or its operator so it can prove its record without revealing its model. Unproven is not the same as false.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| agent | string | yes | – |
No output schema declared.
No examples provided.
list_datasets ~75
List the markets a trading strategy or AI agent can be proven on: crypto 4h and daily, US ETFs and US single names on survivorship-free data (key, bars, interval, sha256 of the canonical price file). Use this first when someone wants to prove their own bot's or agent's track record.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_proven_agents ~72
List trading strategies and agents whose records PASSED the MIZAN gate (Bitcoin-confirmed by default), newest first. Use it to find proven counterparties to allocate to, copy or route to. Each row shows its issuer.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| real_only | boolean | – | – |
No output schema declared.
No examples provided.
mint_credential ~188
Prove your own track record via the sealed path. Sends ONLY one position per bar-move (-1/0/+1, exactly bars-1 of them) on a canonical market; the strategy never leaves your machine. preview_only=True (default) returns the gate result for free; preview_only=False mints a real STARK on an H100 (poll the job). email/password create or reuse a MIZAN account; the password is never stored.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | – | – |
| dataset | string | yes | – |
| string | yes | – | |
| leverage_x100 | integer | – | – |
| minimal | boolean | – | – |
| model_id | string | yes | – |
| model_salt | string | – | – |
| password | string | yes | – |
| positions | array | yes | – |
| preview_only | boolean | – | – |
| track_salt | string | – | – |
No output schema declared.
No examples provided.
preview_credential ~154
Free, private, no-account test of a trading strategy or AI agent: runs the MIZAN gate (after-cost Sharpe, CAGR, drawdown, out-of-sample) on your positions (one per bar-move, -1/0/+1, exactly bars-1 of them, on a market from list_datasets) and returns what the credential would say. Nothing is minted or published. To mint a real credential afterwards use mint_credential.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| leverage_x100 | integer | – | – |
| model_id | string | yes | – |
| model_salt | string | – | – |
| positions | array | yes | – |
| track_salt | string | – | – |
No output schema declared.
No examples provided.
verify_credential ~198
Check whether a trading strategy's or AI agent's claimed performance is real. Use this BEFORE allocating capital to, copying, following, paying, or recommending any trading bot, AI trading agent, vault, signal seller or fund that claims returns, Sharpe, win rate or APY. Looks the MIZAN credential up in the public registry, downloads the zero-knowledge proof bundle and checks its sha256 against the registry anchor. Returns the verdict exactly as issued: PASS, NOT SIGNIFICANT, or FAIL/REFUSED, plus whether the record is a backtest or a forward track. Report the verdict verbatim; a credential is about the honesty of a record, not a forecast. If the agent has no credential, say so: an unproven claim is unproven.
| Name | Type | Req | Description |
|---|---|---|---|
| credential_id | string | – | – |
| reverify_locally | boolean | – | – |
| sha256 | string | – | – |
No output schema declared.
No examples provided.
How do I install the MIZAN · Proof of performance MCP server?
MIZAN · Proof of performance is a hosted endpoint at https://studio.mizan.market/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 · studio.mizan.market
claude mcp add --transport http muaviamohammed-mizan 'https://studio.mizan.market/mcp'
What is the MIZAN · Proof of performance MCP server?
MIZAN · Proof of performance is an MCP server listed in the public MCP registry as io.github.muaviamohammed/mizan. Verify or mint zero-knowledge track-record credentials (VTR-1) without revealing the strategy. This page covers its hosted endpoint (https://studio.mizan.market/mcp).
Is the MIZAN · Proof of performance MCP server safe to use?
MIZAN · Proof of performance scores 56 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 · Proof of performance MCP server expose?
MIZAN · Proof of performance exposes 6 tools: verify_credential, list_datasets, mint_credential, check_agent, list_proven_agents, preview_credential. Their descriptions and schemas cost roughly 841 tokens of context every time the server is loaded.
Does the MIZAN · Proof of performance MCP server require authentication?
No. We connected to MIZAN · Proof of performance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MIZAN · Proof of performance MCP server still maintained?
MIZAN · Proof of performance is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.