MCP server (stdio): repair broken/malformed JSON via the AgentForge API
Cloud & Infrav0.1.0streamable-httpapim-agentforge-6lfm33.azure-api.net
| Criterion | Points | Observed |
|---|---|---|
| reachability | 18 / 25 | HTTP 401 in 475ms — auth required; WWW-Authenticate present: "AzureApiManagementKey realm="https://apim-agentforge-6lfm33.azure-api.net/json-repair",name="Ocp-Apim-Subscription-Key"," |
| protocol | 0 / 15 | handshake not reachable behind auth — unverified |
| tooling | 0 / 0 | auth-gated — tooling unverifiable, excluded from score (grade marked provisional) |
| latency | 10 / 10 | initialize round-trip 475ms |
| provenance | 5 / 15 | description present; no repository URL; version 0.1.0; namespace io.github.CedricKouma does NOT match remote host (expected *.cedrickouma.github.io) |
Score 51/100 · latency 475ms · — tools · protocol access: auth-wellbehaved ⓘ
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.CedricKouma/json-repair.json
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.CedricKouma/json-repair)
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-16 14:16 | D | 51 | 475ms |
| 2026-07-13 14:46 | F | 5 | —ms |