Remote MCP · Endpoint

APEX EVM Reads & Security MCP server

No. APEX EVM Reads & Security answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://apexfaucet.xyz/api/mcp/evm

The last check completed an MCP handshake.

Registry name
xyz.apexfaucet/apex-evm
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
357 ms
Tools exposed
33 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
7-chain EVM audits, log simulator, wallet due diligence, calldata decoder, Chainlink & ENS.
Listing
From the official MCP registry (active).
Recent checks of APEX EVM Reads & Security
CheckedResultHandshake
1 hour agoHandshake completed357 ms
9 days agoHandshake completed168 ms
9 days agoHandshake completed342 ms
11 days agoHandshake completed374 ms
12 days agoHandshake completed334 ms
13 days agoHandshake completed810 ms
14 days agoHandshake completed138 ms
14 days agoHandshake completed153 ms
16 days agoHandshake completed358 ms
19 days agoHandshake completed610 ms
21 days agoHandshake completed312 ms
24 days agoHandshake completed409 ms
26 days agoFailed - the request timed out—
28 days agoHandshake completed392 ms

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

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 APEX EVM Reads & Security and makes no claim about it beyond what these checks measured.