Is DERO MCP Server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highRemote endpoint did not respond — TypeError: fetch failed
How DERO MCP Server compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 65/100
- higher than 15% of 1,293 Productivity servers
- Tools that change things
- 3%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 0%
- of our recent checks; the typical remote Productivity server answers 100%
What its tools let an agent do: 32 read · 1 change
Public scan report
scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it
1 high1 medium
- Code scan56 source files scanned20/25
- Live reliabilityremote unreachable: TypeError: fetch failed0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (2)
- highRemote endpoint did not respond
reliability.unreachableTypeError: fetch failed
- mediumeval / new Function used
exec.evaldata/docs-index.json: …nst content = await fetchTELADoc(scid); eval(content); // Load the module } 4. **Remo…
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what DERO MCP Server does
Context7Up-to-date docs for AI agentsnot reviewedWidely usedA- Svelte MCPThe official Svelte MCP server providing docs and autofixing tools for Svelte developmentnot reviewedWidely usedA
SvGridChecks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.not reviewedEstablishedA