Remote MCP · Endpoint

Manta Signal Gate MCP server

Yes, as of 8 hours ago: the server returned an HTTP error.

DownLast checked 8 hours ago

Server URL

https://signals.easyrider.one/mcp

The last check failed: the server returned an HTTP error.

Registry name
one.easyrider/signal-gate
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
7 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Live trading journal of one bot for AI agents: free stats and sample, x402-paid signals and follow
Listing
From the official MCP registry (active).
Recent checks of Manta Signal Gate
CheckedResultHandshake
8 hours agoFailed - the server returned an HTTP error—
3 days agoHandshake completed382 ms
12 days agoHandshake completed431 ms
13 days agoHandshake completed404 ms
14 days agoHandshake completed389 ms
15 days agoHandshake completed2.89 s
16 days agoHandshake completed448 ms
17 days agoHandshake completed631 ms
18 days agoHandshake completed393 ms
20 days agoHandshake completed382 ms
22 days agoHandshake completed3.98 s
25 days agoHandshake completed416 ms
27 days agoHandshake completed395 ms
30 days agoHandshake completed1.68 s

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

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