_ registry / mcp http-sse · checked 1h ago

csolar-energia

https://csolar.com.br

Registry code: 2fb6c53f28bc12cc

api record

Ferramentas da CSolar Energia, empresa de energia solar de Sorocaba/SP que atende o estado de São Paulo. Use estimate_solar_system para estimar um sistema pela conta de luz ou pelo consumo, e check_service_area para saber se um município está na área atendida. Os resultados são estimativas, não orçamento. Nenhuma ferramenta pede dados pessoais.

endpoint
https://csolar.com.br/mcp
protocol
http-sse ·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 csolar-energia live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is csolar-energia free to use?
Yes — the hub reached it with no key and no payment.
What tools does csolar-energia have?
2 tools: estimate_solar_system, check_service_area.
Is csolar-energia 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
684ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • estimate_solar_system unknown 1h ago

    Estima um sistema de energia solar com microinversores a partir do consumo mensal em kWh ou do valor mensal da conta de luz em reais. Devolve potência em kWp, número de módulos, geração mensal, economia mensal, preço instalado e tempo de retorno, pela tabela de preços da CSolar Energia (setembro/2026). O cálculo usa a irradiação da região de Sorocaba/SP; fora da área atendida (estado de São Paulo), os números são só referência. É estimativa, não orçamento. Não pede nem guarda dados pessoais.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "uf": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "UF do município, opcional (ex.: SP)."
        },
        "cidade": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "Município da instalação, opcional. Não muda o cálculo; serve para dizer se fica na área atendida."
        },
        "consumo_kwh_mes": {
          "type": "number",
          "maximum": 1000000,
          "description": "Consumo mensal de energia em kWh, como aparece na conta de luz. Aceito de 50 a 20.000 kWh.",
          "exclusiveMinimum": 0
        },
        "valor_conta_mes": {
          "type": "number",
          "maximum": 1000000,
          "description": "Valor mensal da conta de luz em reais. Use quando não souber o consumo em kWh.",
          "exclusiveMinimum": 0
        }
      }
    }
    arguments 30 lines
  • check_service_area unknown 1h ago

    Diz se um município está na área atendida pela CSolar Energia para instalação de energia solar. A área atendida é o estado de São Paulo (645 municípios). Informe o município e, se souber, a UF. Não pede nem guarda dados pessoais.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "cidade"
      ],
      "properties": {
        "uf": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "UF do município, opcional (ex.: SP). Ajuda quando há municípios com o mesmo nome em outros estados."
        },
        "cidade": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "Nome do município, por exemplo Sorocaba."
        }
      }
    }
    arguments 21 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 2fb6c53f28bc12cc.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2fb6c53f28bc12cc/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/2fb6c53f28bc12cc/badge.svg)](https://brick.blue/agent/2fb6c53f28bc12cc?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
60%

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.