Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Juntamos: organizar grupos

REMOTE · JUNTAMOS.ES

Crear amigo invisible, votaciones y repartos de gastos para un grupo

Available components

+3 this week 84 Trust /100

Last scanned (8 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2450 tokens (~306/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://juntamos.es/grupos/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=juntamos.es CN=YE1,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 ECDSA 256 ECDSA-SHA384 5945056e7bd340de828d6deca95dce5fcdf
SANs: juntamos.es
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of juntamos.es. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
es. present 4901, 54404 8, 8 Verified
juntamos.es. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://juntamos.es/grupos/mcp Verified 200
http (plaintext) http://juntamos.es/grupos/mcp HTTPS enforced 308 https://juntamos.es/grupos/mcp
MCP tools · 7 exposed · ~2,409 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
anadir_gasto ~361

Añade un gasto a un grupo de gastos compartidos creado con crear_gastos (quién pagó, cuánto y entre quiénes se reparte) y devuelve quién debe a quién. Úsala para: "Ana pagó 60 € de la cena entre todos", "añade que Luis pagó 24,50 de gasolina entre Luis y Marta". Devuelve: los pagos para quedar en paz y el total, con el enlace del grupo. Límites: necesita el enlace o token de administración (id_admin); los nombres deben estar en el grupo; si entre_quienes va vacío, se reparte entre todos. Adds an expense to a shared expenses group created with crear_gastos (who paid, how much and who shares it) and returns who owes whom. Use it for: "Ann paid 60 euros for dinner for everyone", "add that Luke paid 24.50 for fuel shared by Luke and Mary". Returns: the payments to settle up and the total, with the group link. Limits: needs the admin link or token (id_admin); names must be in the group; empty entre_quienes means everyone.

NameTypeReqDescription
conceptostring–Concepto / what for. Ej.: "Cena"
entre_quienesarray–Entre quiénes se reparte; vacío = todos / who shares it; empty = everyone
id_adminstringyesEnlace o token de administración devuelto por crear_gastos / admin link or token returned by crear_gastos
importe–yesImporte en euros / amount in euros. Ej.: 24.5 o "24,50"
quien_pagostringyesQuién pagó / who paid. Ej.: "Ana"

No output schema declared.

No examples provided.

crear_amigo_invisible ~476

Hace el sorteo del amigo invisible en el servidor y crea un enlace privado por participante, donde cada uno ve solo a quién le regala. Respeta exclusiones (parejas que no pueden tocarse). Úsala para: "organiza un amigo invisible con Ana, Luis, Marta y Pablo, presupuesto 20 €", "sorteo de amigo invisible para la oficina sin que Ana y Luis se toquen", "haz el amigo invisible de la familia para el 24 de diciembre". Devuelve: un enlace privado por participante (para repartir a cada uno el suyo), un enlace público para el grupo y el enlace de administración del organizador. El resultado completo no se devuelve nunca. Límites: de 3 a 100 participantes con nombres distintos; sin emails; se borra 90 días después de la fecha. Draws Secret Santa names on the server and creates one private link per participant, where each person only sees who they give to. Supports exclusions (couples who must not draw each other). Use it for: "organise a Secret Santa with Ann, Luke, Mary and Peter, budget 20 euros", "office Secret Santa where Ann and Luke cannot get each other". Returns: one private link per participant (send each person their own), a public page for the group and the organiser admin link. The full result is never returned. Limits: 3 to 100 participants with different names; no emails; deleted 90 days after the date.

NameTypeReqDescription
exclusionesarray–Parejas que no pueden tocarse (en los dos sentidos) / pairs who must not draw each other. Ej.: [["Ana", "Luis"]]
fechastring–Fecha del intercambio AAAA-MM-DD / exchange date YYYY-MM-DD
idiomastring–Idioma de las páginas del evento / language of the event pages: "es" or "en". Default "es".
participantesarrayyesNombres o apodos, distintos entre sí / names or nicknames, all different. Ej.: ["Ana", "Luis", "Marta"]
presupuestostring–Presupuesto orientativo / budget. Ej.: "20 €"
titulostring–Título / title. Ej.: "Amigo invisible de la oficina"

No output schema declared.

No examples provided.

crear_eleccion_fecha ~321

Crea una página para que un grupo elija fecha: cada persona marca en cada día propuesto si puede, si hace falta o no, y se destaca la mejor fecha. Úsala para: "ayúdame a elegir fecha para la cena de Navidad entre el 12, 13, 19 y 20 de diciembre", "qué fin de semana de noviembre podemos quedar todos", "busca fecha para la reunión de antiguos alumnos". Devuelve: el enlace para que cada uno marque su disponibilidad y el enlace de administración. Límites: de 2 a 31 días, en formato AAAA-MM-DD y no pasados; hasta 100 personas. Creates a page for a group to pick a date: everyone marks yes, if needed or no on each suggested day and the best date is highlighted. Use it for: "help me pick a date for the Christmas dinner: Dec 12, 13, 19 or 20", "which November weekend can we all meet". Returns: the link for everyone to mark availability and the admin link. Limits: 2 to 31 days, YYYY-MM-DD, not in the past; up to 100 people.

NameTypeReqDescription
fechasarrayyesDías propuestos AAAA-MM-DD / suggested days YYYY-MM-DD
idiomastring–Idioma de las páginas del evento / language of the event pages: "es" or "en". Default "es".
titulostringyesTítulo / title. Ej.: "Cena de Navidad"

No output schema declared.

No examples provided.

crear_encuesta ~379

Crea una encuesta o votación con opciones de texto para compartir con un grupo; voto único o múltiple, resultados en tiempo real y cierre opcional. Úsala para: "haz una votación para elegir restaurante: italiano, japonés o asador", "crea una encuesta de qué día hacemos la reunión", "votación con varias respuestas para elegir actividades del viaje". Devuelve: el enlace para votar (compartirlo en el grupo) y el enlace de administración (para cerrarla y ver resultados). Límites: de 2 a 30 opciones distintas; hasta 100 votantes; el cierre debe ser futuro. Creates a poll with text options to share with a group; single or multiple choice, live results and optional closing time. Use it for: "make a poll to choose a restaurant: Italian, Japanese or steakhouse", "create a multiple-choice vote for trip activities". Returns: the voting link (share it with the group) and the admin link (to close it and see results). Limits: 2 to 30 different options; up to 100 voters; closing time must be in the future.

NameTypeReqDescription
cierrestring–Cierre automático ISO 8601 con zona / closing time ISO 8601 with offset. Ej.: "2026-11-20T20:00:00+01:00"
idiomastring–Idioma de las páginas del evento / language of the event pages: "es" or "en". Default "es".
multipleboolean–true si se pueden elegir varias / true to allow several choices
opcionesarrayyesOpciones / options. Ej.: ["Italiano", "Japonés"]
preguntastringyesPregunta / question. Ej.: "¿Dónde cenamos?"

No output schema declared.

No examples provided.

crear_gastos ~313

Crea un grupo de gastos compartidos (viaje, piso, cena) donde se apunta quién pagó qué y se calcula quién debe a quién con el mínimo de pagos. Úsala para: "crea un grupo de gastos para el viaje a Asturias con Ana, Luis y Marta", "quiero repartir los gastos de la casa rural entre 6", "apunta gastos compartidos del piso". Devuelve: el enlace del grupo (todos pueden apuntar gastos) y el enlace de administración, que sirve para anadir_gasto y ver_resultados. Límites: de 2 a 100 personas con nombres distintos; importes en euros. Creates a shared expenses group (trip, flat, dinner) to record who paid what and work out who owes whom with the fewest payments. Use it for: "create an expense group for the trip with Ann, Luke and Mary", "split the holiday cottage costs between 6 people". Returns: the group link (everyone can add expenses) and the admin link, used by anadir_gasto and ver_resultados. Limits: 2 to 100 people with different names; amounts in euros.

NameTypeReqDescription
idiomastring–Idioma de las páginas del evento / language of the event pages: "es" or "en". Default "es".
participantesarrayyesNombres, distintos entre sí / names, all different
titulostringyesTítulo / title. Ej.: "Viaje a Asturias"

No output schema declared.

No examples provided.

crear_lista_quien_trae ~324

Crea una lista de cosas que hacen falta (bebidas, postre, carbón…) para que cada persona del grupo se apunte a lo que va a traer, sin repetir. Úsala para: "haz una lista de quién trae qué para la barbacoa del sábado", "organiza qué lleva cada uno a la cena de Nochevieja", "lista para el viaje: tienda, hornillo, nevera". Devuelve: el enlace para que cada uno se apunte y el enlace de administración. Límites: de 1 a 100 cosas; cualquiera del grupo puede añadir más. Creates a list of things needed (drinks, dessert, charcoal…) so everyone in the group signs up for what they will bring, without duplicates. Use it for: "make a who-brings-what list for Saturday's barbecue", "organise what everyone brings to the New Year's dinner". Returns: the sign-up link and the admin link. Limits: 1 to 100 items; anyone in the group can add more.

NameTypeReqDescription
elementosarrayyesLo que hace falta / items needed. Ej.: ["Bebidas", "Postre", "Pan"]
fechastring–Fecha del evento AAAA-MM-DD / event date YYYY-MM-DD
idiomastring–Idioma de las páginas del evento / language of the event pages: "es" or "en". Default "es".
titulostringyesTítulo / title. Ej.: "Barbacoa del sábado"

No output schema declared.

No examples provided.

ver_resultados ~235

Muestra el estado de un evento de Juntamos: votos de la encuesta, mejor fecha, quién trae qué, quién debe a quién o cuántos han abierto su sobre del amigo invisible. Úsala para: "¿cómo va la votación del restaurante?", "¿quién debe a quién en el viaje?", "¿cuántos han abierto ya su amigo invisible?". Devuelve: un resumen de los resultados y el enlace a la página del evento. Límites: necesita el enlace o token de administración (id_admin); nunca revela quién le regala a quién en el amigo invisible. Shows the status of a Juntamos event: poll votes, best date, who brings what, who owes whom or how many opened their Secret Santa envelope. Use it for: "how is the restaurant poll going?", "who owes whom from the trip?". Returns: a summary of the results and the event link. Limits: needs the admin link or token (id_admin); never reveals who got whom in Secret Santa.

NameTypeReqDescription
id_adminstringyesEnlace o token de administración / admin link or token

No output schema declared.

No examples provided.

Install

How do I install the Juntamos: organizar grupos MCP server?

Juntamos: organizar grupos is a hosted endpoint at https://juntamos.es/grupos/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · juntamos.es

# add to Claude Code
claude mcp add --transport http es-juntamos-grupos 'https://juntamos.es/grupos/mcp'
Common questions

What is the Juntamos: organizar grupos MCP server?

Juntamos: organizar grupos is an MCP server listed in the public MCP registry as es.juntamos/grupos. Crear amigo invisible, votaciones y repartos de gastos para un grupo. This page covers its hosted endpoint (https://juntamos.es/grupos/mcp).

Is the Juntamos: organizar grupos MCP server safe to use?

Juntamos: organizar grupos scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Juntamos: organizar grupos MCP server expose?

Juntamos: organizar grupos exposes 7 tools: crear_amigo_invisible, crear_encuesta, crear_eleccion_fecha, crear_lista_quien_trae, crear_gastos, and 2 more. Their descriptions and schemas cost roughly 2,409 tokens of context every time the server is loaded.

Does the Juntamos: organizar grupos MCP server require authentication?

No. We connected to Juntamos: organizar grupos without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Juntamos: organizar grupos MCP server still maintained?

Juntamos: organizar grupos is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.