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.
npx agentmods add mcp/nschneir/project64/c64-toolsgit clone --depth 1 https://github.com/nschneir/Project64Wrote 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/nschneir/project64/c64-tools)<a href="https://agentmods.dev/mcp/nschneir/project64/c64-tools"><img src="https://agentmods.dev/badge/mcp/nschneir/project64/c64-tools.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
c64-tools 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 5 lines scan A bbac280c1846
c64-tools is an MCP server published in the GitHub repository nschneir/Project64 (2 stars, last pushed 11d ago), with no licence file. 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
pet-tools
MCP server "pet-tools" as configured in nschneir/PET-Project. Runs locally from the pet-tools Python package.
c64bridge
MCP server "c64bridge" as configured in chrisgleissner/c64bridge. Runs scripts/start.mjs with node. Needs 3 environment variables to run.
regenerator2000
MCP server "regenerator2000", hosted remotely at 127.0.0.1, as configured in ricardoquesada/regenerator2000.
strata
MCP server for progressive tool usage at any scale (see https://klavis.ai). Remote server at strata.klavis.ai.
pare-test
Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON. Runs locally from the @paretools/test npm package.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.