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.cookinfun/cookin-mcp

NPM · @COOKINFUN/MCP

Solana and Pump.fun token intelligence: bundles, holder quality, KOLs, deployer history.

Available components

+5 this week 85 Trust /100

Last scanned (7 hours ago)

Scores higher than 87% of npm servers

Category Crypto and Web3

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 Security99
  • 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
  • 30 of 151 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 645 tokens (~80/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 30 Oct 26 +3
    • CVE-2023-54404 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 −2
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 22 Oct 26 +1

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

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 5 Nov 2026 · Analysed npm/@cookinfun/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 151 packages
Packages resolved 151
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~645 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
deployer_history ~110

Every token one deployer has launched, with its bond rate, peak market caps, and a survival curve across market cap rungs. Changes slowly, so cache the answer. Costs $0.01 per call (no payment configured, calls will return 402).

NameTypeReqDescription
addressstringyesDeployer wallet address, base58.
limitinteger–Tokens per page, 1 to 100. Default 50.
offsetinteger–Tokens to skip. Default 0.

No output schema declared.

No examples provided.

list_agent_buys ~62

Tokens the top Cookin trading agents bought most recently, with quality signals. The most-bought Cookin endpoint: it answers what proven strategies are doing right now. Costs $0.01 per call (no payment configured, calls will return 402).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_graduated_tokens ~49

Pump.fun tokens that recently graduated to Raydium or PumpSwap, with quality signals and ratings. Costs $0.01 per call (no payment configured, calls will return 402).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_new_tokens ~52

Newly launched Pump.fun tokens that passed Cookin's rug filters, with quality signals and ratings. Use it to find candidates. Costs $0.01 per call (no payment configured, calls will return 402).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_pumping_tokens ~44

Pump.fun tokens currently pumping, with quality signals, holder behavior, and ratings. Costs $0.01 per call (no payment configured, calls will return 402).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

profile_wallet ~86

Lifetime trading profile of one Solana wallet: PnL, ROI, win rate, hold times, bundle and smart-money flags, recent tokens traded. Use it to judge a buyer or seller you saw in a trade list. Costs $0.01 per call (no payment configured, calls will return 402).

NameTypeReqDescription
addressstringyesSolana wallet address, base58.

No output schema declared.

No examples provided.

scan_token ~155

Full Cookin snapshot for one Solana or Pump.fun token: quality score, holders, bundles (coordinated wallets), KOL positions, holder behavior cohorts, pump/dump signals, and a green/yellow/red rating per metric. The first call to make about a token, at any stage of its life. Costs $0.02 per call (no payment configured, calls will return 402).

NameTypeReqDescription
fieldsstring–Comma-separated groups to return, for a smaller response at the same price: meta, status, market, holders, bundles, score, cohorts, kols, signals, ratings. Omit for all of them.
mintstringyesSolana token mint address, base58.

No output schema declared.

No examples provided.

token_trades ~87

Recent trades for one token, each carrying the trader's history as it stood at that moment: PnL, win rate, bundle membership, smart-money flag. Use it to see who is buying or selling right now. Costs $0.01 per call (no payment configured, calls will return 402).

NameTypeReqDescription
mintstringyesSolana token mint address, base58.

No output schema declared.

No examples provided.

Install

How do I install the io.github.cookinfun/cookin-mcp server?

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

# add to Claude Code
claude mcp add cookinfun-cookin-mcp -- npx -y @cookinfun/mcp
Common questions

What is the io.github.cookinfun/cookin-mcp server?

io.github.cookinfun/cookin-mcp is listed in the public MCP registry as io.github.cookinfun/cookin-mcp. Solana and Pump.fun token intelligence: bundles, holder quality, KOLs, deployer history. This page covers its npm package (@cookinfun/mcp).

Is the io.github.cookinfun/cookin-mcp server safe to use?

io.github.cookinfun/cookin-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.cookinfun/cookin-mcp server expose?

io.github.cookinfun/cookin-mcp exposes 8 tools: scan_token, token_trades, list_new_tokens, list_pumping_tokens, list_graduated_tokens, and 3 more. Their descriptions and schemas cost roughly 645 tokens of context every time the server is loaded.

Is the io.github.cookinfun/cookin-mcp server still maintained?

io.github.cookinfun/cookin-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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.cookinfun/cookin-mcp server under?

io.github.cookinfun/cookin-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.