Skip to content

Soljo Solar (Switzerland) MCP server

ch.soljo/solarsoljo.chstreamable-httpv0.2.0Scanned

Independent rooftop solar first estimate for Switzerland: yield, median cost, subsidy, with sources

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Soljo Solar (Switzerland) MCP server can do

The Soljo Solar (Switzerland) MCP server is published by soljo.ch, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: building_energy_profile and solar_first_estimate), but cannot delete data. 2 tools only read.

3 tools bring in text other people can write (building_energy_profile, solar_first_estimate and geocode_address).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • building_energy_profileSoljo Data: full solar profile for one Swiss building from official data.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • solar_first_estimateFirst 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • geocode_addressResolve a Swiss or German street address to latitude, longitude, postcode and country (swisstopo address register, OpenStreetMap fallback).Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "resolve": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Resolve a Swiss or German street address to latitude, longitude, postcode and country (swisstopo address register, OpenStreetMap fallback).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • list_citiesList 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…No findings

    Why it is in this group

    • The name "list_cities" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:31 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://cwghnqlpeeocjsjfhgyk.supabase.co/functions/v1/mcp: tools/list returned 4 tools to an anonymous client, including building_energy_profile (write), solar_first_estimate (write)

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 1 to 2

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added.+1 addedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
    • Tools that change things, listed without credentials: 1 to 2

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http solar https://cwghnqlpeeocjsjfhgyk.supabase.co/functions/v1/mcp
claude mcp add --transport http solar https://cwghnqlpeeocjsjfhgyk.supabase.co/functions/v1/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__solar__geocode_address",
      "mcp__solar__list_cities"
    ],
    "ask": [
      "mcp__solar__building_energy_profile",
      "mcp__solar__solar_first_estimate"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as solar. Review it before you use it.

Capability tags behind 3 rules
  • mcp__solar__building_energy_profile untrusted-input
  • mcp__solar__solar_first_estimate untrusted-input
  • mcp__solar__geocode_address untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ch.soljo/solar/verify?hash=b2a5f590bdb13423aa610a8f3a249739ad13dc5eb9aad206796b16a3a020b181" | jq -e '.changed == false'

Pinned hash b2a5f590bdb1, from Nov 12, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ch.soljo/solar/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ch.soljo/solar
[![Anlyon Radar](https://radar.anlyon.com/badge/ch.soljo/solar.svg)](https://radar.anlyon.com/servers/ch.soljo/solar)

Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.

Soljo Solar (Switzerland) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Soljo Solar (Switzerland) MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Soljo Solar (Switzerland) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Soljo Solar (Switzerland) MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Soljo Solar (Switzerland) MCP server have?

4 tools: 2 write, 2 read. building_energy_profile, solar_first_estimate, geocode_address and list_cities.

Does the Soljo Solar (Switzerland) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Soljo Solar (Switzerland) MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Soljo Solar (Switzerland) MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 30, 2026. Every change is on this page and in its Atom feed.