MCP QUEEN
dev.kamy/kamy A
Document API for AI-native software: render PDFs, e-sign, PAdES-seal, and verify.
Media & Designv1.2.0streamable-httpmcp.kamy.dev repository
Grade evidence — probed 2026-07-13 10:30 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 279ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo kamy@1.2.0 |
| tooling | 35 / 35 | tools/list OK: 12 tools e.g. "list_templates"; 12/12 described, 12/12 fully-typed schemas, median description 140 chars |
| latency | 10 / 10 | initialize round-trip 279ms |
| provenance | 15 / 15 | description present; repository linked; version 1.2.0; namespace dev.kamy matches endpoint/repo |
Score 100/100 · latency 279ms · 12 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http kamy https://mcp.kamy.dev/mcp
Generic MCP client config:
{ "mcpServers": { "kamy": { "type": "http", "url": "https://mcp.kamy.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/dev.kamy/kamy · referral link https://mcpqueen.com/go/dev.kamy/kamy (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/dev.kamy/kamy)
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-13 10:30 | A | 100 | 279ms |