# MIZAN · Proof of performance (remote · studio.mizan.market)

Verify or mint zero-knowledge track-record credentials (VTR-1) without revealing the strategy.

- Trust score: 56/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `studio.mizan.market`: 56/100 (this document), [markdown](https://verifymcp.io/servers/muaviamohammed-mizan/studio.md), [page](https://verifymcp.io/servers/muaviamohammed-mizan/studio)

## Channel facts

- Endpoint: `https://studio.mizan.market/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http muaviamohammed-mizan 'https://studio.mizan.market/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "muaviamohammed-mizan": {
      "url": "https://studio.mizan.market/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "muaviamohammed-mizan": {
      "type": "http",
      "url": "https://studio.mizan.market/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.muaviamohammed-mizan]
url = "https://studio.mizan.market/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "muaviamohammed-mizan": {
      "type": "remote",
      "url": "https://studio.mizan.market/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add muaviamohammed-mizan --url 'https://studio.mizan.market/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  muaviamohammed-mizan:
    url: "https://studio.mizan.market/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "muaviamohammed-mizan": {
      "Transport": "http",
      "Url": "https://studio.mizan.market/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add muaviamohammed-mizan -t streamable-http -u 'https://studio.mizan.market/mcp'
```

### Other

```json
{
  "mcpServers": {
    "muaviamohammed-mizan": {
      "type": "http",
      "url": "https://studio.mizan.market/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 56, +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.

### 2026-10-15 (score 55, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Schema quality: 182 → 161
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “check_agent”
- [functional] New tool “list_proven_agents”

### 2026-10-14 (score 54)

First indexed and scored.

## MCP tools (6)

### `verify_credential` (~198 tokens)

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.

Input parameters:

- `credential_id` (string)
- `reverify_locally` (boolean)
- `sha256` (string)

### `list_datasets` (~75 tokens)

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.

### `mint_credential` (~188 tokens)

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.

Input parameters:

- `alias` (string)
- `dataset` (string, required)
- `email` (string, required)
- `leverage_x100` (integer)
- `minimal` (boolean)
- `model_id` (string, required)
- `model_salt` (string)
- `password` (string, required)
- `positions` (array, required)
- `preview_only` (boolean)
- `track_salt` (string)

### `check_agent` (~154 tokens)

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.

Input parameters:

- `action` (string)
- `agent` (string, required)

### `list_proven_agents` (~72 tokens)

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.

Input parameters:

- `limit` (integer)
- `real_only` (boolean)

### `preview_credential` (~154 tokens)

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.

Input parameters:

- `dataset` (string, required)
- `leverage_x100` (integer)
- `model_id` (string, required)
- `model_salt` (string)
- `positions` (array, required)
- `track_salt` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/muaviamohammed-mizan/studio#diagnostics

## Score history

- 2026-10-17: 56
- 2026-10-16: 56
- 2026-10-15: 55
- 2026-10-14: 54

## Common questions

### 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.

## Links

- Remote endpoint: https://studio.mizan.market/mcp
- Repository: https://github.com/muaviamohammed/mizan-mcp
- Website: https://mizan.market/skill/
- Changelog RSS feed: https://verifymcp.io/servers/muaviamohammed-mizan/studio.xml
- Changelog JSON feed: https://verifymcp.io/servers/muaviamohammed-mizan/studio.json
- HTML version of this page: https://verifymcp.io/servers/muaviamohammed-mizan/studio