MCP gateway with 10 tools for code analysis, architecture, package audit & security.
Dev & Codev1.0.0streamable-httpzephex.dev
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 1386ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo zephex@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 10 tools e.g. "get_project_context"; 10/10 described, 10/10 fully-typed schemas, median description 936 chars |
| latency | 7 / 10 | initialize round-trip 1386ms |
| provenance | 5 / 15 | description present; no repository URL; version 1.0.0; namespace io.github.Tanbir404 does NOT match remote host (expected *.tanbir404.github.io) |
Score 87/100 · latency 1386ms · 10 tools · auth: open
Claude Code:
claude mcp add --transport http zephex https://zephex.dev/mcp
Generic MCP client config:
{ "mcpServers": { "zephex": { "type": "http", "url": "https://zephex.dev/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/io.github.Tanbir404/zephex · referral link https://mcpqueen.com/go/io.github.Tanbir404/zephex (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.Tanbir404/zephex)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 19:32 | B | 87 | 1386ms |