Skip to content
HexScan logo

HexScan MCP server

Which MCP servers are HexScan's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to HexScan

Whose server it is
  • Registry namexyz.hexscan/token-securityverified in the MCP registry

The registry name sits under hexscan.xyz. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools3
  • Server calls itselfhexscan
  • Server version1.0.0
  • Protocol version2025-03-26

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 48 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer224 ms
  • Space in an agent's context≈ 298 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 3 of 3

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-26
  • scan_token

    Full token security scan. Args: address (0x...), chain (ethereum|base|arbitrum|optimism|polygon|bsc|avalanche). Risk score 0-100 from our on-chain checks plus GoPlus. Not an audit.

  • honeypot_check

    Fast honeypot check. Args: address (0x...), chain. Returns: honeypot boolean, canBuy, canSell, buyTax, sellTax, riskScore.

  • simulate_transfer

    Simulate buy-then-sell on-chain. Args: address (0x...), chain. Returns: canBuy, canSell, revertReason, verdict (ALLOW/REVIEW/BLOCK). Uses real eth_call simulation.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "token-security": {
      "type": "http",
      "url": "https://hexscan.xyz/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http hexscan https://hexscan.xyz/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://hexscan.xyz/mcp as a custom connector in the settings.

OpenAPI spec

5 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.