Remote MCP · Endpoint

Femtos MCP server

No. Femtos answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://api.femtos.xyz/mcp

The last check completed an MCP handshake.

Registry name
xyz.femtos/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
582 ms
Tools exposed
130 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Hyperliquid data on HyperCore, HyperEVM, Elysium: balances, prices, trades, token security, bridges
Website
https://femtos.xyz/mcp
Listing
From the official MCP registry (active).
Recent checks of Femtos
CheckedResultHandshake
43 minutes agoHandshake completed582 ms
8 days agoHandshake completed287 ms
9 days agoHandshake completed651 ms
11 days agoHandshake completed748 ms
12 days agoHandshake completed240 ms
13 days agoHandshake completed282 ms
14 days agoHandshake completed244 ms
14 days agoHandshake completed301 ms
16 days agoHandshake completed218 ms
19 days agoHandshake completed265 ms
21 days agoHandshake completed610 ms
24 days agoHandshake completed1.37 s

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 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.

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