Remote MCP · Endpoint

desenmascara.me MCP server

No. desenmascara.me answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://desenmascara.me/mcp/v1

The last check completed an MCP handshake.

Registry name
me.desenmascara/desenmascara
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
328 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Is this website a scam? Dated, sourced fraud assessments of domains. Free, read-only, no key.
Listing
From the official MCP registry (active).
Recent checks of desenmascara.me
CheckedResultHandshake
1 hour agoHandshake completed328 ms
1 day agoHandshake completed343 ms
4 days agoHandshake completed141 ms
6 days agoHandshake completed411 ms
9 days agoHandshake completed135 ms
11 days agoHandshake completed327 ms
13 days agoHandshake completed600 ms
15 days agoHandshake completed306 ms
17 days agoHandshake completed323 ms
19 days agoHandshake completed148 ms
21 days agoHandshake completed121 ms
22 days agoHandshake completed153 ms
24 days agoHandshake completed402 ms
25 days agoHandshake completed122 ms
27 days agoHandshake completed320 ms

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

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