Remote MCP · Endpoint

SignalLayer MCP server

No. SignalLayer answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://signallayer.floot.app/_api/mcp

The last check completed an MCP handshake.

Registry name
io.github.xavierleterrible-hub/signallayer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
4.93 s
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Machine-native tools for autonomous agents with free routing and x402 USDC pay-per-call.
Listing
From the official MCP registry (active).
Recent checks of SignalLayer
CheckedResultHandshake
56 minutes agoHandshake completed4.93 s
1 day agoHandshake completed87 ms
2 days agoHandshake completed111 ms
5 days agoHandshake completed93 ms
8 days agoHandshake completed88 ms
10 days agoHandshake completed1.55 s
12 days agoHandshake completed214 ms
14 days agoHandshake completed5.56 s
16 days agoHandshake completed66 ms
18 days agoHandshake completed79 ms
20 days agoHandshake completed58 ms
22 days agoHandshake completed283 ms
23 days agoHandshake completed5.53 s

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

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