Remote MCP · Endpoint

GW8 Signal API MCP server

No. GW8 Signal API answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://micro-saas-agent.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.GrayWolf8-creator/gw8-signal-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
121 ms
Tools exposed
35 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Daily crypto brief, payment rails, and token safety (rug/honeypot). x402 USDC on Base. Signal only.
Listing
From the official MCP registry (active).
Recent checks of GW8 Signal API
CheckedResultHandshake
7 hours agoHandshake completed121 ms
4 days agoHandshake completed55 ms
14 days agoHandshake completed90 ms
15 days agoHandshake completed81 ms
15 days agoHandshake completed97 ms
17 days agoHandshake completed61 ms
18 days agoHandshake completed70 ms
19 days agoHandshake completed64 ms
20 days agoHandshake completed67 ms
21 days agoHandshake completed148 ms
23 days agoHandshake completed116 ms
26 days agoHandshake completed60 ms
28 days agoHandshake completed56 ms

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

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