Is Durable Thinking MCP server safe?
Not recommended.
Hidden from default browsing. Significant findings or unreachable.
What to know before installing
- highRemote endpoint did not respond — TypeError: fetch failed
How Durable Thinking compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 47/100
- higher than 9% of 48,255 servers
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
1 high
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote unreachable: TypeError: fetch failed0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 5 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableTypeError: fetch failed
Overall 47/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Safer options for the same job
- ComputerA private persistent computer: files that survive between runs, a bash shell and JavaScript.not reviewedEstablishedA
