
Cookin Mcp
io.github.cookinfunv0.1.1Updated Oct 4, 2026
Solana and Pump.fun token intelligence: bundles, holder quality, KOLs, deployer history.
Overview
Gives an assistant Solana and Pump.fun token intelligence: bundles, holder quality, KOL positions, wallet reputation, and deployer history.
- What it does
- Exposes eight tools over stdio that query the Cookin API for token and wallet intelligence. scan_token returns a full snapshot for one mint (score, holders, bundles, KOLs, cohorts, signals, ratings); token_trades lists recent trades with each trader's history; list_new_tokens, list_pumping_tokens, list_graduated_tokens and list_agent_buys surface launches and activity; profile_wallet and deployer_history cover one wallet's lifetime profile and every token a deployer launched. Results include green, yellow, red or neutral ratings per metric.
- When to use it
- Use it when an assistant needs to check who is behind a Solana or Pump.fun token before entering, while holding, or after exiting, or to look up wallet reputation and deployer track records. It is aimed at token research rather than trading execution.
- Requirements
- Runs locally as an npm package (@cookinfun/mcp) over stdio, so Node.js and npx are needed. Payment is required: either a COOKIN_API_KEY for Cookin Pro, or a SOLANA_KEY base58 Solana keypair holding USDC for per-call x402 payment. COOKIN_MAX_PAYMENT and COOKIN_BASE_URL are optional. Network access to the Cookin API is required. Desktop only.
Installation
In SourceWeft
- Open Cookin Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@cookinfun/mcp
MCP server for the Cookin API: Solana and Pump.fun token intelligence for agents. Ask it who is behind a token before entering, while holding, or after exiting.
Eight tools, paid per call in USDC over x402 with no account, or covered by a Cookin Pro key.
What it answers
- Coordinated wallets. Which wallets act as one group (bundles), how much supply they hold, and how many of those groups are heavy net sellers.
- Holder quality. Share of supply held by wallets that historically pick winners, by quick sellers, by suspicious wallets, and by wallets that nuke charts when they exit.
- KOL positions. Which tracked KOL wallets hold, and how much.
- Wallet reputation. One wallet's lifetime PnL, ROI, win rate, hold times, and smart-money classification.
- Deployer history. Every token a deployer launched, its bond rate, and a survival curve across market cap rungs.
- Ratings. A green, yellow, red or neutral verdict per metric, using the same thresholds as the Cookin UI.
Install
Claude Desktop
Add this to claude_desktop_config.json:
Cursor
In .cursor/mcp.json:
Anything else that speaks MCP
Paying
Pick one. The server prints which mode it started in, on stderr.
SOLANA_KEY is a base58-encoded 64-byte Solana keypair. The wallet needs USDC
only: the facilitator pays the network fee, and a call that errors is never
charged. Mint a Pro key at
cookin.fun/account/api-keys.
Optional:
COOKIN_MAX_PAYMENTcaps what one call may pay. Default$0.05.COOKIN_BASE_URLpoints at another host. Defaulthttps://api.cookin.fun.
Tools
Spend less: start with one scan_token, and stop if its ratings already answer
the question. fields trims a snapshot at the same price. Deployer history
changes slowly, so cache it.
Remote endpoint
The same tools are served remotely at https://api.cookin.fun/mcp, with
nothing to install. Point an MCP host at that URL. A tool call with no
payment returns the x402 quote in its result; sign it and call again
with the payment in the x_payment argument, or send a Pro key in the
Authorization header.
Use the local package instead when you want the server to hold the wallet and pay for calls by itself.
Reference
- Field-by-field reference: api.cookin.fun/skill.md
- OpenAPI spec: api.cookin.fun/openapi.json
- Docs: cookin.fun/api
Development
Releasing
package.json and server.json both carry the version, and the MCP
Registry rejects a mismatch. Bump both, publish to npm first (the
registry reads mcpName from the published package), then publish the
metadata:
MIT
Source: README.md at commit b79b7cb
Tools
0Version history
1- v0.1.1LatestOct 4, 2026


