Remote MCP · Endpoint

RelayShield Scam Checks MCP server

No. RelayShield Scam Checks answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://relayshieldadmin-relayshield-free-mcp.hf.space/mcp

The last check completed an MCP handshake.

Registry name
io.github.nzdsf2-gif/relayshield-free-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
28 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free scam checks for links, wallets, emails, and breach exposure. No signup.
Listing
From the official MCP registry (active).
Recent checks of RelayShield Scam Checks
CheckedResultHandshake
1 hour agoHandshake completed28 ms
2 days agoHandshake completed28 ms
4 days agoHandshake completed83 ms
6 days agoHandshake completed24 ms
8 days agoHandshake completed26 ms
10 days agoHandshake completed20 ms
12 days agoHandshake completed25 ms
14 days agoHandshake completed21 ms
15 days agoHandshake completed48 ms
17 days agoHandshake completed27 ms
18 days agoHandshake completed48 ms
20 days agoHandshake completed31 ms
22 days agoHandshake completed25 ms
24 days agoHandshake completed27 ms

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

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 RelayShield Scam Checks and makes no claim about it beyond what these checks measured.