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.

Sunwise Solar

REMOTE · WWW.SUNWISE.CL

Precios de paneles solares en Chile: precio por kWp por región y cotización de una casa.

Available components

+3 this week 69 Trust /100

Last scanned (20 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category IoT and Hardware

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 Security63
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 850 tokens (~283/item across 3 items; 3 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 Management30
  • Stability observed for 9 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

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.

  • 20 Nov 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.

  • 18 Nov 26 0
    • Tool “simular_casa” rewrote its description, which is the text the model reads security
    • Schema quality: 224 → 283 ▼ functional
    • “simular_casa” added an optional parameter “bateria_kwh” cosmetic
    • “simular_casa” added an optional parameter “tipo_sistema” cosmetic
  • 17 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.

  • 15 Nov 26 +1

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

  • 14 Nov 26 0
    • “simular_casa” added an optional parameter “latitud” cosmetic
    • “simular_casa” added an optional parameter “longitud” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 66

    First indexed and scored.

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 21 Nov 2026 · Probed https://www.sunwise.cl/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.sunwise.cl CN=YR2,O=Let's Encrypt,C=US 8 Nov 2026 6 Feb 2027 RSA 2048 SHA256-RSA 514931d4d339e6d27b37262e234092006c9
SANs: *.sunwise.cl, sunwise.cl
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.sunwise.cl. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cl. DS published 21199 8 Verified
sunwise.cl. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' https://*.googletagmanager.com https://www.googletagmanager.com https://*.google-analytics.com https://www.google-analytics.com https://*.googleadservices.com https://www.googleadservices.com https://*.doubleclick.net https://*.supabase.co https://va.vercel-scripts.com https://maps.googleapis.com https://connect.facebook.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: https: blob: https://www.facebook.com https://connect.facebook.net; connect-src 'self' https://*.supabase.co https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://analytics.google.com https://stats.g.doubleclick.net https://*.doubleclick.net https://*.google.cl https://www.google.com https://maps.googleapis.com wss://*.supabase.co https://connect.facebook.net https://*.facebook.com https://*.googleadservices.com; frame-src 'self' blob: https://www.googletagmanager.com htt
x-content-type-options nosniff
x-frame-options SAMEORIGIN
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://www.sunwise.cl/api/mcp Verified 200
http (plaintext) http://www.sunwise.cl/api/mcp HTTPS enforced 308 https://www.sunwise.cl/api/mcp
MCP tools · 3 exposed · ~674 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
consultar_faq ~77

Responde preguntas regulatorias y conceptuales sobre energía solar residencial en Chile: Ley Net Billing 21.118, trámite SEC TE4, garantías de paneles e inversores, orientación del techo y dimensionamiento. Devuelve la respuesta con la URL de la fuente para citarla.

NameTypeReqDescription
preguntastringyesLa pregunta en español.

No output schema declared.

No examples provided.

precio_por_region ~145

Precio de referencia de instalación solar en Chile por kWp y región, sin IVA y con instalación incluida. Usa esta herramienta para preguntas como '¿cuánto cuesta el kWp en Maule?'. Devuelve el precio por kWp, el total del sistema y la tabla comparativa de las 8 regiones. El campo `camino` es 'referencia': es el promedio de mercado, no la cotización de una casa concreta (esa la da `simular_casa`).

NameTypeReqDescription
kwpnumber–Tamaño del sistema en kWp. Default 4.
regionstring–Slug o nombre de la región. Default 'rm'.

No output schema declared.

No examples provided.

simular_casa ~452

Calcula la cotización de un sistema solar residencial en Chile a partir de muy pocos datos: el monto de la boleta mensual (o el consumo en kWh) y la comuna o la región. Opcionalmente acepta texto libre en `consulta` con esos datos redactados ("pago 80 lucas en Talca"). Devuelve la cotización real: kWp, costo total, ahorro anual y payback. El campo `camino` es 'cotizacion'. Si no se indica `tipo_sistema`, el default es on-grid CONECTADO A LA RED Y SIN BATERÍA: no lo infieras. Usa `tipo_sistema` sólo cuando el caso es realmente off-grid, híbrido o cuando el cliente pidió una batería.

NameTypeReqDescription
bateria_kwhnumber–Capacidad de la batería en kWh, si el cliente la pidió con cifras. Si no se manda, el motor la dimensiona. Un 0 significa 'sin batería' (off-grid de consumo directo).
comunastring–Comuna del domicilio, por ejemplo 'Talca'.
consultastring–Texto libre en español con los datos del caso. Se parsea para extraer monto, comuna y región.
consumo_kwh_mesnumber–Consumo mensual en kWh. Alternativa a monto_boleta.
kwpnumber–Tamaño del sistema en kWp, si ya se conoce.
latitudnumber–Latitud de la cubierta. Si viene, la simulación usa la irradiación real de ese punto.
longitudnumber–Longitud de la cubierta.
monto_boletanumber–Monto de la boleta mensual en CLP.
regionstring–Región, por ejemplo 'maule' o 'Región Metropolitana'.
tipo_sistemastring–Tipo de sistema a cotizar. 'on-grid': conectado a la red, sin batería (es el default). 'hibrido': on-grid con batería, la red sigue siendo el respaldo. 'off-grid': sin red, con batería. Si no se mand…

No output schema declared.

No examples provided.

Install

How do I install the Sunwise Solar MCP server?

Sunwise Solar is a hosted endpoint at https://www.sunwise.cl/api/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 · www.sunwise.cl

# add to Claude Code
claude mcp add --transport http customxx-solar-mcp 'https://www.sunwise.cl/api/mcp'
Common questions

What is the Sunwise Solar MCP server?

Sunwise Solar is an MCP server listed in the public MCP registry as io.github.customxx/solar-mcp. Precios de paneles solares en Chile: precio por kWp por región y cotización de una casa. This page covers its hosted endpoint (https://www.sunwise.cl/api/mcp).

Is the Sunwise Solar MCP server safe to use?

Sunwise Solar scores 69 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 Sunwise Solar MCP server expose?

Sunwise Solar exposes 3 tools: simular_casa, precio_por_region, consultar_faq. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.

Does the Sunwise Solar MCP server require authentication?

No. We connected to Sunwise Solar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Sunwise Solar MCP server still maintained?

Sunwise Solar 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 Sunwise Solar MCP server?

VerifyMCP ran 12 checks on Sunwise Solar, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Sunwise Solar: Authorization. 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.