Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Discord MCP

NPM · @ORYGN/DISCORD-MCP

Discord server management MCP for AI agents: chat, moderation, admin, and full server building.

Available components

+4 this week 84 Trust /100

Last scanned (22 hours ago)

Scores higher than 75% of npm servers

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 19 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to OrygnsCode/discord-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 22611 tokens (~137/item across 164 items; 164 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 29 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 165 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1
    • Package version: 2.1.0 → 2.1.1 functional
  • 19 Nov 26 +1
    • Stability: 0.20 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 2.0.0 → 2.1.0 functional
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@orygn/discord-mcp@2.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo OrygnsCode/discord-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/OrygnsCode/discord-mcp/.github/workflows/release.yml@refs/tags/v2.1.1
Rekor log index 4030686623
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:f6bcfbf400c3a89a174edd387335c704423f8036557bb85f35ea5d8a6e9f6bd9c736ac0e6d7d6d4f810c6cdf04e7d82d5073a841a620000dc7171a937

Background: How many MCP packages publish verified provenance →

Dependencies 19 packages
Packages resolved 19
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 164 exposed · ~22,249 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
update_event ~196

Edit a scheduled event's details, or move it through its lifecycle: status start makes it live, status end completes it. An ended event cannot be started again, so ending one needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Everything else happens at once.

NameTypeReqDescription
confirm_tokenstring–The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.
descriptionstring––
end_timestring––
eventstringyesEvent name or ID.
guildstring–Guild (server) name or ID. Omit to use the default guild.
locationstring––
namestring––
start_timestring––
statusstring––

No output schema declared.

No examples provided.

update_forum_post ~111

Edit a post's title or tags, pin or unpin it within the forum, lock or unlock replies, or archive it.

NameTypeReqDescription
archivedboolean––
guildstring–Guild (server) name or ID. Omit to use the default guild.
lockedboolean––
pinnedboolean––
poststringyesPost title or thread ID.
tagsarray–Replace the applied tags with these.
titlestring––

No output schema declared.

No examples provided.

update_forum_tag ~78

Rename a forum tag or change its moderated flag.

NameTypeReqDescription
forumstringyesForum channel name or ID.
guildstring–Guild (server) name or ID. Omit to use the default guild.
moderatedboolean––
namestring––
tagstringyesCurrent tag name.

No output schema declared.

No examples provided.

update_member ~262

Edit a member's nickname or voice state. Voice changes (server mute, server deafen, move to another voice channel) only apply while the member is connected to voice. Role changes go through assign_role and remove_role. Moving someone into a voice channel they cannot join themselves lets them hear it, and lifting a server mute or deafen undoes what a moderator did, so those need confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Everything else, muting and deafening included, happens at once.

NameTypeReqDescription
confirm_tokenstring–The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.
guildstring–Guild (server) name or ID. Omit to use the default guild.
memberstringyesMember name or user ID.
move_to_voicestring–Voice channel name or ID to move the member into.
nicknamestring–New nickname, or empty string to clear it.
reasonstring––
server_deafenboolean––
server_muteboolean––

No output schema declared.

No examples provided.

update_onboarding ~232

Configure the new-member onboarding flow on a Community server: prompts with options that grant channels and roles, the default channels every member sees, and the enabled state. Discord's app asks for at least seven default channels when configuring this by hand; the API has been observed to accept fewer. Members pick these options themselves, so offering a role that gives moderator or admin powers, or opens channels hidden from everyone, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token saves it.

NameTypeReqDescription
confirm_tokenstring–The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.
default_channelsarray–Channel names or IDs every new member gets.
enabledboolean––
guildstring–Guild (server) name or ID. Omit to use the default guild.
modestring–default counts only default channels toward the constraints; advanced counts prompt option channels too.
promptsarray––

No output schema declared.

No examples provided.

update_role ~423

Edit a role's name, color (solid, gradient, or holographic), icon, hoist, mentionable flag, or permissions. Passing preset and/or permissions replaces the role's permission set with the named bundle plus listed names. Only passed fields change. Supports dry_run. A permission change that would give the role moderator or admin powers (such as banning, kicking, or timing out members, deleting other people's messages, or managing the server, roles, or channels), or let it see channels it cannot see now, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

NameTypeReqDescription
colorstring–Hex color like #00b0f4.
confirm_tokenstring–The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.
dry_runboolean––
guildstring–Guild (server) name or ID. Omit to use the default guild.
hoistboolean––
holographicboolean–Discord's holographic style, which uses its own three colors; false for a solid color. Needs the Enhanced Role Colors server feature.
icon_emojistring–A standard emoji shown beside members' names instead of an image, or none to remove. Needs boost level 2.
icon_urlstring–Public URL of a small image (png, jpeg, webp; 256 KB) shown beside members' names, or none to remove. Needs boost level 2.
mentionableboolean––
namestring––
permissionsarray––
presetstring––
rolestringyesRole name or ID.
secondary_colorstring–A second hex color, so the role name shows a gradient from color to this one; none for a solid color. Needs the Enhanced Role Colors server feature.

No output schema declared.

No examples provided.

update_server ~485

Edit server settings: name, description, icon, banner, invite background, AFK behavior, system and rules channels, verification level, explicit media filter, and default notifications. Images come from public URLs. Only passed fields change. Descriptions need a Community server; the banner and invite background need boosts. A lower verification level, a weaker media filter, or turning Community off lowers the server's protection, so that needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Raising them, and every other setting, happens at once.

NameTypeReqDescription
afk_channelstring–Voice channel name or ID, or none to clear.
afk_timeout_secondsnumber––
banner_urlstring–Public URL of the banner shown at the top of the channel list, or none. Needs boost level 2.
communityboolean–Enable or disable the Community feature. Enabling needs rules_channel and public_updates_channel.
confirm_tokenstring–The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.
default_notificationsstring–What new members are notified of by default.
descriptionstring––
discovery_background_urlstring–Public URL of the Server Discovery background, or none. Needs a discoverable server.
dry_runboolean––
explicit_media_filterstring–Which members' images Discord scans for explicit content.
guildstring–Guild (server) name or ID. Omit to use the default guild.
icon_urlstring–Public URL of the new server icon (png, jpeg, gif, webp), or none to remove it. A gif needs the animated icon feature.
invite_background_urlstring–Public URL of the invite page background (the splash), or none. Needs boost level 1.
namestring––
public_updates_channelstring–Text channel for Discord's mod updates, when enabling Community.
rules_channelstring–Text channel for the rules, when enabling Community.
system_channelstring–Channel for join notices, or none to clear.
verification_levelstring––

No output schema declared.

No examples provided.

update_server_widget ~197

Enable or disable the widget, or point its invite channel. An enabled widget shows the server's name, who is online, and its voice channels to anyone on the web, and with an invite channel it lets anyone join. So turning it on, or pointing it at an invite channel while it is on, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Turning it off or clearing the channel happens at once.

NameTypeReqDescription
channelstring–Invite channel name or ID, or none to clear.
confirm_tokenstring–The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.
enabledboolean––
guildstring–Guild (server) name or ID. Omit to use the default guild.

No output schema declared.

No examples provided.

update_soundboard_sound ~67

Rename a soundboard sound or change its volume.

NameTypeReqDescription
guildstring–Guild (server) name or ID. Omit to use the default guild.
namestring––
soundstringyesSound name or ID.
volumenumber––

No output schema declared.

No examples provided.

update_stage ~57

Change the topic of a live stage.

NameTypeReqDescription
channelstringyesStage channel name or ID.
guildstring–Guild (server) name or ID. Omit to use the default guild.
topicstringyes–

No output schema declared.

No examples provided.

update_sticker ~73

Rename a sticker or change its description and tags.

NameTypeReqDescription
descriptionstring––
guildstring–Guild (server) name or ID. Omit to use the default guild.
namestring––
stickerstringyesSticker name or ID.
tagsstring––

No output schema declared.

No examples provided.

update_thread ~106

Rename a thread, archive or unarchive it, lock or unlock it, or change its slowmode and auto-archive window.

NameTypeReqDescription
archivedboolean––
auto_archive_minutesnumber––
guildstring–Guild (server) name or ID. Omit to use the default guild.
lockedboolean––
namestring––
slowmode_secondsinteger––
threadstringyesThread name or ID.

No output schema declared.

No examples provided.

update_webhook ~86

Rename a webhook, change its avatar, or move it to another channel.

NameTypeReqDescription
avatar_urlstring––
channelstring–Move the webhook to this channel.
guildstring–Guild (server) name or ID. Omit to use the default guild.
namestring––
webhookstringyesWebhook name or ID.

No output schema declared.

No examples provided.

update_welcome_screen ~68

Edit the Community welcome screen: the description and up to five channel cards.

NameTypeReqDescription
channelsarray––
descriptionstring––
enabledboolean––
guildstring–Guild (server) name or ID. Omit to use the default guild.

No output schema declared.

No examples provided.

Install

How do I install the Discord MCP server?

Discord MCP runs locally as an npm package, launched with npx -y @orygn/discord-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @orygn/discord-mcp

# add to Claude Code
claude mcp add orygnscode-discord-mcp -- npx -y @orygn/discord-mcp
Common questions

What is the Discord MCP server?

Discord MCP is listed in the public MCP registry as io.github.OrygnsCode/discord-mcp. Discord server management MCP for AI agents: chat, moderation, admin, and full server building. This page covers its npm package (@orygn/discord-mcp).

Is the Discord MCP server safe to use?

Discord MCP scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Discord MCP server expose?

Discord MCP exposes 164 tools: get_rate_limit_status, get_bot_info, run_setup_check, get_server_overview, list_channels, and 159 more. Their descriptions and schemas cost roughly 22,249 tokens of context every time the server is loaded.

Is the Discord MCP server still maintained?

Discord MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Discord MCP server under?

Discord MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Discord MCP server?

VerifyMCP ran 16 checks on Discord MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.