HexScan Token Security

Honeypot detection & token risk scan for ERC-20s. Risk score 0-100, tax, source verification.

Should I use this

Quality & Safety

A
Description quality
93%
Schema completeness
100%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~297Tokens (tool definitions)
~549 BTypical response size
Minimal attention impact (0.23% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://hexscan.xyz/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪scan_token(address, chain)

Full token security scan. Args: address (0x...), chain (ethereum|base|arbitrum|optimism|polygon|bsc|avalanche). Returns risk score 0-100, honeypot, tax, source verification.

Input Schema

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "Token contract address"
    },
    "chain": {
      "type": "string",
      "description": "Chain name"
    }
  },
  "required": [
    "address",
    "chain"
  ]
}
🟢honeypot_check(address, chain)

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

Input Schema

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "Token contract address"
    },
    "chain": {
      "type": "string",
      "description": "Chain name"
    }
  },
  "required": [
    "address",
    "chain"
  ]
}
⚪simulate_transfer(address, chain)

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

Input Schema

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "Token contract address"
    },
    "chain": {
      "type": "string",
      "description": "Chain name"
    }
  },
  "required": [
    "address",
    "chain"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools
verifiedversion not recorded3 tools
verifiedversion not recorded2 tools