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/jalcodev/gridhub-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/jalcodev/gridhub-mcp/gridhub)<a href="https://agentmods.dev/mcp/jalcodev/gridhub-mcp/gridhub"><img src="https://agentmods.dev/badge/mcp/jalcodev/gridhub-mcp/gridhub/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/jalcodev/gridhub-mcp/gridhub"><img src="https://agentmods.dev/badge/mcp/jalcodev/gridhub-mcp/gridhub.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gridhub 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 1mo 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
{
"gridhub": {
"url": "https://api.grid-hub.app/mcp",
"type": "streamable-http"
}
}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.
- 1mo ago First seen · 6 lines scan A 7d1a5a1a4bf8
gridhub is an MCP server published in the GitHub repository jalcodev/gridhub-mcp (0 stars, last pushed 23d 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
datacenter-power-grid-fiber
Live power, energy, grid, gas, fiber & data-center site-selection infrastructure — query and cite. Remote server at dchub.cloud.
mcp-server
Data-center, grid, fiber & gas infrastructure intelligence for AI agents — query and cite. Remote server at dchub.cloud.
dchub
MCP server "dchub", hosted remotely at dchub.cloud, as configured in azmartone67/dchub-mcp-server.
carbon-intensity
MCP server "carbon-intensity", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-carbon-intensity.
aemo
MCP server for the Australian Energy Market Operator (AEMO) NEM. Plain-English access to 5-min dispatch prices, regional demand, interconnector flows, generation by fuel, and rooftop PV. Runs locally from the aemo-mcp Python package.
aemo-mcp
MCP server for the Australian Energy Market Operator (AEMO) NEM. Plain-English access to 5-min dispatch prices, regional demand, interconnector flows, generation by fuel, and rooftop PV. Runs locally from the aemo-mcp Python package.