Cernion Energy Tools MCP is answering right now. Last checked 5 min ago. Last commit 10 Nov 2026.
Energy-domain MCP tools for Cernion context, evidence and guarded process preparation
We read the source, 14 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
/\b([A-ZÄÖÜ][A-Za-zÄÖÜäöüß-]+(?:\s+[A-ZÄÖÜ][A-Za-zÄÖÜäöüß-]+)?)\s+(?:in|im)\s+(?:Baden-Württemberg|Bayern|Nordrhein-Westfalen|Hessen|Thüringen|Sachsen-Anhalt|Sachsen|Brandenburg|Mecklenburg-Vorpommern|Schleswig-Holstein|Niedersachsen|Rheinland-Pfalz|Saarla…
const result = spawnSync(jestBin, args, {
${updateRequest ? `Update Request:\n${updateRequest}` : ''}
return await page.$$eval(`${tableSelector} tr`, (trs) =>
path.join(output, name),
formGrid.innerHTML = requiredInputs
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.
claude mcp add cernion-energy-tools --transport http https://api.cernion.de/api/mcp
https://api.cernion.de/api/mcp
[mcp_servers.cernion-energy-tools]
url = "https://api.cernion.de/api/mcp"
{
"mcpServers": {
"cernion-energy-tools": {
"url": "https://api.cernion.de/api/mcp"
}
}
}
{
"servers": {
"cernion-energy-tools": {
"type": "http",
"url": "https://api.cernion.de/api/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.cernion.de/api/mcp | streamable-http | needs auth | 136 ms | 5 min ago |
Guarded local Charles Proxy automation and bounded XML session evidence
Context and control for any AI. Agent identity, scoped access, and proof across tools.
MCP server for the SCF Controls Platform — 187 tools for controls, evidence, risk, and TPRM.
Complete Holded Invoice API integration with 72 MCP tools for invoices, contacts, products, and more
Domain attribution and correlation for AI agents, with confidence and per-signal evidence.
Read-only verifier for 25 ProofRelay MCP tools and non-confidential evidence bundles.
Governed AI-agent memory, Evidence Ledger traces, evals, and portable context tools.
Model Context Protocol server for Studex tools, notifications, and profile integrations
Answers built from our own checks of this server.