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.

io.github.jessepetersondev/consentgate-mcp

NPM · CONSENTGATE-MCP · SCANNED SEP 20

Gate AI agent actions behind a consent policy with human approval via Telegram. Fail-closed.

Available components

0 this week 83 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 Security98
  • 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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 517 tokens (~258/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.jessepetersondev/consentgate-mcp server?

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

npm · consentgate-mcp

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

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.80 functional
  • 8 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified functional
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/consentgate-mcp@0.1.1

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~517 tokens

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
check_action ~261

Check whether an action is permitted by the ConsentGate owner's consent policy BEFORE you perform it. Call this for any potentially sensitive, irreversible, or high-impact action — e.g. sending email or messages, posting publicly, spending money, deleting or overwriting files, calling external/destructive APIs, or changing system state. Returns a decision: "allow" (you may proceed), "deny" (do NOT proceed), or "ask" (no rule matched — not approval; use request_approval to get a human decision, or ask the user). This call does not block. FAIL CLOSED: if the result is anything other than "allow", do not perform the action.

NameTypeReqDescription
actionstringyesThe specific action you intend to take, e.g. "send_email", "delete_file", "transfer_funds".
categorystringyesAction category. Built-in categories: email, social_post, message, file_write, file_delete, api_call, spending, calendar, system, custom. Any short label (<=50 chars) is accepted.
metadataobjectStructured details of the action (e.g. recipient, amount, path, url). Used by the owner's rules and shown in any approval prompt. Max 10KB.

No output schema declared.

No examples provided.

request_approval ~256

Request a human's explicit approval for an action and BLOCK until they decide or the timeout elapses. Use for high-stakes actions, or whenever check_action returned "ask". The owner gets an Approve/Deny prompt on Telegram. Returns "allow" ONLY if a human tapped Approve. Returns "deny" on tap-deny, on timeout (fail-closed), or when interactive approvals are unavailable (owner not on Pro, or Telegram not linked — see upgrade_required / telegram_linked). NEVER treat a non-"allow" result as permission.

NameTypeReqDescription
actionstringyesThe specific action requiring approval, e.g. "send_email", "transfer_funds".
categorystringyesAction category. Built-in categories: email, social_post, message, file_write, file_delete, api_call, spending, calendar, system, custom. Any short label (<=50 chars) is accepted.
metadataobjectStructured details shown to the human in the approval prompt (e.g. recipient, amount, summary). Max 10KB.
wait_secondsintegerHow long to block waiting for the human's tap (1-120s). On timeout the result fails closed to "deny".

No output schema declared.

No examples provided.

Common questions

What is the io.github.jessepetersondev/consentgate-mcp server?

io.github.jessepetersondev/consentgate-mcp is listed in the public MCP registry as io.github.jessepetersondev/consentgate-mcp. Gate AI agent actions behind a consent policy with human approval via Telegram. Fail-closed. This page covers its npm package (consentgate-mcp).

Is the io.github.jessepetersondev/consentgate-mcp server safe to use?

io.github.jessepetersondev/consentgate-mcp scores 83 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. 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.

What tools does the io.github.jessepetersondev/consentgate-mcp server expose?

io.github.jessepetersondev/consentgate-mcp exposes 2 tools: check_action, request_approval. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.

Is the io.github.jessepetersondev/consentgate-mcp server still maintained?

io.github.jessepetersondev/consentgate-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 io.github.jessepetersondev/consentgate-mcp server under?

io.github.jessepetersondev/consentgate-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.