Remote MCP · Endpoint

2ds · Visibilidad en IA MCP server

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

UpLast checked 2 hours 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
661 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 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
2 hours agoHandshake completed661 ms
2 days agoHandshake completed98 ms
4 days agoHandshake completed819 ms
6 days agoHandshake completed131 ms
8 days agoHandshake completed576 ms
9 days agoHandshake completed97 ms
11 days agoHandshake completed117 ms
12 days agoHandshake completed725 ms
13 days agoHandshake completed746 ms
16 days agoHandshake completed732 ms
17 days agoHandshake completed97 ms
19 days agoHandshake completed131 ms
20 days agoHandshake completed760 ms
21 days agoHandshake completed147 ms
23 days agoHandshake completed185 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 2ds · Visibilidad en IA and makes no claim about it beyond what these checks measured.