Can the Hogar Montevideo · Agenda de service técnico MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

Does the Hogar Montevideo · Agenda de service técnico MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Hogar Montevideo · Agenda de service técnico MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Hogar Montevideo · Agenda de service técnico MCP server

uy.hogarmontevideo/agendahogarmontevideo.uystreamable-httpv1.0.0Scanned 9 days ago

Agendá un técnico de electrodomésticos a domicilio en Montevideo y Ciudad de la Costa (Uruguay).

7 tools: 7 change things.

Reads private data · 0
Reads text others write · 3
Can send data out · 0
No findings

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

Anlyon lists the tools and adopts none.
Each tool you adopt gets approvals and receipts.
Your agent never holds the key.

Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. anlyon.dev only lists and labels, and these labels are the same either way.

What the Hogar Montevideo · Agenda de service técnico MCP server can do

The Hogar Montevideo · Agenda de service técnico MCP server is published by hogarmontevideo.uy, a domain the MCP Registry verified. It has 7 tools. It can create or change data (7 tools: obtener_catalogo, consultar_disponibilidad, agendar_servicio, solicitar_codigo_garantia and 3 more), but cannot delete data. None of its tools only reads.

3 tools bring in text other people can write (agendar_servicio, solicitar_codigo_garantia and agendar_reclamo).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 5, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 7Creates or changes something that can be changed back.Claude Code: ask

agendar_reclamoAgenda la visita de reclamo en garantía con el mismo técnico del servicio original, en una franja devuelta por consultar_disponibilidad_reclamo.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it
Agenda la visita de reclamo en garantía con el mismo técnico del servicio original, en una franja devuelta por consultar_disponibilidad_reclamo. Confirmá antes con el cliente el día, la franja y el problema. Devuelve el número de la nueva orden.
Annotations the server declares
- title: Reclamo en garantía · agendar
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
agendar_servicioReserva la visita de un técnico de Hogar Montevideo al domicilio y devuelve el número de orden.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it
Reserva la visita de un técnico de Hogar Montevideo al domicilio y devuelve el número de orden. Antes de llamarla: (1) elegí una franja libre con consultar_disponibilidad; (2) pedí nombre, celular, dirección y, en reparaciones, la descripción del problema; (3) mostrale al cliente un resumen con las condiciones (si el cliente no acepta el presupuesto abona $ 700 de visita técnica) y esperá su confirmación explícita. Si el celular tiene servicios recientes en garantía, la herramienta pide aclarar si es un reclamo (ver ignorar_garantia).
Annotations the server declares
- title: Agendar visita de un técnico
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
consultar_disponibilidadConsulta en tiempo real los días y franjas horarias en que un técnico de Hogar Montevideo puede ir al domicilio, según el tipo de servicio, el equipo y el barrio.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
Consulta en tiempo real los días y franjas horarias en que un técnico de Hogar Montevideo puede ir al domicilio, según el tipo de servicio, el equipo y el barrio. Devuelve hasta 5 días hábiles a partir de 'desde' (por defecto, desde ahora). Mostrale al cliente sólo estas opciones y usá la elegida en agendar_servicio. No reserva nada.
Annotations the server declares
- title: Ver días y horarios disponibles
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
consultar_disponibilidad_reclamoDías y franjas libres del técnico que hizo el servicio original, para atender el reclamo en garantía.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
Días y franjas libres del técnico que hizo el servicio original, para atender el reclamo en garantía. Requiere el token_garantia y el orden_id que devolvió verificar_codigo_garantia. No reserva nada.
Annotations the server declares
- title: Reclamo en garantía · ver horarios
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
obtener_catalogoInformación de Hogar Montevideo (service de electrodomésticos a domicilio en Montevideo y Ciudad de la Costa, Uruguay): tipos de servicio, equipos que atiende, barrios con cobertur…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
Información de Hogar Montevideo (service de electrodomésticos a domicilio en Montevideo y Ciudad de la Costa, Uruguay): tipos de servicio, equipos que atiende, barrios con cobertura, franjas horarias de visita, condiciones (costo de la visita si no se repara), garantía y contacto. Usala para responder dudas o comprobar cobertura antes de agendar.
Annotations the server declares
- title: Qué ofrece Hogar Montevideo
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
solicitar_codigo_garantiaPrimer paso para reclamar por un servicio de Hogar Montevideo de los últimos 6 meses: comprueba que el celular tenga servicios en garantía y le envía un código por SMS.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it
Primer paso para reclamar por un servicio de Hogar Montevideo de los últimos 6 meses: comprueba que el celular tenga servicios en garantía y le envía un código por SMS. Usala sólo si el cliente quiere reclamar por un trabajo anterior; después pedile el código y llamá a verificar_codigo_garantia.
Annotations the server declares
- title: Reclamo en garantía · enviar código por SMS
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
verificar_codigo_garantiaVerifica el código recibido por SMS y devuelve los servicios en garantía de ese celular (con su orden_id) y un token_garantia válido por 60 minutos, necesario para consultar_dispon…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
Verifica el código recibido por SMS y devuelve los servicios en garantía de ese celular (con su orden_id) y un token_garantia válido por 60 minutos, necesario para consultar_disponibilidad_reclamo y agendar_reclamo. Cada código sirve una sola vez.
Annotations the server declares
- title: Reclamo en garantía · verificar código
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0: Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.; agendar_reclamo
agendar_servicio
solicitar_codigo_garantia
Can send data out0: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 13, 2026, 11:21 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable: yes
HTTP status of an anonymous initialize: 200
tools/list served without credentials: yes
Tools that change things, listed without credentials: 7
Protocol version: 2025-06-18
WWW-Authenticate on 401: not observed
resource_metadata in WWW-Authenticate: not observed
RFC 9728 protected resource metadata: not observed
Authorization servers: not observed
Legacy HTTP+SSE transport: no
Dynamic client registration: not observed
Client ID metadata documents: not observed

WarnThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.
Matched text
https://hogarmontevideo.uy/mcp: tools/list returned 7 tools to an anonymous client, including obtener_catalogo (write), consultar_disponibilidad (write), agendar_servicio (write), solicitar_codigo_garantia (write), verificar_codigo_garantia (write) and 2 more
What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agenda https://hogarmontevideo.uy/mcp

claude mcp add --transport http agenda https://hogarmontevideo.uy/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__agenda__obtener_catalogo",
      "mcp__agenda__consultar_disponibilidad",
      "mcp__agenda__agendar_servicio",
      "mcp__agenda__solicitar_codigo_garantia",
      "mcp__agenda__verificar_codigo_garantia",
      "mcp__agenda__consultar_disponibilidad_reclamo",
      "mcp__agenda__agendar_reclamo"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agenda. Review it before you use it.

Capability tags behind 3 rules

mcp__agenda__agendar_servicio untrusted-input
mcp__agenda__solicitar_codigo_garantia untrusted-input
mcp__agenda__agendar_reclamo untrusted-input

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/uy.hogarmontevideo/agenda/verify?hash=305e5b3666a14f9f9379ba341856eb438274e13a03ab71249d18980d72bb3270" | jq -e '.changed == false'

Pinned hash 305e5b3666a1, from Nov 5, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/uy.hogarmontevideo/agenda/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/uy.hogarmontevideo/agenda.svg)](https://anlyon.dev/servers/uy.hogarmontevideo/agenda)

Source: MCP Registry. Synced Nov 6, 2026, 00:18 UTC.