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/mdlockyer/fusion-electronicsWrote 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/mdlockyer/fusion-electronics/fusion-electronics-fusion_el)<a href="https://agentmods.dev/mcp/mdlockyer/fusion-electronics/fusion-electronics-fusion_el"><img src="https://agentmods.dev/badge/mcp/mdlockyer/fusion-electronics/fusion-electronics-fusion_el.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
fusion_el 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 8d 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
{
"fusion_el": {
"command": "node",
"args": [
"./mcp/fusion-electronics-server.mjs"
],
"cwd": ".",
"tool_timeout_sec": 120,
"env": {
"PORT": "27182"
}
}
}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.
- 8d ago First seen · 13 lines scan A d6968eb82068
fusion_el is an MCP server published in the GitHub repository mdlockyer/fusion-electronics (2 stars, last pushed 2mo 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
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.
cad-service
MCP server "cad-service" as configured in halsyourpal422/Battenmark. Runs locally from the cad-service npm package.
cadloop-openscad
Parametric CAD and slicing behind MCP, with every plate proven on the bed. Runs locally from the cadloop Python package. Needs 3 environment variables to run.
cadloop-slicer
Parametric CAD and slicing behind MCP, with every plate proven on the bed. Runs locally from the cadloop Python package. Needs 4 environment variables to run.
boardrepo
Search and review real KiCad and Altium PCB designs: schematics, BOMs, netlists, DRC/ERC. Remote server at boardrepo.com.
mcp_cad
MCP server "mcpcad" as configured in danielproxd2/solidworks-mcp. Runs locally from the mcp_cad Python package.