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/flintt-dev/boardrepo-pluginWrote 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/flintt-dev/boardrepo-plugin/boardrepo)<a href="https://agentmods.dev/mcp/flintt-dev/boardrepo-plugin/boardrepo"><img src="https://agentmods.dev/badge/mcp/flintt-dev/boardrepo-plugin/boardrepo/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/flintt-dev/boardrepo-plugin/boardrepo"><img src="https://agentmods.dev/badge/mcp/flintt-dev/boardrepo-plugin/boardrepo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
boardrepo 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
{ "boardrepo": { "url": "https://boardrepo.com/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 5684e936ed55
boardrepo is an MCP server published in the GitHub repository flintt-dev/boardrepo-plugin (0 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
kicad-schematic-manipulation
MCP server "kicad-schematic-manipulation" as configured in richard-luc/KiCAD-Schematic-Manipulation. Runs locally from the KiCAD-Schematic-Manipulation Python package.
immybot-mcp
MCP server "immybot-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/immybot-v0.1.9/immybot. Needs 9 environment variables to run.
cisco-meraki-mcp
MCP server "cisco-meraki-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/cisco-meraki-v0.1.3/ci. Needs 6 environment variables to run.
unifi-network-mcp
MCP server "unifi-network-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/unifi-network-v0.1.9/u. Needs 5 environment variables to run.
kicad-mcp
KiCad MCP Server. Runs locally from the kicad-mcp Python package. Needs 3 environment variables to run.
kicad-sch-api
MCP server "kicad-sch-api" as configured in circuit-synth/kicad-sch-api. Runs locally from the kicad-sch-mcp Python package.