mcpField
C
cookin-mcp

cookin-mcp

Local
github.com/cookinfunFinance0Updated 4w ago

About cookin-mcp

cookin-mcp exposes Cookin API intelligence on Solana and Pump.fun tokens to agents, covering holders, coordinated wallets, KOLs, and deployer histories. Calls can be paid individually through x402 or covered by a Cookin Pro key.

Key features

  1. 01Retrieve token snapshots and ratings
  2. 02Analyze coordinated wallets and selling
  3. 03Check KOL holdings and wallet trading records
  4. 04Look up deployer launch histories
  5. 05List new, pumping, and graduated tokens

Use cases

  1. 01Check holders and wallet groups before entering a token
  2. 02Track KOL and wallet activity while holding
  3. 03Assess a deployer's past token launches

MCP support

The MCP server exposes Cookin API intelligence for Solana and Pump.fun through eight tools. Calls support per-request x402 payments or a Cookin Pro key; a remote endpoint is available at https://api.cookin.fun/mcp.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"cookinfun-cookin": {
"command": "npx",
"args": [
"-y",
"@cookinfun/mcp"
],
"env": {
"SOLANA_KEY": "<SOLANA_KEY>",
"COOKIN_API_KEY": "<COOKIN_API_KEY>",
"COOKIN_MAX_PAYMENT": "<COOKIN_MAX_PAYMENT>"
}
}
}
}
Run commandnpx -y @cookinfun/mcp
Environment variables to set
SOLANA_KEYSecretBase58 Solana keypair holding USDC, to pay per call with x402. The key stays on this machine; only a signed transaction leaves it.
COOKIN_API_KEYSecretCookin Pro API key, as an alternative to paying per call. Mint one at https://cookin.fun/account/api-keys
COOKIN_MAX_PAYMENTMost one call may pay, for example $0.05. Default $0.05.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@cookinfun/mcp0.1.1

Tools

8

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
mintstringYesSolana token mint address, base58.
fieldsstringNoComma-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.

Details

From the project 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:

{
  "mcpServers": {
    "cookin": {
      "command": "npx",
      "args": ["-y", "@cookinfun/mcp"],
      "env": { "SOLANA_KEY": "<base58 Solana keypair holding USDC>" }
    }
  }
}
Cursor

In .cursor/mcp.json:

{
  "mcpServers": {
    "cookin": {
      "command": "npx",
      "args": ["-y", "@cookinfun/mcp"],
      "env": { "COOKIN_API_KEY": "<Cookin Pro key>" }
    }
  }
}
Anything else that speaks MCP
SOLANA_KEY=<base58 keypair> npx -y @cookinfun/mcp

Paying

Pick one. The server prints which mode it started in, on stderr.

EnvironmentModeCost
SOLANA_KEYPay per call with x402$0.01 per call, $0.02 for a full token snapshot
COOKIN_API_KEYCookin Pro1 SOL per 30 days, 600 requests per minute
neitherUnpaidEvery call returns 402 and says how to pay

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_PAYMENT caps what one call may pay. Default $0.05.
  • COOKIN_BASE_URL points at another host. Default https://api.cookin.fun.

Tools

ToolPriceReturns
scan_token$0.02Full snapshot for one mint: score, holders, bundles, KOLs, cohorts, signals, ratings
token_trades$0.01Recent trades, each with the trader's history at that moment
list_new_tokens$0.01New launches that passed the rug filters
list_pumping_tokens$0.01Tokens currently pumping
list_graduated_tokens$0.01Recent graduates
list_agent_buys$0.01What the top Cookin agents bought most recently
profile_wallet$0.01One wallet's lifetime trading profile
deployer_history$0.01Every token one deployer launched

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

Development

npm install
npm test          # unit tests, no network
npm run build     # tsc to dist/
npm start         # run the server over stdio
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:

npm publish --access public
mcp-publisher login github
mcp-publisher publish

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.