GuildControl MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to GuildControl scoped Discord reads and reviewed administration: Do bot-identity checks and private-user allowlists preserve minimized reads before any administrative mutation?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Safety-first Discord search/audit/administration with explicit toolsets and reviewed changes.

What we know

Discord MCP focused on privacy-safe reads, auditing and scoped administration. Discord permissions are the outer boundary and connector policy/toolsets narrow authority further.

Maintenance / activity evidence

guildctl 2.3.0 published 2026-09-15T00:03:26.652Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read/audit plus selected admin authority constrained by Discord permission and toolset/policy gates. Reported action classes: Potentially manage commands/webhooks/integrations/invites/templates/settings/AutoMod/events depending on enabled toolsets. Complete write authority is not verified.
Discord application/bot credentials.
Sensitive access: Discord messages/community config, Member/admin data, Bot credentials

Community administration has high blast radius; use least-privilege Discord permissions and narrow toolsets.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do bot-identity checks and private-user allowlists preserve minimized reads before any administrative mutation?

The bounded review of the publisher's documented GuildControl scoped Discord reads and reviewed administration and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Community administration has high blast radius; use least-privilege Discord permissions and narrow toolsets.
Read/audit plus selected admin authority constrained by Discord permission and toolset/policy gates.
Discord application/bot credentials.
Discord content/configuration is processed through the connector.
Reviewed write actions: Potentially manage commands/webhooks/integrations/invites/templates/settings/AutoMod/events depending on enabled toolsets
Sensitive access: Discord messages/community config, Member/admin data, Bot credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
exact install/auth env
full write-tool inventory
Toolset selection does not itself grant Discord permission; bot/user permissions remain authoritative.
Administrative actions can alter live communities.
Exact credential/setup fields were not fully captured in this pass.

Original activity observations

guildctl 2.3.0 published 2026-09-15T00:03:26.652Z

Technical identity

npm/guildctl

Exact implementation source: https://www.npmjs.com/package/guildctl ↗
Reviewed resource type: MCP Server
Repository identity: j-256/guildcontrol
Package identity: npm:guildctl

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
guildctl
Recorded package identity, distribution or download evidence.
GitHub repository ↗
j-256/guildcontrol
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Discord bot credential; multistep preset/config/host and scope controls; setup CLI may write configs; review exact syntax before execution
Targeted 2026-10-13 re-research: Discord bot/host connector requires bot token, guild ID, least-privilege preset, validated config; use official multi-step onboarding.
Discord bot/host connector requires bot token, guild ID, least-privilege preset, validated config; use official multi-step onboarding.
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Discord bot setup requires owner-managed bot identity, preset scopes and host activation; V1 single setup command is insufficient for complete MCP deployment.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Discord bot credential; multistep preset/config/host and scope controls; setup CLI may write configs; review exact syntax before execution | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npx --yes guildctl@2.3.1 setup --npx
Configure / authenticate
MCP100 setup guide
Conditional or different product type. npm package install is not proof of MCP registration. Discord bot credential; multistep preset/config/host and scope controls; setup CLI may write configs; review exact syntax before execution Verify the correct host/transport from the publisher README; secure credentials in local client settings.
Required environment variables: DISCORD_BOT_TOKEN
Check connection
Suggested check
Use read-only guildctl catalog or publisher onboarding health checks and verify explicitly configured MCP tools; never install Discord bot or grant permissions merely as a smoke check.
Remove / uninstall / revoke
MCP100 setup guide
If your Claude Code MCP registration is named `guildctl`, run the client removal command. For Claude Desktop/Cursor/Codex or another registered name, remove the matching entry in that host’s MCP settings. Hosted OAuth disconnect and stopping a self-hosted process are separate; npx has no permanent global package install.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove guildctl

Official Documentation & Sources

What it does

Discord MCP focused on privacy-safe reads, auditing and scoped administration. Discord permissions are the outer boundary and connector policy/toolsets narrow authority further.

Capability: Communication
Resource type: MCP Server
Best fit: Safety-first Discord search/audit/administration with explicit toolsets and reviewed changes.

Representative uses

Search/read Discord safely
Audit guild/community configuration
Review integrations/webhooks/invites/AutoMod/events
Perform selected administration under explicit policy gates

Limitations

Toolset selection does not itself grant Discord permission; bot/user permissions remain authoritative.
Administrative actions can alter live communities.
Exact credential/setup fields were not fully captured in this pass.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Discord application/bot credentials.
Permissions: Read/audit plus selected admin authority constrained by Discord permission and toolset/policy gates.
Data handling: Discord content/configuration is processed through the connector.
Cost: unknown
Risk and cautions: Community administration has high blast radius; use least-privilege Discord permissions and narrow toolsets.

Access scope and cautions

Write actions: Not verified Potentially manage commands/webhooks/integrations/invites/templates/settings/AutoMod/events depending on enabled toolsets
Sensitive access: Discord messages/community config Member/admin data Bot credentials
Risk level: high

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Search/read Discord safely; Audit guild/community configuration; Review integrations/webhooks/invites/AutoMod/events; Perform selected administration under explicit policy gates.

What authentication is documented?

Discord permissions plus local connector policy.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Potentially manage commands/webhooks/integrations/invites/templates/settings/AutoMod/events depending on enabled toolsets. Recorded permission context: Read/audit plus selected admin authority constrained by Discord permission and toolset/policy gates.

What data-handling boundary should I consider?

Discord content/configuration is processed through the connector. Recorded sensitive-access context: Discord messages/community config; Member/admin data; Bot credentials.

What limitations and risks should I check before use?

Community administration has high blast radius; use least-privilege Discord permissions and narrow toolsets. Toolset selection does not itself grant Discord permission; bot/user permissions remain authoritative. Administrative actions can alter live communities. Exact credential/setup fields were not fully captured in this pass. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.