MCP QUEEN
io.github.DunkelCloud/toolmesh F
Self-hosted MCP gateway. Turn any REST API into MCP tools via YAML (DADL). Authz, audit, policies.
Dev & Codev0.3.0streamable-http{host} repository
Grade evidence — probed 2026-07-16 14:46 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 0 / 25 | fetch failed: Fetch API cannot load: https://{host}:8123/mcp |
| protocol | 0 / 15 | no handshake |
| tooling | 0 / 35 | unreachable — no tooling to assess |
| latency | 0 / 10 | not measurable |
| provenance | 15 / 15 | description present; repository linked; version 0.3.0; namespace io.github.DunkelCloud matches endpoint/repo |
Score 15/100 · latency —ms · — tools · protocol access: unreachable ⓘ
Trust receipt
Security, data integrity, citation quality, and advertised claims are measured separately from protocol uptime. Missing evidence is marked unverified, never converted into a pass.
No deterministic trust observations published yet. This means unaudited—not safe, unsafe, accurate, or inaccurate.
Machine-readable receipt: /api/trust/io.github.DunkelCloud/toolmesh.json
Own this server? Embed your grade badge
Live operational-grade badge, re-probed continuously — not a security or data-quality certification. Put it in your README and link to the complete receipt:
[](https://mcpqueen.com/s/io.github.DunkelCloud/toolmesh)
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.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-16 14:46 | F | 15 | —ms |
| 2026-07-13 15:16 | F | 15 | —ms |