Hogar Montevideo · Agenda de service técnico
REMOTE · HOGARMONTEVIDEO.UY
Agendá un técnico de electrodomésticos a domicilio en Montevideo y Ciudad de la Costa (Uruguay).
Available components
Last scanned (16 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Workflow Automation
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1985 tokens (~283/item across 7 items; 7 tools + 0 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 Management50
- Stability observed for 15 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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://hogarmontevideo.uy/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hogarmontevideo.uy | CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB | 12 Nov 2026 | 29 May 2027 | RSA 2048 | SHA256-RSA | 8a91d2e3fa35b4ce84d941e859cd5431 |
| SANs: hogarmontevideo.uy, www.hogarmontevideo.uy | ||||||
| CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 397a66cc2756362e0daa87ca6eabe3b1 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hogarmontevideo.uy. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| uy. | DS published | 19730, 35285 | 8, 8 | Verified |
| hogarmontevideo.uy. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hogarmontevideo.uy/mcp | Verified | 200 | |
| http (plaintext) | http://hogarmontevideo.uy/mcp | HTTPS enforced | 301 | https://hogarmontevideo.uy/mcp |
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 →
agendar_reclamo Reclamo en garantía · agendar ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmado_por_cliente | boolean | yes | true sólo después de mostrarle al cliente el resumen (día, franja, dirección, datos y condiciones) y que lo haya confirmado explícitamente. |
| fecha | string | yes | Día elegido (AAAA-MM-DD). |
| hora_desde | string | yes | Inicio de la franja elegida (HH:mm). |
| hora_hasta | string | yes | Fin de la franja elegida (HH:mm). |
| orden_id | integer | yes | orden_id del servicio en garantía (de verificar_codigo_garantia). |
| problema | string | yes | Qué sigue fallando o qué pasó después del servicio. |
| token_garantia | string | yes | token_garantia devuelto por verificar_codigo_garantia. |
No output schema declared.
No examples provided.
agendar_servicio Agendar visita de un técnico ~543
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).
| Name | Type | Req | Description |
|---|---|---|---|
| apartamento | string | – | Opcional. Número de apartamento u oficina. |
| barrio | string | yes | Barrio del domicilio, por ejemplo Pocitos, Cordón, Malvín, Carrasco, Prado o Solymar (lista completa en obtener_catalogo). |
| celular | string | yes | Celular uruguayo de contacto: 9 dígitos que empiezan con 09 (por ejemplo 099123456). |
| confirmado_por_cliente | boolean | yes | true sólo después de mostrarle al cliente el resumen (día, franja, dirección, datos y condiciones) y que lo haya confirmado explícitamente. |
| direccion | string | yes | Calle y número de puerta, por ejemplo 'Av. Brasil 2520'. |
| fecha | string | yes | Día elegido (AAAA-MM-DD), tal como lo devolvió consultar_disponibilidad. |
| hora_desde | string | yes | Inicio de la franja elegida (HH:mm), por ejemplo 09:00. |
| hora_hasta | string | yes | Fin de la franja elegida (HH:mm), por ejemplo 12:00. |
| ignorar_garantia | boolean | – | Poné true sólo si el cliente ya aclaró que NO es un reclamo por un servicio anterior (la herramienta lo pregunta cuando corresponde). |
| marca | string | – | Opcional. Marca del equipo. |
| modelo | string | – | Opcional. Modelo del equipo. |
| nombre | string | yes | Nombre de la persona de contacto. |
| nombre_empresa | string | – | Opcional. Sólo si el servicio es para una empresa. |
| problema | string | – | Qué le pasa al equipo (obligatorio en reparaciones). Cuanto más detalle, mejor preparado va el técnico. |
| tipo_equipo | string | yes | Equipo a atender. 'Electricista' es para trabajos de electricidad en el hogar. |
| tipo_servicio | string | yes | Reparación (falla o rotura), Mantenimiento (limpieza o service preventivo) o Instalación (equipo nuevo). |
No output schema declared.
No examples provided.
consultar_disponibilidad Ver días y horarios disponibles ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| barrio | string | yes | Barrio del domicilio, por ejemplo Pocitos, Cordón, Malvín, Carrasco, Prado o Solymar (lista completa en obtener_catalogo). |
| desde | string | – | Opcional. Fecha (AAAA-MM-DD) a partir de la cual buscar; por ejemplo, el valor 'siguiente_desde' de una consulta anterior. |
| tipo_equipo | string | yes | Equipo a atender. 'Electricista' es para trabajos de electricidad en el hogar. |
| tipo_servicio | string | yes | Reparación (falla o rotura), Mantenimiento (limpieza o service preventivo) o Instalación (equipo nuevo). |
No output schema declared.
No examples provided.
consultar_disponibilidad_reclamo Reclamo en garantía · ver horarios ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| desde | string | – | Opcional. Fecha (AAAA-MM-DD) a partir de la cual buscar. |
| orden_id | integer | yes | orden_id del servicio en garantía (de verificar_codigo_garantia). |
| token_garantia | string | yes | token_garantia devuelto por verificar_codigo_garantia. |
No output schema declared.
No examples provided.
obtener_catalogo Qué ofrece Hogar Montevideo ~84
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
solicitar_codigo_garantia Reclamo en garantía · enviar código por SMS ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| celular | string | yes | Celular uruguayo de contacto: 9 dígitos que empiezan con 09 (por ejemplo 099123456). |
No output schema declared.
No examples provided.
verificar_codigo_garantia Reclamo en garantía · verificar código ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| celular | string | yes | Celular uruguayo de contacto: 9 dígitos que empiezan con 09 (por ejemplo 099123456). |
| codigo | string | yes | Código numérico recibido por SMS. |
No output schema declared.
No examples provided.
How do I install the Hogar Montevideo · Agenda de service técnico MCP server?
Hogar Montevideo · Agenda de service técnico is a hosted endpoint at https://hogarmontevideo.uy/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 · hogarmontevideo.uy
claude mcp add --transport http uy-hogarmontevideo-agenda 'https://hogarmontevideo.uy/mcp'
What is the Hogar Montevideo · Agenda de service técnico MCP server?
Hogar Montevideo · Agenda de service técnico is an MCP server listed in the public MCP registry as uy.hogarmontevideo/agenda. Agendá un técnico de electrodomésticos a domicilio en Montevideo y Ciudad de la Costa (Uruguay). This page covers its hosted endpoint (https://hogarmontevideo.uy/mcp).
Is the Hogar Montevideo · Agenda de service técnico MCP server safe to use?
Hogar Montevideo · Agenda de service técnico scores 79 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 Hogar Montevideo · Agenda de service técnico MCP server expose?
Hogar Montevideo · Agenda de service técnico exposes 7 tools: obtener_catalogo, consultar_disponibilidad, agendar_servicio, solicitar_codigo_garantia, verificar_codigo_garantia, and 2 more. Their descriptions and schemas cost roughly 1,419 tokens of context every time the server is loaded.
Does the Hogar Montevideo · Agenda de service técnico MCP server require authentication?
No. We connected to Hogar Montevideo · Agenda de service técnico without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Hogar Montevideo · Agenda de service técnico MCP server still maintained?
Hogar Montevideo · Agenda de service técnico is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Hogar Montevideo · Agenda de service técnico MCP server?
VerifyMCP ran 13 checks on Hogar Montevideo · Agenda de service técnico, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.