Omnicord MCP Server

@orygn/omnicord npm v1.3.0

Published by @orygn — 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.

Omnicord: an MCP server for Discord. Chat, moderate, administrate, and build out entire servers through any MCP client.

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 12

high Tool "update_app_command" exposes command/code executionMTC-CAP-001

Tool "update_app_command" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool update_app_command

high Tool "delete_app_command" exposes command/code executionMTC-CAP-001

Tool "delete_app_command" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool delete_app_command

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([get_message, read_messages]) co-exist with external-action tools ([update_app_command, delete_app_command, create_webhook, update_webhook, delete_webhook, send_webhook_message, crosspost_message, lock_channel, unlock_channel, send_message, forward_message]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [get_message, read_messages] → sinks [update_app_command, delete_app_command, create_webhook, update_webhook, delete_webhook, send_webhook_message, cr

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow get_message → update_app_command

medium Hardcoded egress to an external endpoint (dist/wizard.js)MTC-SRC-003

In the server's implementation (`dist/wizard.js:122`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { const res = await fetch(`https://discord.com/api/v10${path}`, { headers: { Authorization: `Bot ${token}` }

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/wizard.js

medium Unconstrained URL/host parameter "avatar_url" on "create_webhook"MTC-CAP-007

Tool "create_webhook" takes a URL/host parameter "avatar_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool create_webhook · inputSchema.properties.avatar_url

medium Unconstrained URL/host parameter "avatar_url" on "update_webhook"MTC-CAP-007

Tool "update_webhook" takes a URL/host parameter "avatar_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool update_webhook · inputSchema.properties.avatar_url

medium Unconstrained URL/host parameter "avatar_url_override" on "send_webhook_message"MTC-CAP-007

Tool "send_webhook_message" takes a URL/host parameter "avatar_url_override" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool send_webhook_message · inputSchema.properties.avatar_url_override

medium Unconstrained command parameter "command" on "update_app_command"MTC-CAP-006

Tool "update_app_command" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool update_app_command · inputSchema.properties.command

medium Unconstrained command parameter "command" on "delete_app_command"MTC-CAP-006

Tool "delete_app_command" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool delete_app_command · inputSchema.properties.command

medium Dynamic module load from a non-literal (dist/config.js)MTC-SRC-005

In the server's implementation (`dist/config.js:30`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: t: true }); const pkg = require(packageJsonPath); export const VERSION = pkg.version; // Pure: given a parsed bots.json

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/config.js

low Mutating tool "update_app_command" declares no destructiveHintMTC-CAP-005

Tool "update_app_command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool update_app_command

low Mutating tool "delete_app_command" declares no destructiveHintMTC-CAP-005

Tool "delete_app_command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool delete_app_command

Tools 155

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

  • create_webhooknetwork egress
  • crosspost_messagenetwork egress
  • delete_app_commandruns code / shell
  • delete_webhooknetwork egress
  • forward_messagenetwork egress
  • get_messageingests untrusted input
  • lock_channelnetwork egress
  • read_messagesingests untrusted input
  • send_messagenetwork egress
  • send_webhook_messagenetwork egress
Show 145 more tools ↓
  • unlock_channelnetwork egress
  • update_app_commandruns code / shell
  • update_webhooknetwork egress
  • add_reactionsno sensitive capability
  • add_thread_memberno sensitive capability
  • assign_roleno sensitive capability
  • ban_memberno sensitive capability
  • bulk_banno sensitive capability
  • bulk_delete_messagesno sensitive capability
  • bulk_update_rolesno sensitive capability
  • cancel_eventno sensitive capability
  • cancel_scheduled_messageno sensitive capability
  • clear_channel_permissionsno sensitive capability
  • clear_reactionsno sensitive capability
  • clone_channelno sensitive capability
  • clone_roleno sensitive capability
  • create_automod_ruleno sensitive capability
  • create_channelno sensitive capability
  • create_emojino sensitive capability
  • create_eventno sensitive capability
  • create_forum_postno sensitive capability
  • create_forum_tagno sensitive capability
  • create_inviteno sensitive capability
  • create_pollno sensitive capability
  • create_roleno sensitive capability
  • create_server_templateno sensitive capability
  • create_soundboard_soundno sensitive capability
  • create_stickerno sensitive capability
  • create_threadno sensitive capability
  • delete_automod_ruleno sensitive capability
  • delete_blueprintno sensitive capability
  • delete_channelno sensitive capability
  • delete_emojino sensitive capability
  • delete_forum_postno sensitive capability
  • delete_forum_tagno sensitive capability
  • delete_integrationno sensitive capability
  • delete_inviteno sensitive capability
  • delete_messageno sensitive capability
  • delete_roleno sensitive capability
  • delete_server_templateno sensitive capability
  • delete_soundboard_soundno sensitive capability
  • delete_stickerno sensitive capability
  • delete_threadno sensitive capability
  • diff_blueprintno sensitive capability
  • disconnect_memberno sensitive capability
  • edit_messageno sensitive capability
  • end_pollno sensitive capability
  • end_stageno sensitive capability
  • execute_build_planno sensitive capability
  • explain_permissionsno sensitive capability
  • export_server_blueprintno sensitive capability
  • findno sensitive capability
  • follow_announcement_channelno sensitive capability
  • get_audit_logno sensitive capability
  • get_blueprintno sensitive capability
  • get_bot_infono sensitive capability
  • get_channelno sensitive capability
  • get_channel_permissionsno sensitive capability
  • get_eventno sensitive capability
  • get_event_attendeesno sensitive capability
  • get_inviteno sensitive capability
  • get_memberno sensitive capability
  • get_member_permissionsno sensitive capability
  • get_onboardingno sensitive capability
  • get_poll_resultsno sensitive capability
  • get_rate_limit_statusno sensitive capability
  • get_reactionsno sensitive capability
  • get_recent_eventsno sensitive capability
  • get_reference_layoutno sensitive capability
  • get_role_membersno sensitive capability
  • get_server_overviewno sensitive capability
  • get_server_previewno sensitive capability
  • get_server_widgetno sensitive capability
  • get_threadno sensitive capability
  • get_welcome_screenno sensitive capability
  • kick_memberno sensitive capability
  • list_app_commandsno sensitive capability
  • list_automod_rulesno sensitive capability
  • list_bansno sensitive capability
  • list_blueprintsno sensitive capability
  • list_channelsno sensitive capability
  • list_emojisno sensitive capability
  • list_event_subscriptionsno sensitive capability
  • list_eventsno sensitive capability
  • list_forum_postsno sensitive capability
  • list_integrationsno sensitive capability
  • list_invitesno sensitive capability
  • list_membersno sensitive capability
  • list_pinned_messagesno sensitive capability
  • list_reference_layoutsno sensitive capability
  • list_rolesno sensitive capability
  • list_scheduled_messagesno sensitive capability
  • list_server_templatesno sensitive capability
  • list_serversno sensitive capability
  • list_soundboard_soundsno sensitive capability
  • list_stagesno sensitive capability
  • list_stickersno sensitive capability
  • list_thread_membersno sensitive capability
  • list_threadsno sensitive capability
  • list_voice_membersno sensitive capability
  • list_webhooksno sensitive capability
  • pin_messageno sensitive capability
  • plan_server_buildno sensitive capability
  • prune_membersno sensitive capability
  • register_app_commandno sensitive capability
  • remove_reactionno sensitive capability
  • remove_roleno sensitive capability
  • remove_thread_memberno sensitive capability
  • remove_timeoutno sensitive capability
  • reorder_channelsno sensitive capability
  • reorder_rolesno sensitive capability
  • reply_to_forum_postno sensitive capability
  • run_setup_checkno sensitive capability
  • save_blueprintno sensitive capability
  • schedule_messageno sensitive capability
  • search_membersno sensitive capability
  • search_messagesno sensitive capability
  • send_dmno sensitive capability
  • set_bot_presenceno sensitive capability
  • set_channel_permissionsno sensitive capability
  • set_incident_actionsno sensitive capability
  • set_voice_channel_statusno sensitive capability
  • start_stageno sensitive capability
  • subscribe_eventsno sensitive capability
  • sync_server_templateno sensitive capability
  • timeout_memberno sensitive capability
  • unban_memberno sensitive capability
  • unpin_messageno sensitive capability
  • unsubscribe_eventsno sensitive capability
  • update_automod_ruleno sensitive capability
  • update_channelno sensitive capability
  • update_emojino sensitive capability
  • update_eventno sensitive capability
  • update_forum_postno sensitive capability
  • update_forum_tagno sensitive capability
  • update_memberno sensitive capability
  • update_onboardingno sensitive capability
  • update_roleno sensitive capability
  • update_serverno sensitive capability
  • update_server_widgetno sensitive capability
  • update_soundboard_soundno sensitive capability
  • update_stageno sensitive capability
  • update_stickerno sensitive capability
  • update_threadno sensitive capability
  • update_welcome_screenno 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 3

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
v1.3.0 latest A 93/100 12 1.13.0 2026-09-07
v1.2.1 A 96/100 6 1.12.1 2026-08-10
v1.2.0 A 96/100 6 1.12.1 2026-08-02

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/orygn-omnicord/badge.svg)](https://mcptrustchecker.com/registry/orygn-omnicord)
HTML
<a href="https://mcptrustchecker.com/registry/orygn-omnicord"><img src="https://mcptrustchecker.com/registry/orygn-omnicord/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/orygn-omnicord/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 @orygn/omnicord --online

Use the free API → How scoring works

More in Productivity & Workflow