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

NPM · GUILDCTL · 3 COMPONENTS · SCANNED SEP 20

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

Available components

mcpb · guildcontrol-2.3.0.mcpb 14 npm · guildctl 50 oci · ghcr.io/j-256/guildcontrol:2.3.0 14
0 this week 50 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 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
  • 3 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to j-256/guildcontrol). View diagnostics → Pass
  • Clear OSI-approved license (AGPL-3.0-only).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the GuildControl MCP server?

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

npm · guildctl

# add to Claude Code
claude mcp add app-lasers-guildcontrol-discord -- npx -y guildctl
// .cursor/mcp.json
{
  "mcpServers": {
    "app-lasers-guildcontrol-discord": {
      "command": "npx",
      "args": [
        "-y",
        "guildctl"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "app-lasers-guildcontrol-discord": {
      "command": "npx",
      "args": [
        "-y",
        "guildctl"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add app-lasers-guildcontrol-discord -- npx -y guildctl
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-lasers-guildcontrol-discord": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "guildctl"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add app-lasers-guildcontrol-discord --command npx --arg -y --arg guildctl
# ~/.hermes/config.yaml
mcp_servers:
  app-lasers-guildcontrol-discord:
    command: "npx"
    args: ["-y", "guildctl"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "app-lasers-guildcontrol-discord": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "guildctl"
      ]
    }
  }
}
# add to Vellum
assistant mcp add app-lasers-guildcontrol-discord -t stdio -c npx -a -y guildctl
// mcp.json
{
  "mcpServers": {
    "app-lasers-guildcontrol-discord": {
      "command": "npx",
      "args": [
        "-y",
        "guildctl"
      ]
    }
  }
}
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.

  • 16 Sept 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
  • 15 Sept 26 0
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 2.2.0 → 2.3.0 functional
  • 4 Sept 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan. security
    • Dependency health: unverified → 0.98 ▲ functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
  • 3 Sept 26 −11
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Dependency health: 0.98 → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Package version: 0.4.0 → 2.2.0 functional
  • 2 Sept 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan. security
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
  • 1 Sept 26 50

    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 20 Sept 2026 · Analysed npm/guildctl@2.3.0

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 j-256/guildcontrol
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/j-256/guildcontrol/.github/workflows/release.yml@refs/tags/v2.3.0
Rekor log index 2836634820
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:123bdcd70e203bf984d9d2f6baaf8fc7e5d2ec2545b8d888477d351e6369274a83b1512999967a5a28d5154ba418b6bd5f4aef146f79e05cc3a2397f9

Background: How many MCP packages publish verified provenance →

Dependencies 29 packages
Packages resolved 29
Stale 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

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 npm package (guildctl).

Is the GuildControl MCP server safe to use?

GuildControl MCP scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.

Is the GuildControl MCP server still maintained?

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