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/Craftiee/circuitarium-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/craftiee/circuitarium-mcp/circuitarium)<a href="https://agentmods.dev/mcp/craftiee/circuitarium-mcp/circuitarium"><img src="https://agentmods.dev/badge/mcp/craftiee/circuitarium-mcp/circuitarium/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/craftiee/circuitarium-mcp/circuitarium"><img src="https://agentmods.dev/badge/mcp/craftiee/circuitarium-mcp/circuitarium.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
circuitarium 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 10d 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
{
"circuitarium": {
"command": "npx",
"args": [
"-y",
"circuitarium-mcp"
],
"env": {}
}
}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.
- 10d ago First seen · 10 lines scan A 12dce8be86e1
circuitarium is an MCP server published in the GitHub repository Craftiee/circuitarium-mcp (1 stars, last pushed 5d ago), licensed Apache-2.0. 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
rftools
241 RF & electronics calculators + 13 simulation tools for AI agents. Runs locally from the rftools-mcp npm package.
mikrotik-mcp
MCP server for MikroTik integration with Claude and other AI assistants. Runs locally from the mcp-server-mikrotik Python package. Needs 5 environment variables to run.
easyeda-mcp-pro
MCP server for EasyEDA Pro: PCB inspection, BOM, exports, and hardware review. Runs locally from the easyeda-mcp-pro npm package. Needs 4 environment variables to run.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.0). Needs 6 environment variables to run.
cad-mcp-server
STEP file inspection for AI. Measure walls, draft angles, clearances. Returns facts, not guesses. Runs locally from the cad-mcp-server npm package.
partuno
Provider-neutral DigiKey and Mouser MCP server for electronic component research, BOM analysis, and sourcing comparison. Runs locally from the partuno Python package. Needs 5 environment variables to run.