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

soljo-mcp

https://cwghnqlpeeocjsjfhgyk.supabase.co

Registry code: 26a5fa32c7731d07

api record

Soljo is an independent solar calculator for Switzerland; first estimates also work for German addresses (it sells no systems and earns no installer commissions). Use `building_energy_profile` for a specific Swiss address when the user wants real numbers for their building (roof, shading, cost, subsidy, savings, payback). Use `solar_first_estimate` for German addresses or when someone asks whether solar is worth it at an address, how much a system yields or costs, or which subsidy applies. Always cite the returned sources. The first estimate has no savings, self-consumption, payback or…

endpoint
https://cwghnqlpeeocjsjfhgyk.supabase.co/functions/v1/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 soljo-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
Is soljo-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does soljo-mcp have?
4 tools: solar_first_estimate, geocode_address, building_energy_profile, list_cities.
Is soljo-mcp 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
98.1%

90 days 99.1%· all time 99.1%

latency
1,435ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 530 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • estimate rooftop solar yield at an address
  • geocode a swiss or german address
  • list swiss cities with electricity prices
takes → gives
text → data
tools
3 reads
_ 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 4 tools
1 open 3 never probed 1 of 4 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.

  • list_cities reads open 25h ago

    List Swiss cities and municipalities (about 200, German-speaking) with a Soljo page showing local electricity price (ElCom), solar yield (PVGIS), feed-in tariff, subsidy programmes and an example calculation, each with sources. Filter by canton or name.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 60,
          "minLength": 2,
          "description": "Part of the municipality name, e.g. 'Uster'."
        },
        "canton": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Canton abbreviation, e.g. 'ZH', 'BE', 'AG'."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • solar_first_estimate reads unknown 25h ago

    First estimate for a rooftop solar system at a Swiss or German address: annual yield (PVGIS), and for Switzerland the median turnkey cost (federal price study 2025, incl. VAT), the Pronovo one-time subsidy (EIV 2026) and the statutory minimum feed-in tariff. Does NOT include measured roof shading, self-consumption, savings or payback; for those, point the user to fullReport.url (the Soljo report). Always cite the returned sources and say it is a rough estimate.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "kwp": {
          "type": "number",
          "default": 10,
          "maximum": 100,
          "minimum": 1,
          "description": "System size in kWp. A typical single-family home has 8 to 15 kWp."
        },
        "lat": {
          "type": "number",
          "maximum": 56,
          "minimum": 45,
          "description": "Latitude, only if no address is given."
        },
        "lon": {
          "type": "number",
          "maximum": 16,
          "minimum": 5,
          "description": "Longitude, only if no address is given."
        },
        "tilt": {
          "type": "number",
          "default": 30,
          "maximum": 90,
          "minimum": 0,
          "description": "Roof/panel tilt in degrees. Flat roofs: use 15."
        },
        "address": {
          "type": "string",
          "maxLength": 200,
          "minLength": 3,
          "description": "Street address in Switzerland or Germany, e.g. 'Bahnhofstrasse 1, 8001 Zürich'. Preferred over coordinates."
        },
        "azimuth": {
          "type": "number",
          "default": 0,
          "maximum": 180,
          "minimum": -180,
          "description": "Orientation: 0 = south, -90 = east, 90 = west, 180 = north."
        },
        "country": {
          "enum": [
            "CH",
            "DE"
          ],
          "type": "string",
          "description": "Country when only coordinates are given."
        }
      },
      "additionalProperties": false
    }
    arguments 54 lines
  • geocode_address reads unknown never probed

    Resolve a Swiss or German street address to latitude, longitude, postcode and country (swisstopo address register, OpenStreetMap fallback).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "address"
      ],
      "properties": {
        "address": {
          "type": "string",
          "maxLength": 200,
          "minLength": 3,
          "description": "Full postal address, e.g. 'Bahnhofstrasse 1, 8001 Zürich'."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • building_energy_profile unknown 25h ago

    Soljo Data: full solar profile for one Swiss building from official data. Returns the roof faces (Sonnendach, BFE), building facts from the federal register (construction period, floors, heating energy source), measured shading from the swisstopo LiDAR surface model, system size and annual yield, and the economics: turnkey cost, subsidies, local electricity price (ElCom), feed-in tariff, self-consumption, savings, payback and 25-year net result. Same calculation as the Soljo report. Every value block lists sourceIds that resolve to `sources`; cite them. Without api_key a small shared free allowance applies; a free key with 100 profiles per month: https://soljo.ch/developers. Takes about 2 to 5 seconds.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "address"
      ],
      "properties": {
        "ev": {
          "type": "boolean",
          "description": "Household has or plans an electric car."
        },
        "address": {
          "type": "string",
          "maxLength": 200,
          "minLength": 5,
          "description": "Swiss street address with house number and postcode, e.g. 'Bundesplatz 3, 3011 Bern'."
        },
        "api_key": {
          "type": "string",
          "pattern": "^sjd_[A-Za-z0-9]{20,64}$",
          "description": "Soljo Data API key (sjd_…). Optional."
        },
        "battery": {
          "type": "boolean",
          "description": "Include a battery recommendation and its payback."
        },
        "heat_pump": {
          "type": "boolean",
          "description": "Household has or plans a heat pump."
        },
        "household_size": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "People in the household (default 3); drives consumption and self-consumption."
        },
        "annual_consumption_kwh": {
          "type": "number",
          "maximum": 100000,
          "minimum": 500,
          "description": "Known annual electricity consumption in kWh; overrides household_size."
        }
      },
      "additionalProperties": false
    }
    arguments 45 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 26a5fa32c7731d07.

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

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.

_ also on supabase.co 131 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

123 more sit on this domain. All of them.