MCP QUEEN
io.github.ejentum/self-inspect-mcp A
Send a thought, get one metathought that makes your agent inspect its own assumptions. Keyless.
Dev & Codev0.1.1streamable-httpapi.ejentum.com repository
Grade evidence — probed 2026-07-14 00:45 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 73ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo self-inspect@0.1.0 |
| tooling | 35 / 35 | tools/list OK: 1 tools e.g. "self_inspect"; 1/1 described, 1/1 fully-typed schemas, median description 764 chars |
| latency | 10 / 10 | initialize round-trip 73ms |
| provenance | 15 / 15 | description present; repository linked; version 0.1.1; namespace io.github.ejentum matches endpoint/repo |
Score 100/100 · latency 73ms · 1 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http self-inspect-mcp https://api.ejentum.com/self-inspect-mcp
Generic MCP client config:
{ "mcpServers": { "self-inspect-mcp": { "type": "http", "url": "https://api.ejentum.com/self-inspect-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.ejentum/self-inspect-mcp · referral link https://mcpqueen.com/go/io.github.ejentum/self-inspect-mcp (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.ejentum/self-inspect-mcp)
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-14 00:45 | A | 100 | 73ms |