MCP.Market

Chaink9 MCP server

online · 100% uptime
by chaink9.com·com.chaink9/chaink9·v0.2.1

Token risk checks on BSC, ETH, Base and Arc: trades the token on a fork. Paid in USDC via x402.

A87/100grade A
What users say
No reviews yet
Be the first
Safety scan
A87/100

not scanned yet

Adoption
Growing

0 stars439 downloads/wk

Reviews

Write one

Nobody has reviewed Chaink9 yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Chaink9 tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Chaink9 compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 73% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
617 ms
faster than 23% of 30,031 servers
Downloads a week
439
more than 86% of 12,191 servers with a package

Release history: 2 versions in the registry since 2026-10-22, latest 2026-10-28, typically one every 6 days.

Install Chaink9 in Claude Code, Cursor or VS Code

claude mcp add --transport http chaink9 https://api.chaink9.com/mcp
Add to Cursor

What the publisher says

From the Chaink9 repository's README, as published. We do not edit it. Read it on GitHub

ChainK9 MCP server

Token risk checks for AI agents on BNB Smart Chain, Ethereum and Base.

Most token scanners read flags from someone else's API. ChainK9 does what a buyer would: it forks the chain and really buys and sells the token through its market (PancakeSwap or Uniswap V2, V3 or V4, hooks included), then runs 60+ checks. A honeypot is caught by what it does, not by what its code looks like.

Each successful call is paid automatically in USDC on Base with the x402 protocol, from a wallet you choose. There is no account and no API key, and failed calls (bad input, not a token, no liquidity, engine busy) are free.

Tools

The tool list is read live from api.chaink9.com, so new products appear without updating this package.

Every tool takes chain: bsc (default), eth or base.

Setup

needs no ETH: x402 payments are signatures, and the payment service pays the gas.

  1. Make a new wallet just for this and put a few dollars of USDC on Base in it. It
  1. Add the server to your MCP client with that wallet's private key.

Claude Code:

claude mcp add chaink9 -e CHAINK9_PRIVATE_KEY=0x... -- npx -y chaink9-mcp

Cursor, Claude Desktop or any client with a JSON config:

{
  "mcpServers": {
    "chaink9": {
      "command": "npx",
      "args": ["-y", "chaink9-mcp"],
      "env": { "CHAINK9_PRIVATE_KEY": "0x..." }
    }
  }
}

Claude Desktop can also install the .mcpb bundle from the releases with a click.

Hosted server, no install

https://api.chaink9.com/mcp serves the same tools over streamable HTTP, plus a free verdict tool (the stored verdict and which checks flagged it). Paid tools there take the payment inside the MCP call, x402-style, so they need an x402-aware client such as @x402/mcp's createx402MCPClient. Ordinary MCP clients can connect and use verdict; to pay from those, use the package above.

Limits

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Chaink9: common questions

Is Chaink9 MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Chaink9 safety report
How do I install Chaink9?
It runs remotely at api.chaink9.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Chaink9 need an API key?
Yes. The registry entry asks for CHAINK9_PRIVATE_KEY.
Is Chaink9 maintained?
The last commit was 13 days ago (2026-10-22). The latest release is v0.2.1.
Is Chaink9 up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Chaink9 compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 617 ms (faster than 23% of 30,031 servers). Full comparison.