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/thesigma1receptor/fm8MCPWrote 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/thesigma1receptor/fm8mcp/fm8)<a href="https://agentmods.dev/mcp/thesigma1receptor/fm8mcp/fm8"><img src="https://agentmods.dev/badge/mcp/thesigma1receptor/fm8mcp/fm8/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/thesigma1receptor/fm8mcp/fm8"><img src="https://agentmods.dev/badge/mcp/thesigma1receptor/fm8mcp/fm8.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fm8 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
{
"fm8": {
"command": "node",
"args": [
"C:/fm8MCP/dist/server.js",
"--transport=stdio",
"--midi-port-name=fm8",
"--channel=1"
]
}
}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 · 11 lines scan A e357e79f715a
fm8 is an MCP server published in the GitHub repository thesigma1receptor/fm8MCP (0 stars, last pushed 10mo 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
pixoo-mcp-server
Render and push styled pixel art, text, dashboards, and animations to Divoom Pixoo LED displays. Runs locally from the @cyanheads/pixoo-mcp-server npm package. Needs 5 environment variables to run.
vcv-rack-mcp
MCP server "vcv-rack-mcp" as configured in sandraschi/vcv-rack-mcp. Runs locally from the vcv-rack-mcp Python package.
obsbot-mcp
Control an OBSBOT Tiny 2 camera: pan/tilt/zoom, AI tracking, focus, exposure, snapshots, recording. Runs locally from the obsbot-mcp npm package. Needs 1 environment variable to run.
samsung-spotify-tv
MCP server "samsung-spotify-tv", hosted remotely at 127.0.0.1, as configured in dudibuilds/samsung-stremio-spotify-mcp.
ledfx-mcp
MCP server "ledfx-mcp" as configured in abossard/ledfx-mcp. Runs locally from the @abossard/ledfx-mcp npm package.
rc505mk2-mcp
MCP server "rc505mk2-mcp" as configured in hysteve/rc505mk2-mcp. Runs locally from the rc505mk2-mcp npm package.