de.cernion/cernion-energy-tools

MCPcommunitylive
v0.99.4de.cernionUnknownUpdated 1mo agoGitHub

Energy-domain MCP tools for Cernion context, evidence and guarded process preparation

Endpoint healthlive
checked 1 day ago · 426ms · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorde.cernion
LicenseUnknown
Version0.99.4
Sourcemcp-registry
GitHubenergychain/cernion-energy-tools
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface11 tools · none privileged
Security scan✓ CleanvHEAD · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

11 tools · none privileged
Statically extracted from the published packagevHEAD · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

stromdao-validierung-q1-2026No description published

This tool published no description. Forge does not invent one.

get_weatherNo description published

This tool published no description. Forge does not invent one.

cernion.askNo description published

This tool published no description. Forge does not invent one.

cernion.answer_dossierNo description published

This tool published no description. Forge does not invent one.

cernion.recommend_capabilityNo description published

This tool published no description. Forge does not invent one.

cernion.list_readonly_capabilitiesNo description published

This tool published no description. Forge does not invent one.

cernion.get_evidence_statusNo description published

This tool published no description. Forge does not invent one.

qualityScoreNo description published

This tool published no description. Forge does not invent one.

findingsCountNo description published

This tool published no description. Forge does not invent one.

timestampNo description published

This tool published no description. Forge does not invent one.

gridOperatorIdNo description published

This tool published no description. Forge does not invent one.

0 of 11 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Energy-domain MCP tools for Cernion context, evidence and guarded process preparation

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

11 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.