app.higgsfield.mizan-bazar/mizan
REMOTE · MIZAN-BAZAR.HIGGSFIELD.APP
Check an x402 endpoint before your agent pays it: avoid / caution / ok, proven on-chain.
Available components
Last scanned (1 hour ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security57
- 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 3 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 223 tokens (~74/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 +5
- HTTPS: fail → pass ▲ security
- 10 Oct 26 0
- Stability: 0.97 → pass security
- 7 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 87 to 97. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Sept 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
- 9 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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://mizan-bazar.higgsfield.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=higgsfield.app | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 68b120fff17da96c0e58b82e157aa54c |
| SANs: higgsfield.app, *.higgsfield.app | ||||||
| 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 mizan-bazar.higgsfield.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| higgsfield.app. | 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 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'self' https://higgsfield.app https://higgsfield.ai https://*.higgsfield.ai https://claude.ai https://*.claude.ai https://*.claudemcpcontent.com file: |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mizan-bazar.higgsfield.app/mcp | Verified | 200 | |
| http (plaintext) | http://mizan-bazar.higgsfield.app/mcp | HTTPS enforced | 301 | https://mizan-bazar.higgsfield.app/mcp |
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 →
mizan_check Check an x402 endpoint before paying it ~85
Free. Returns avoid / caution / ok / unrated for an x402 endpoint or operator, based on what Mizan measured when it bought from them with its own money. Call this before any x402 payment.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | Or just the hostname, to judge the whole operator. |
| url | string | – | The full endpoint URL you are about to pay. |
No output schema declared.
No examples provided.
mizan_coverage What Mizan has measured so far ~38
Free. How many endpoints are on file, how many were actually bought, how many charge without delivering, and when the last survey ran.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mizan_report What the paid report card contains ~45
Explains what evidence sits under a verdict for a given operator and how to buy it over x402. Does not itself cost anything.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Operator hostname. |
No output schema declared.
No examples provided.
How do I install the app.higgsfield.mizan-bazar/mizan MCP server?
app.higgsfield.mizan-bazar/mizan is a hosted endpoint at https://mizan-bazar.higgsfield.app/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 · mizan-bazar.higgsfield.app
claude mcp add --transport http app-higgsfield-mizan-bazar-mizan 'https://mizan-bazar.higgsfield.app/mcp'
What is the app.higgsfield.mizan-bazar/mizan MCP server?
app.higgsfield.mizan-bazar/mizan is an MCP server listed in the public MCP registry as app.higgsfield.mizan-bazar/mizan. Check an x402 endpoint before your agent pays it: avoid / caution / ok, proven on-chain. This page covers its hosted endpoint (https://mizan-bazar.higgsfield.app/mcp).
Is the app.higgsfield.mizan-bazar/mizan MCP server safe to use?
app.higgsfield.mizan-bazar/mizan scores 78 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 app.higgsfield.mizan-bazar/mizan MCP server expose?
app.higgsfield.mizan-bazar/mizan exposes 3 tools: mizan_check, mizan_report, mizan_coverage. Their descriptions and schemas cost roughly 168 tokens of context every time the server is loaded.
Does the app.higgsfield.mizan-bazar/mizan MCP server require authentication?
No. We connected to app.higgsfield.mizan-bazar/mizan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the app.higgsfield.mizan-bazar/mizan MCP server still maintained?
app.higgsfield.mizan-bazar/mizan 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.