Remote MCP · Endpoint

com.stevesignals.api/steve-guard MCP server

No. com.stevesignals.api/steve-guard answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.stevesignals.com/mcp

The last check completed an MCP handshake.

Registry name
com.stevesignals.api/steve-guard
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
339 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Solana + Robinhood-Chain token safety & net-USD accumulation intel for trading agents.
Listing
From the official MCP registry (active).
Recent checks of com.stevesignals.api/steve-guard
CheckedResultHandshake
1 hour agoHandshake completed339 ms
2 days agoHandshake completed311 ms
4 days agoHandshake completed313 ms
5 days agoHandshake completed324 ms
7 days agoHandshake completed361 ms
8 days agoHandshake completed308 ms
9 days agoHandshake completed325 ms
12 days agoHandshake completed356 ms
13 days agoHandshake completed356 ms
15 days agoHandshake completed339 ms
16 days agoHandshake completed332 ms
17 days agoHandshake completed350 ms
19 days agoHandshake completed333 ms
20 days agoHandshake completed320 ms
20 days agoHandshake completed321 ms
21 days agoHandshake completed348 ms
22 days agoHandshake completed454 ms

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

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 com.stevesignals.api/steve-guard and makes no claim about it beyond what these checks measured.