Historis keeps track of what happened — so you and your AI are never out of sync.
Dev & Codev1.3.1streamable-httpapi.historis.app
| Criterion | Points | Observed |
|---|---|---|
| reachability | 18 / 25 | HTTP 401 in 521ms — auth required; WWW-Authenticate present: "Bearer resource_metadata="https://api.historis.app/.well-known/oauth-protected-resource"" |
| protocol | 0 / 15 | handshake not reachable behind auth — unverified |
| tooling | 0 / 0 | auth-gated — tooling unverifiable, excluded from score (grade marked provisional) |
| latency | 7 / 10 | initialize round-trip 521ms |
| provenance | 5 / 15 | description present; no repository URL; version 1.3.1; namespace io.github.SvenLC does NOT match remote host (expected *.svenlc.github.io) |
Score 46/100 · latency 521ms · — 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.
| Dimension | Metric | Status | Evidence | Source |
|---|---|---|---|---|
| security | authentication_boundary | observed | Live protocol probe observed auth_state=auth-wellbehaved. This describes discovery/access behavior; it is not by itself a vulnerability finding. Observed value: auth-wellbehaved | live_probe |
Machine-readable receipt: /api/trust/io.github.SvenLC/historis.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.SvenLC/historis)
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 19:01 | D | 46 | 521ms |
| 2026-07-13 19:17 | D | 46 | 768ms |