Compared · discord
6 Discord MCP servers. Which one to use.
Every Discord server we index, with whether its source is still reachable and whether we hold a screening verdict. None currently carry a source-liveness flag.
Scope: 6 servers indexed from the MCP registry as of 2026-07-25. Servers whose authors never published to the registry are not listed here, so treat this as the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Discord MCP | io.github.hypark5540 | no flag | not screened | 90 | npm @hypark5540/discord-mcp |
| io.github.PaSympa/discord-mcp | io.github.PaSympa | no flag | not screened | 85 | npm @pasympa/discord-mcp |
| io.github.jaimenbell/discord-mcp | io.github.jaimenbell | no flag | REVIEW | 80 | pypi jaimenbell-discord-mcp |
| io.github.Oratorian/discord-node-mcp | io.github.Oratorian | no flag | REVIEW | 74 | npm @mahesvara/discord-mcpserver |
| ai.smithery/Danushkumar-V-mcp-discord | ai.smithery | no flag | REVIEW | 64 | remote endpoint |
| TDA Discord Reader | io.github.targeteddesignagency-blip | no flag | not screened | 63 | not published |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.