_ registry / mcp streamable-http · checked 14h ago

sunwise-solar

https://www.sunwise.cl

Registry code: 8289827c5c20f2e9

api record

Datos de precios de sistemas solares residenciales en Chile (Sunwise). Usa `precio_por_region` para el precio de referencia por kWp y por región. Usa `simular_casa` para cotizar un caso concreto: necesita al menos el monto de la boleta mensual o el consumo en kWh, y la comuna o la región. Usa `consultar_faq` para Net Billing, trámite SEC TE4, garantías y orientación de techo. IMPORTANTE: `precio_por_region` devuelve el precio de referencia (camino 'referencia'); `simular_casa` devuelve la cotización final de esa casa (camino 'cotizacion'). Cita siempre la cifra con su camino y menciona la…

endpoint
https://www.sunwise.cl/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is sunwise-solar live?
Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
Is sunwise-solar free to use?
Not measured yet.
What tools does sunwise-solar have?
3 tools: simular_casa, precio_por_region, consultar_faq.
Is sunwise-solar safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
392ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • simular_casa unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "kwp": {
          "type": "number",
          "maximum": 320,
          "description": "Tamaño del sistema en kWp, si ya se conoce.",
          "exclusiveMinimum": 0
        },
        "comuna": {
          "type": "string",
          "maxLength": 120,
          "minLength": 1,
          "description": "Comuna del domicilio, por ejemplo 'Talca'."
        },
        "region": {
          "type": "string",
          "maxLength": 120,
          "minLength": 1,
          "description": "Región, por ejemplo 'maule' o 'Región Metropolitana'."
        },
        "latitud": {
          "type": "number",
          "maximum": -17,
          "minimum": -56,
          "description": "Latitud de la cubierta. Si viene, la simulación usa la irradiación real de ese punto."
        },
        "consulta": {
          "type": "string",
          "maxLength": 600,
          "minLength": 1,
          "description": "Texto libre en español con los datos del caso. Se parsea para extraer monto, comuna y región."
        },
        "longitud": {
          "type": "number",
          "maximum": -66,
          "minimum": -76,
          "description": "Longitud de la cubierta."
        },
        "bateria_kwh": {
          "type": "number",
          "maximum": 500,
          "minimum": 0,
          "description": "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)."
        },
        "monto_boleta": {
          "type": "number",
          "maximum": 10000000,
          "description": "Monto de la boleta mensual en CLP.",
          "exclusiveMinimum": 0
        },
        "tipo_sistema": {
          "enum": [
            "on-grid",
            "off-grid",
            "hibrido"
          ],
          "type": "string",
          "description": "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 manda, se cotiza on-grid sin batería."
        },
        "consumo_kwh_mes": {
          "type": "number",
          "maximum": 20000,
          "description": "Consumo mensual en kWh. Alternativa a monto_boleta.",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 70 lines
  • precio_por_region unknown never probed

    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`).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "kwp": {
          "type": "number",
          "maximum": 320,
          "description": "Tamaño del sistema en kWp. Default 4.",
          "exclusiveMinimum": 0
        },
        "region": {
          "type": "string",
          "maxLength": 120,
          "minLength": 1,
          "description": "Slug o nombre de la región. Default 'rm'."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • consultar_faq unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "pregunta"
      ],
      "properties": {
        "pregunta": {
          "type": "string",
          "maxLength": 400,
          "minLength": 3,
          "description": "La pregunta en español."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8289827c5c20f2e9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8289827c5c20f2e9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8289827c5c20f2e9/badge.svg)](https://brick.blue/agent/8289827c5c20f2e9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.