Remote MCP · Endpoint

io.github.rezearcher/tech-risk MCP server

No. io.github.rezearcher/tech-risk answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.rezearcher/tech-risk
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
399 ms
Tools exposed
34 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
MCP security scanner: tool-poisoning & prompt-injection audit (OWASP LLM01/LLM08), x402-payable
Listing
From the official MCP registry (active).
Recent checks of io.github.rezearcher/tech-risk
CheckedResultHandshake
2 hours agoHandshake completed399 ms
1 day agoHandshake completed413 ms
2 days agoHandshake completed97 ms
3 days agoHandshake completed70 ms
4 days agoHandshake completed293 ms
5 days agoHandshake completed57 ms
6 days agoHandshake completed367 ms
9 days agoHandshake completed193 ms
11 days agoHandshake completed419 ms
14 days agoHandshake completed266 ms
16 days agoHandshake completed95 ms
18 days agoHandshake completed334 ms
20 days agoHandshake completed332 ms
22 days agoHandshake completed300 ms
24 days agoHandshake completed292 ms
26 days agoHandshake completed243 ms
27 days agoHandshake completed379 ms
29 days agoHandshake completed431 ms

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

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