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/boykush/scrapsWrote 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/boykush/scraps/mcp-server-scraps)<a href="https://agentmods.dev/mcp/boykush/scraps/mcp-server-scraps"><img src="https://agentmods.dev/badge/mcp/boykush/scraps/mcp-server-scraps.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
scraps 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 7d 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
{
"scraps": {
"type": "http",
"url": "${SCRAPS_MCP_URL:-http://127.0.0.1:1113/mcp}"
}
}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.
- 7d ago First seen · 6 lines scan A 7c7e51a2f6ec
scraps is an MCP server published in the GitHub repository boykush/scraps (47 stars, last pushed yesterday), 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-30.
Other mcp servers, from other repositories
remem
MCP server "remem" as configured in majiayu000/remem. Runs ${PLUGIN_ROOT}/scripts/remem-mcp.js with node.
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.
vulcanus
A validated Markdown memory vault your coding agent can recall, project by project. Runs locally from the @sunsato/vulcanus npm package.
ai-journal-mcp
Journal engine and MCP server: capture, structure, and ask questions of your work journals. Runs locally from the ai-journal-mcp Python package.
research-hub
AI-operable research workspace for Zotero, Obsidian, and NotebookLM. Use any two, or all three, through CLI, MCP, REST, and dashboard. Runs locally from the research-hub-pipeline Python package.
recollect
MCP server "recollect" as configured in juunzzi/recollect. Launched with recollect mcp.