Remote MCP · Endpoint

ai.greyridgesignals/tech-risk MCP server

No. ai.greyridgesignals/tech-risk answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://x402-data-api.sigrunner.workers.dev/sse

The last check completed an MCP handshake.

Registry name
ai.greyridgesignals/tech-risk
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
410 ms
Tools exposed
34 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
MCP security scanner: tool-poisoning & prompt-injection audit (OWASP LLM01/08) + Base data
Listing
From the official MCP registry (active).
Recent checks of ai.greyridgesignals/tech-risk
CheckedResultHandshake
56 minutes agoHandshake completed410 ms
3 days agoHandshake completed532 ms
12 days agoHandshake completed1.02 s
13 days agoHandshake completed238 ms
15 days agoHandshake completed494 ms
15 days agoHandshake completed391 ms
17 days agoHandshake completed91 ms
18 days agoHandshake completed94 ms
18 days agoHandshake completed68 ms
20 days agoHandshake completed775 ms
22 days agoHandshake completed74 ms
25 days agoHandshake completed55 ms
27 days agoHandshake completed136 ms

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 ai.greyridgesignals/tech-risk and makes no claim about it beyond what these checks measured.