Remote MCP · Endpoint

HexScan Token Security MCP server

No. HexScan Token Security answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://hexscan.xyz/mcp

The last check completed an MCP handshake.

Registry name
xyz.hexscan/token-security
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
136 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Honeypot detection & token risk scan for ERC-20s. Risk score 0-100, tax, source verification.
Listing
From the official MCP registry (active).
Recent checks of HexScan Token Security
CheckedResultHandshake
1 hour agoHandshake completed136 ms
1 day agoHandshake completed52 ms
2 days agoHandshake completed247 ms
3 days agoHandshake completed156 ms
4 days agoHandshake completed127 ms
5 days agoHandshake completed200 ms
6 days agoHandshake completed242 ms
8 days agoHandshake completed193 ms
11 days agoHandshake completed141 ms
13 days agoHandshake completed74 ms
15 days agoHandshake completed291 ms
18 days agoHandshake completed160 ms
20 days agoHandshake completed155 ms
22 days agoHandshake completed155 ms
24 days agoHandshake completed283 ms
26 days agoHandshake completed137 ms
27 days agoHandshake completed152 ms
28 days agoHandshake completed165 ms
29 days agoHandshake completed270 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with HexScan Token Security and makes no claim about it beyond what these checks measured.

HexScan Token Security MCP server - status, uptime and latency - Glide