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/shredEngineer/Archive-AgentWrote 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/shredengineer/archive-agent/my-remote-server)<a href="https://agentmods.dev/mcp/shredengineer/archive-agent/my-remote-server"><img src="https://agentmods.dev/badge/mcp/shredengineer/archive-agent/my-remote-server/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/shredengineer/archive-agent/my-remote-server"><img src="https://agentmods.dev/badge/mcp/shredengineer/archive-agent/my-remote-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
my-remote-server 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 today.
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
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- today First seen · 10 lines scan A 55be97a29e99
my-remote-server is an MCP server published in the GitHub repository shredEngineer/Archive-Agent (64 stars, last pushed yesterday), licensed GPL-3.0. 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-09-25.
Other mcp servers, from other repositories
mcp-local-vision
MCP server "mcp-local-vision" as configured in jshsakura/mcp-local-vision. Runs locally from the mcp-local-vision npm package.
pdf-dashboard-with-mcp
MCP server "pdf-dashboard-with-mcp" as configured in dakshp26/PDFDashboardWithMCP. Runs locally from the pdf-dashboard-with-mcp Python package.
codex-octopus
Spawn multiple specialized Codex agents as MCP servers, each independently configured. Runs locally from the codex-octopus npm package. Needs 7 environment variables to run.
transcreveai
MCP server "transcreveai" as configured in DeHor-Labs/transcreve-ai. Launched with bash ./scripts/transcreveai-mcp --transport stdio.
yahboom-mcp
MCP server "yahboom-mcp" as configured in sandraschi/yahboom-mcp. Launched with https://github.com/sandraschi/yahboom-mcp/releases/download/v2.5.0b1/yahboom-mcp.
openai-responses-mcp
Lightweight MCP server (Responses API core). OpenAI integration + websearch. Runs locally from the openai-responses-mcp npm package.