mcp.mzizi.dev

Item: mcp.mzizi.dev
Rating: 84
Author: wmcp.sh

https://mcp.mzizi.dev

84/100 · MCP Trust Grade · checked 5h ago · MCP 2025-06-18

✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 7 tools · Database

list_collections

List every collection in the Mzizi document store with document counts and per-owner breakdown (components, primitives, skills, brand, styling-*, docu

read_documents

Read documents from a collection in the Mzizi document store. Omit `name` to list a collection; pass `name` for one document. Use list_collections to

get_component

Fetch one component as its full JSON document (metadata, owner, sources/descriptors, files, source code, docs) from the `components` collection.

list_components

List components (lean index) from the `components` collection. Optionally filter by owner. Use get_component for the full document.

get_node_documents

List documents for an ecosystem node (1–10), optionally scoped to a collection. Returns each document's full JSON.

read_versions

Read the version-history snapshots for a document (version_number, change_type, comment, snapshot).

get_database_status

Diagnostic info — Supabase connection health and document-store row count.

Spec conformance20%100

✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 7 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

7 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%70

single-probe latency 2575ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%63

71% of tools have typed inputSchema
0/7 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-06-18

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade mcp.mzizi.dev on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — mcp.mzizi.dev grade B

Share on X Open card image

https://wmcp.sh/mcp/grade/mcp.mzizi.dev

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B](https://wmcp.sh/mcp/grade/mcp.mzizi.dev/badge.svg)](https://wmcp.sh/mcp/grade/mcp.mzizi.dev)

HTML

<a href="https://wmcp.sh/mcp/grade/mcp.mzizi.dev"><img src="https://wmcp.sh/mcp/grade/mcp.mzizi.dev/badge.svg" alt="MCP Trust Grade B · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.