Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/PckyDev/discord-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/pckydev/discord-mcp/discord-mcp)<a href="https://agentmods.dev/mcp/pckydev/discord-mcp/discord-mcp"><img src="https://agentmods.dev/badge/mcp/pckydev/discord-mcp/discord-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/pckydev/discord-mcp/discord-mcp"><img src="https://agentmods.dev/badge/mcp/pckydev/discord-mcp/discord-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
discord-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"discord-mcp": {
"command": "node",
"args": [
"./scripts/discord-mcp.mjs"
],
"cwd": ".",
"env_vars": [
"DISCORD_BOT_TOKEN",
"DISCORD_ALLOWED_GUILD_IDS"
],
"startup_timeout_sec": 10,
"tool_timeout_sec": 60,
"default_tools_approval_mode": "writes"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 16 lines scan A 936070f85d0b
discord-mcp is an MCP server published in the GitHub repository PckyDev/discord-mcp (0 stars, last pushed 18d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
discord-mcp
Caller-owned Discord operations for AI agents with 209 typed tools and verifiable guild builds. Runs locally from the @discord-mcp/cli npm package. Needs 3 environment variables to run.
discord-mcp
A lightweight, multi-guild Discord MCP server with 95+ tools. Runs locally from the @pasympa/discord-mcp npm package. Needs 1 environment variable to run.
discord-mcp
MCP server "discord-mcp" as configured in sandraschi/discord-mcp. Runs locally from the python Python package. Needs 2 environment variables to run.
discord-developer-mcp
MCP server for verifying Discord bot behavior through a test bot account. Runs locally from the discord-developer-mcp npm package.
omnicord
Discord server management MCP for AI agents: chat, moderation, admin, and full server building. Runs locally from the @orygn/omnicord npm package. Needs 2 environment variables to run.
mcp-discord
MCP server "mcp-discord" as configured in devli13/mcp-discord. Runs locally from the @devli13/mcp-discord npm package.