HexScan Token Security
REMOTE · HEXSCAN.XYZ
Honeypot detection & token risk scan for ERC-20s. Risk score 0-100, tax, source verification.
Available components
Last scanned (23 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 218 tokens (~72/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "simulate_transfer" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 0
- Tool “scan_token” rewrote its description, which is the text the model reads security
- 10 Oct 26 +1
- Stability: 0.93 → pass security
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 90. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 0
- Schema quality: 144 → 216 ▼ functional
- Destructive annotations: pass → 0 functional
- New tool “simulate_transfer” functional
- 10 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://hexscan.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hexscan.xyz | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | de125377fc60ea5c0eade2ae983aa885 |
| SANs: hexscan.xyz, *.hexscan.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hexscan.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| hexscan.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hexscan.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://hexscan.xyz/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
honeypot_check ~66
Fast honeypot check. Args: address (0x...), chain. Returns: honeypot boolean, canBuy, canSell, buyTax, sellTax, riskScore.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract address |
| chain | string | yes | Chain name |
No output schema declared.
No examples provided.
scan_token ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract address |
| chain | string | yes | Chain name |
No output schema declared.
No examples provided.
simulate_transfer ~72
Simulate buy-then-sell on-chain. Args: address (0x...), chain. Returns: canBuy, canSell, revertReason, verdict (ALLOW/REVIEW/BLOCK). Uses real eth_call simulation.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract address |
| chain | string | yes | Chain name |
No output schema declared.
No examples provided.
How do I install the HexScan Token Security MCP server?
HexScan Token Security is a hosted endpoint at https://hexscan.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hexscan.xyz
claude mcp add --transport http xyz-hexscan-token-security 'https://hexscan.xyz/mcp'
What is the HexScan Token Security MCP server?
HexScan Token Security is an MCP server listed in the public MCP registry as xyz.hexscan/token-security. Honeypot detection & token risk scan for ERC-20s. Risk score 0-100, tax, source verification. This page covers its hosted endpoint (https://hexscan.xyz/mcp).
Is the HexScan Token Security MCP server safe to use?
HexScan Token Security scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HexScan Token Security MCP server expose?
HexScan Token Security exposes 3 tools: scan_token, honeypot_check, simulate_transfer. Their descriptions and schemas cost roughly 218 tokens of context every time the server is loaded.
Does the HexScan Token Security MCP server require authentication?
No. We connected to HexScan Token Security without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HexScan Token Security MCP server still maintained?
HexScan Token Security is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.