swiss-energy-mcp@0.5.2
CAUTION· not startedPublisher claims: "MCP Server für Schweizer Energiedaten – BFE Elektrizitätsproduktionsanlagen, Windkraft, Wasserkraft, Photovoltaik, Solareignung, Energiestädte via GeoAdmin REST API und opendata.swiss" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso admin.ch, opendata.swiss, shields.io, claude.ai — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 79/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
assert_url_allowed("https://169.254.169.254/latest/meta-data")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.kill -KILL "$pid" 2>/dev/nullFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.while kill -0 "$pid" 2>/dev/null; doFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.vorlage = Path(__file__).resolve().parent.parent / ".env.example"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Genau der Wert, den README und .env.example nennen.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.modul = importlib.util.module_from_spec(spec)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""Build a MCPServer lifespan that owns the shared HTTP client."""Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.fertig = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.modul = importlib.util.module_from_spec(spec)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""`MCPServer` lehnt einen unbekannten Schluessel schon im Konstruktor ab;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.``.env.example`` document — died there as a ``SettingsError``. TheFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.spec.loader.exec_module(modul)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.``SWISS_ENERGY_``) or an optional ``.env`` file. This keeps configuration outFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.ziel = tmp_path / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.fertig = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.spec.loader.exec_module(modul)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.done = subprocess.run(call, capture_output=True, text=True, check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.env_file=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.ergebnis = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.kill -TERM "$pid" 2>/dev/nullFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.pytest tests/ -m live -v --tb=short --junitxml=live-report.xml 2>&1 | tee live-output.txtFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."""`.env.example` woertlich als `.env` — die Datei sagt selbst, manFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for swiss-energy-mcp@0.5.2 as of 18 h ago. This is the package itself, not its dependencies.
What would make this Verified
1 point to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim hayal-oezkan-hayal.oezkan: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- URL to the cloud instance metadata address≈ +2 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Access to sensitive file paths≈ +2 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.