Remote MCP · Endpoint

FET112 MCP server

No. FET112 answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://www.fet112.com/mcp

The last check completed an MCP handshake.

Registry name
com.fet112/fet112
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
310 ms
Tools exposed
14 tools
Uptime, last 30 days
33.3% from 12 checks
Described by its publisher as
Security intelligence for AI agents monitoring Ethereum before actions.
Listing
From the official MCP registry (active).
Recent checks of FET112
CheckedResultHandshake
20 minutes agoHandshake completed310 ms
3 days agoHandshake completed292 ms
14 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
22 days agoHandshake completed373 ms
25 days agoHandshake completed315 ms

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

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 FET112 and makes no claim about it beyond what these checks measured.