Discord (iflow-mcp) MCP Server

@iflow-mcp/discord-mcp npm v0.0.3

Published by @iflow-mcp — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Model Context Protocol (MCP) server for Discord API integration

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: read_messages → read_private_messages → create_webhook. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow read_messages → read_private_messages → create_webhook

Tools 93

Each tool and what it can reach — statically extracted from the published source.

  • read_private_messagesingests untrusted inputreads sensitive data
  • create_webhooknetwork egress
  • crosspost_messagenetwork egress
  • delete_webhooknetwork egress
  • read_messagesingests untrusted input
  • send_messagenetwork egress
  • send_webhook_messagenetwork egress
  • upload_filenetwork egress
  • add_reactionno sensitive capability
  • add_role_to_memberno sensitive capability
Show 83 more tools ↓
  • bulk_delete_messagesno sensitive capability
  • bulk_set_privacyno sensitive capability
  • comprehensive_channel_managementno sensitive capability
  • create_announcement_channelno sensitive capability
  • create_automod_ruleno sensitive capability
  • create_categoryno sensitive capability
  • create_emojino sensitive capability
  • create_eventno sensitive capability
  • create_forum_channelno sensitive capability
  • create_inviteno sensitive capability
  • create_roleno sensitive capability
  • create_stage_channelno sensitive capability
  • create_stickerno sensitive capability
  • create_text_channelno sensitive capability
  • create_voice_channelno sensitive capability
  • delete_automod_ruleno sensitive capability
  • delete_categoryno sensitive capability
  • delete_channelno sensitive capability
  • delete_emojino sensitive capability
  • delete_eventno sensitive capability
  • delete_inviteno sensitive capability
  • delete_messageno sensitive capability
  • delete_private_messageno sensitive capability
  • delete_roleno sensitive capability
  • delete_stickerno sensitive capability
  • discord_manageno sensitive capability
  • edit_automod_ruleno sensitive capability
  • edit_channel_advancedno sensitive capability
  • edit_eventno sensitive capability
  • edit_memberno sensitive capability
  • edit_messageno sensitive capability
  • edit_private_messageno sensitive capability
  • edit_roleno sensitive capability
  • edit_serverno sensitive capability
  • edit_welcome_screenno sensitive capability
  • export_chat_logno sensitive capability
  • find_categoryno sensitive capability
  • find_channelno sensitive capability
  • get_automod_rulesno sensitive capability
  • get_channel_structureno sensitive capability
  • get_emojisno sensitive capability
  • get_eventsno sensitive capability
  • get_invitesno sensitive capability
  • get_member_infono sensitive capability
  • get_membersno sensitive capability
  • get_message_attachmentsno sensitive capability
  • get_message_historyno sensitive capability
  • get_pinned_messagesno sensitive capability
  • get_rolesno sensitive capability
  • get_server_infono sensitive capability
  • get_server_statsno sensitive capability
  • get_server_widgetno sensitive capability
  • get_stickersno sensitive capability
  • get_user_id_by_nameno sensitive capability
  • get_voice_connectionsno sensitive capability
  • get_welcome_screenno sensitive capability
  • join_voice_channelno sensitive capability
  • leave_voice_channelno sensitive capability
  • list_channelsno sensitive capability
  • list_channels_in_categoryno sensitive capability
  • list_webhooksno sensitive capability
  • move_channel_to_categoryno sensitive capability
  • organize_channelsno sensitive capability
  • pin_messageno sensitive capability
  • play_audiono sensitive capability
  • read_imagesno sensitive capability
  • remove_reactionno sensitive capability
  • remove_role_from_memberno sensitive capability
  • search_membersno sensitive capability
  • send_buttonno sensitive capability
  • send_embedno sensitive capability
  • send_modalno sensitive capability
  • send_private_messageno sensitive capability
  • send_select_menuno sensitive capability
  • set_category_positionno sensitive capability
  • set_category_privateno sensitive capability
  • set_channel_positionno sensitive capability
  • set_channel_positionsno sensitive capability
  • set_channel_privateno sensitive capability
  • set_role_positionsno sensitive capability
  • set_volumeno sensitive capability
  • stop_audiono sensitive capability
  • unpin_messageno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.0.3 latest A 93/100 1 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/iflow-mcp-discord-mcp/badge.svg)](https://mcptrustchecker.com/registry/iflow-mcp-discord-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/iflow-mcp-discord-mcp"><img src="https://mcptrustchecker.com/registry/iflow-mcp-discord-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/iflow-mcp-discord-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @iflow-mcp/discord-mcp --online

Use the free API → How scoring works

Other implementations of Discord 24

Independent packages implementing the same tool, scanned with the same engine. Compare all 25 side by side →

More in Communication & Collaboration