Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/jdhart81/energyai-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/jdhart81/energyai-mcp/energyai)<a href="https://agentmods.dev/mcp/jdhart81/energyai-mcp/energyai"><img src="https://agentmods.dev/badge/mcp/jdhart81/energyai-mcp/energyai/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/jdhart81/energyai-mcp/energyai"><img src="https://agentmods.dev/badge/mcp/jdhart81/energyai-mcp/energyai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
energyai scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "energyai": { "url": "https://api.energyaisolution.com/mcp", "type": "streamable-http" } }
What else
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 6 lines scan A dd2c2c598baa
energyai is an MCP server published in the GitHub repository jdhart81/energyai-mcp (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp
Spanish e-invoicing with VeriFactu (AEAT): issue invoices, manage customers, validate NIFs. Runs locally from the @beel_es/mcp npm package. Needs 2 environment variables to run.
ynab
An AI-first MCP server for YNAB. Read-only by default, with reversible writes. Runs locally from the mcp-server-for-ynab Python package. Needs 2 environment variables to run.
mcp-server-for-ynab
An AI-first MCP server for YNAB. Read-only by default, with reversible writes. Runs locally from the mcp-server-for-ynab Python package. Needs 3 environment variables to run.
polymarket-news-mcp
MCP server that matches news headlines to the Polymarket prediction markets they could move — live odds, deep links, explainable matching. Runs locally from the polymarket-news-mcp Python package.
edgar-mcp
MCP server for SEC EDGAR financial data with a manifest-backed 31-tool surface. Runs locally from the edgar-mcp Python package.
quant
Quant tools + an NFL fantasy draft assistant for AI agents — Kalshi & Polymarket EV, edge, ADP. Remote server at predictionmarketspicks.com.