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.cookiechain/cookie-mcp

NPM · COOKIE-MCP · SCANNED SEP 20

Cookie Chain tools for AI agents: swap, launch, liquidity, staking, NFTs, and a Solana bridge.

Available components

+15 this week 77 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 Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects toml 3.0.0, reached via @coral-xyz/anchor > toml. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 73 of 213 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 9135 tokens (~172/item across 53 items; 53 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 Management82
  • Stability check failed: the tool surface changed between 0.2.2 and 0.5.0: 0 tool removals, 1 breaking changes, 21 additions. See how to fix → Fail
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "trade" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 53 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.cookiechain/cookie-mcp server?

io.github.cookiechain/cookie-mcp runs locally as an npm package, launched with npx -y cookie-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 · cookie-mcp

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

  • 19 Sept 26 −3

    No change was recorded against any check on this day. Stability & Change Management went from 98 to 78.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 95 to 98.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 88 to 92.

  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 0
    • Malware scan: unverified → pass security
    • Package version: 0.4.0 → 0.5.0 functional
  • 13 Sept 26 −19
    • Malware scan: pass → unverified security
    • Stability: pass → fail security
    • Schema quality: 110 → 167 functional
    • Security disclosure: fail → unverified functional
    • Stability: pass → 0.83 functional
    • Package version: 0.2.2 → 0.4.0 functional
  • 12 Sept 26 +1
    • Stability: 0.97 → pass security
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/cookie-mcp@0.5.0

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 →

Vulnerabilities 5 findings
ID CVE Severity Vector Fix available
GHSA-3gc7-fjrx-p6mg CVE-2025-3194 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
GHSA-528h-pc64-c93x CVE-2026-71429 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-82x6-q7mm-w9cf CVE-2026-77465 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-v5mp-jgw5-2x6j CVE-2026-63376 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 213 packages
Packages resolved 213
Deprecated 2
Stale 68
No linked repository 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 53 exposed · ~9,135 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
transfer_domain ~129

Hand a .cook name you own to another wallet. FINAL — only the new owner can move it again. If the name is this wallet's primary, the primary record is cleared in the same instruction so it cannot point at a name the wallet no longer owns. The recipient can be given as an address or as a .cook name. Simulates before sending. Requires COOKIE_PRIVATE_KEY.

NameTypeReqDescription
namestringyesthe .cook name, with or without the suffix (e.g. "bot" or "bot.cook")
tostringyesrecipient wallet address or .cook name

No output schema declared.

No examples provided.

unstake ~95

Redeem bCOOK back to COOK instantly from the pool's liquid reserve (≈ amount × rate × 0.98, after the 2% withdrawal fee). Burns bCOOK and pays COOK to your wallet. Simulates first; honors the spend cap (valued in COOK). Requires COOKIE_PRIVATE_KEY.

NameTypeReqDescription
amountyesUI amount of bCOOK to unstake, e.g. 5

No output schema declared.

No examples provided.

update_domain ~140

Set or clear the `resolver` and `metadata` pubkey pointers on a .cook name you own. The program stores them without interpreting them — they are hooks for apps. Pass "none" to clear one. At least one of `resolver`/`metadata` is required. Requires COOKIE_PRIVATE_KEY.

NameTypeReqDescription
metadatastringmetadata account (base58), or "none" to clear it
namestringyesthe .cook name, with or without the suffix (e.g. "bot" or "bot.cook")
resolverstringresolver account (base58), or "none" to clear it

No output schema declared.

No examples provided.

Common questions

What is the io.github.cookiechain/cookie-mcp server?

io.github.cookiechain/cookie-mcp is listed in the public MCP registry as io.github.cookiechain/cookie-mcp. Cookie Chain tools for AI agents: swap, launch, liquidity, staking, NFTs, and a Solana bridge. This page covers its npm package (cookie-mcp).

Is the io.github.cookiechain/cookie-mcp server safe to use?

io.github.cookiechain/cookie-mcp scores 77 out of 100 on VerifyMCP. We recorded 5 known advisories against 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.cookiechain/cookie-mcp server expose?

io.github.cookiechain/cookie-mcp exposes 53 tools: submit_signed_tx, chain_health, get_pools, get_token_info, search_tokens, and 48 more. Their descriptions and schemas cost roughly 9,135 tokens of context every time the server is loaded.

Is the io.github.cookiechain/cookie-mcp server still maintained?

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

io.github.cookiechain/cookie-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.