Remote MCP · Endpoint

Base DEX Liquidity, Honeypot & Token Safety Scanner MCP server

No. Base DEX Liquidity, Honeypot & Token Safety Scanner answered an MCP handshake 51 minutes ago.

UpLast checked 51 minutes ago

Server URL

https://ceadigital.io/mcp/token-intel

The last check completed an MCP handshake.

Registry name
io.ceadigital/base-token-intel-honeypot
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
117 ms
Tools exposed
28 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Real-time DEX liquidity, 24h buy/sell symmetry, Base bytecode check & 0-100 honeypot score.
Listing
From the official MCP registry (active).
Recent checks of Base DEX Liquidity, Honeypot & Token Safety Scanner
CheckedResultHandshake
51 minutes agoHandshake completed117 ms
3 days agoHandshake completed57 ms
12 days agoHandshake completed58 ms

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with Base DEX Liquidity, Honeypot & Token Safety Scanner and makes no claim about it beyond what these checks measured.