just a normal description with a link to https://evil.com
Productivityv0.0.7streamable-httptest-distribution-pr-a7d5a2d3.alpic.live
| Criterion | Points | Observed |
|---|---|---|
| reachability | 0 / 25 | HTTP 200 in 461ms — JSON-RPC error: {"code":-32603,"message":"MCP error -32603: Internal Server Error"} |
| protocol | 0 / 15 | no handshake |
| tooling | 0 / 35 | unreachable — no tooling to assess |
| latency | 0 / 10 | not measurable |
| provenance | 10 / 15 | description present; no repository URL; version 0.0.7; namespace live.alpic.test-distribution-pr-a7d5a2d3 matches endpoint/repo |
Score 10/100 · latency 461ms · — tools · protocol access: unreachable ⓘ
Security, data integrity, citation quality, and advertised claims are measured separately from protocol uptime. Missing evidence is marked unverified, never converted into a pass.
| Dimension | Metric | Status | Evidence | Source |
|---|---|---|---|---|
| security | authentication_boundary | observed | Live protocol probe observed auth_state=unreachable. This describes discovery/access behavior; it is not by itself a vulnerability finding. Observed value: unreachable | live_probe |
Machine-readable receipt: /api/trust/live.alpic.test-distribution-pr-a7d5a2d3/test-distribution-project.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/live.alpic.test-distribution-pr-a7d5a2d3/test-distribution-project)
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-19 17:46 | F | 10 | 461ms |