Remote MCP · Endpoint

Juntamos: organizar grupos MCP server

No. Juntamos: organizar grupos answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://juntamos.es/grupos/mcp

The last check completed an MCP handshake.

Registry name
es.juntamos/grupos
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
360 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Crear amigo invisible, votaciones y repartos de gastos para un grupo
Listing
From the official MCP registry (active).
Recent checks of Juntamos: organizar grupos
CheckedResultHandshake
1 hour agoHandshake completed360 ms
1 day agoHandshake completed358 ms
2 days agoHandshake completed403 ms
3 days agoHandshake completed364 ms
4 days agoHandshake completed355 ms
5 days agoHandshake completed365 ms
6 days agoHandshake completed368 ms
9 days agoHandshake completed373 ms
11 days agoHandshake completed358 ms
14 days agoHandshake completed340 ms
16 days agoHandshake completed358 ms
18 days agoHandshake completed468 ms
20 days agoHandshake completed446 ms
22 days agoHandshake completed414 ms
24 days agoHandshake completed352 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 Juntamos: organizar grupos and makes no claim about it beyond what these checks measured.