Fixter
dev.fixter/fixter
Monitoring for small teams. Logs, traces, metrics, live issue tracking, API/MCP uptime.
— the operator's own registry description reported
Publisher dev.fixter · first seen 2026-08-12 · endpoint https://mcp.fixter.dev/mcp
Dependency rating derived
Cluster alive-toolless · distinctiveness 0.292 (typical). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.
🔏 Signed receipt rr_1d8dbabdd84301d5e5e31a30 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.
Tools last seen
Truth checks observed
Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.
Protocol conformance observed
Capabilities: tools
Drift
No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.
History observed
Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.
changelog (1 events)
| date | type | what changed |
|---|---|---|
| 2026-08-12 | outcome | first probe: ok |
raw probe records
| probed (UTC) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-08-14T19:58:43Z | ok | 200 | 392 | 2025-06-18 |
| 2026-08-12T05:33:57Z | ok | 200 | 469 | 2025-06-18 |
Watch or embed this verdict
Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:
[](https://robinsaige.com/s/dev.fixter/fixter)
Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.