Remote MCP · Endpoint
unflagdomain: website blacklist removal MCP server
No. unflagdomain: website blacklist removal answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://unflagdomain.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.unflagdomain/website-blacklist-removal
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 655 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Website flagged by security vendors? Free scan, then we send the removal requests for you (paid).
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 655 ms |
| 2 days ago | Handshake completed | 544 ms |
| 4 days ago | Handshake completed | 577 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 unflagdomain: website blacklist removal and makes no claim about it beyond what these checks measured.