Durable Thinking
io.github.linxule/durable-thinking
Self-hosted persistent sequential thinking with private history and MCP App visualization.
— the operator's own registry description reported
Publisher io.github.linxule · first seen 2026-08-12 · endpoint https://{worker_host}/mcp-compat
Dependency rating derived
block — dead / unreachable · kind unknown · V n/a
Cluster unreachable · distinctiveness —. Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.
🔏 Signed receipt rr_7f55e0f19980afd98eb5be73 · 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.
● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →
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: connect_error |
What kind of tools these are derived
Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from the operator's own registry description — REPORTED, not observed (tools were not visible to the probe). What checking applies to each kind (the full methodology →):
| nature | tools | meaning | what checking applies |
|---|---|---|---|
| unclassified | 1 | not classifiable from its text | Tier-1 only until its tools describe themselves |
Tools last seen observed
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.
Drift observed
No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.
Looking for an alternative?
This server doesn't answer, but these live, allow-verdict servers describe themselves similarly — similar by what they say they do — never verified drop-in replacements; check each one before depending on it.
| server | verdict | shared terms |
|---|---|---|
| cloud.redu/mcp Agent-native cloud, EU-hosted. Provision VMs, networks & databases on redu.cloud via MCP. | allow | hosted, persistent, private, self |
| io.github.Hlobo-dev/tengu-firm One MCP key: prices, fundamentals, SEC filings, insider/13F/congressional trades. 336 tools. | allow | persistent, private, self, thinking |
| io.stablebaseline/sb End-to-end agent-managed company brain. Docs, diagrams, plans, Knowledge Graph. Lean & affordable. | allow | hosted, private, self, thinking |
| online.sasame/research No-key MCP: audit/certify MCPs, signed trust history; join Gold Rush Town & build with your LLM. | allow | hosted, persistent, private, self |
| com.wiselyenterprisesllc/x402-agent-payment-infr Self-facilitated x402/MCP payments for hosted endpoints, rail proofs, receipts, and agents. | allow | hosted, persistent, private, self |
raw probe records
| probed (UTC) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-08-14T19:59:44Z | connect_error | |||
| 2026-08-12T05:34:57Z | connect_error |
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/io.github.linxule/durable-thinking)
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.