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.

GuildControl MCP

OCI · GHCR.IO/J-256/GUILDCONTROL:2.3.0 · 3 COMPONENTS · SCANNED SEP 21

Safety-first MCP server for Discord with privacy-safe reads, audits, and reviewed administration

14 Trust /100
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 Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (AGPL-3.0-only).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, so we will not judge it on a partial copy.Unverified
Stability & Change Management0
  • Stability not yet verified: the captured schema was too large for us to store in full, and comparing a partial copy would report our own trimming as a change.Unverified
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, so we will not judge them on a partial copy.Unverified
Tool Safety0
  • Tool safety not yet verified: the captured tool definitions were too large for us to store in full, and the trim removes the very descriptions this category reads.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass

Unverified: 5 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the GuildControl MCP server?

GuildControl MCP runs locally as a container image, launched with docker run --rm -i ghcr.io/j-256/guildcontrol:2.3.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/j-256/guildcontrol:2.3.0

# add to Claude Code
claude mcp add app-lasers-guildcontrol-discord -- docker run --rm -i ghcr.io/j-256/guildcontrol:2.3.0
// .cursor/mcp.json
{
  "mcpServers": {
    "app-lasers-guildcontrol-discord": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/j-256/guildcontrol:2.3.0"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "app-lasers-guildcontrol-discord": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/j-256/guildcontrol:2.3.0"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add app-lasers-guildcontrol-discord -- docker run --rm -i ghcr.io/j-256/guildcontrol:2.3.0
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-lasers-guildcontrol-discord": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/j-256/guildcontrol:2.3.0"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  app-lasers-guildcontrol-discord:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/j-256/guildcontrol:2.3.0"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "app-lasers-guildcontrol-discord": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/j-256/guildcontrol:2.3.0"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "app-lasers-guildcontrol-discord": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/j-256/guildcontrol:2.3.0"
      ]
    }
  }
}
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.

  • 15 Sept 26 14

    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 Sept 2026 · Analysed oci/ghcr.io/j-256/guildcontrol:2.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 260 exposed · ~36,310 tokens partial

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
send_discord_interaction_followup ~134

No description provided.

NameTypeReqDescription
keepOpenboolean
referencestringyes
responsestringyes
NameTypeReqDescription
schemaVersionintegeryes
statusstringyes

No examples provided.

send_message ~133

No description provided.

NameTypeReqDescription
channelIdstringyes
contentstringyes
idempotencyKeystringyes
notifyReplyAuthorboolean
notifyUserIdsarray
replyToMessageIdstring
NameTypeReqDescription
schemaVersionintegeryes
statusstringyes

No examples provided.

send_webhook_message ~141

No description provided.

NameTypeReqDescription
contentstringyes
notifyUserIdsarray
operationKeystringyes
webhookIdstringyes
NameTypeReqDescription
schemaVersionintegeryes
statusstringyes

No examples provided.

signal_command_processing ~121

No description provided.

NameTypeReqDescription
channelIdstringyes
sourceMessageIdstringyes
NameTypeReqDescription
schemaVersionintegeryes
statusstringyes

No examples provided.

verify_automod_change ~94

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
schemaVersionintegeryes
statusstringyes

No examples provided.

verify_component_message ~132

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
schemaVersionintegeryes
statusstringyes

No examples provided.

verify_direct_message_change ~127

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
schemaVersionintegeryes
statusstringyes

No examples provided.

verify_embed_message ~90

No description provided.

Input schema present but exposes no named parameters.

NameTypeReqDescription
schemaVersionintegeryes
statusstringyes

No examples provided.

verify_guild_blueprint ~296

No description provided.

NameTypeReqDescription
auditReasonstringyes
autoModerationRulesarray
channelMetadataarray
channelOrdersarray
channelPermissionOverwritesarray
communityobject
guildIdstringyes
onboardingobject
operationKeystringyes
profileobject
publicationsarray
roleConfigurationsarray
roleOrderarray
scaffoldobjectyes
settingsobject
welcomeScreenobject
NameTypeReqDescription
schemaVersionintegeryes
statusstringyes

No examples provided.

verify_guild_scaffold ~145

No description provided.

NameTypeReqDescription
auditReasonstringyes
channelsarray
guildIdstringyes
operationKeystringyes
rolesarray
stepLimitinteger
NameTypeReqDescription
schemaVersionintegeryes
statusstringyes

No examples provided.

Common questions

What is the GuildControl MCP server?

GuildControl MCP is listed in the public MCP registry as app.lasers.guildcontrol/discord. Safety-first MCP server for Discord with privacy-safe reads, audits, and reviewed administration. This page covers its container image (ghcr.io/j-256/guildcontrol:2.3.0).

Is the GuildControl MCP server safe to use?

GuildControl MCP scores 14 out of 100 on VerifyMCP. 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.

Is the GuildControl MCP server still maintained?

GuildControl MCP is still listed as active in the MCP registry. We last reached this channel on 21 September 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 GuildControl MCP server under?

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