Is Discord MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
How Discord MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 68/100
- higher than 30% of 48,273 servers
- Tools that change things
- 20%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 8 read · 2 change
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
2 medium
- Code scan5 source files scanned; 6 source files scanned15/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (2)
- mediumeval / new Function used
exec.evalbundle/discord-mcp.cjs: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de… - mediumeval / new Function used
exec.evalhypark_discord_mcp-0.1.1/python/src/hypark_discord_mcp/_bundled/server.cjs: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
Overall 68/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON