Remote MCP · Endpoint

2ds · Visibilidad en IA MCP server

No. 2ds · Visibilidad en IA answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://www.2ds.dev/mcp/2ds

The last check completed an MCP handshake.

Registry name
dev.2ds/2ds
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
935 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Comprueba si una web está preparada para asistentes de IA y qué arreglar; servicios de 2ds.
Listing
From the official MCP registry (active).
Recent checks of 2ds · Visibilidad en IA
CheckedResultHandshake
18 minutes agoHandshake completed935 ms
9 days agoHandshake completed1.84 s
9 days agoHandshake completed92 ms
11 days agoHandshake completed751 ms
12 days agoHandshake completed254 ms
13 days agoHandshake completed759 ms
14 days agoHandshake completed794 ms
14 days agoHandshake completed100 ms
16 days agoHandshake completed689 ms
19 days agoHandshake completed136 ms
21 days agoHandshake completed159 ms
24 days agoHandshake completed832 ms
26 days agoHandshake completed661 ms
28 days agoHandshake completed98 ms

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

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 2ds · Visibilidad en IA and makes no claim about it beyond what these checks measured.