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/vnmoorthy/reweaveWrote 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/vnmoorthy/reweave/reweave)<a href="https://agentmods.dev/mcp/vnmoorthy/reweave/reweave"><img src="https://agentmods.dev/badge/mcp/vnmoorthy/reweave/reweave/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/vnmoorthy/reweave/reweave"><img src="https://agentmods.dev/badge/mcp/vnmoorthy/reweave/reweave.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
reweave 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
{ "reweave": { "command": "uvx", "args": [ "reweave" ] } }
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 · 8 lines scan A 1ec0615859e1
reweave is an MCP server published in the GitHub repository vnmoorthy/reweave (1 stars, last pushed 1mo 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
mcp
Authorize consequential AI agent actions before execution. Runs locally from the @decionis/mcp npm package. Needs 3 environment variables to run.
agentgate
Human-in-the-loop approval gateway for AI agents over MCP: request, decide, approve. Runs locally from the @agentkitai/agentgate-mcp npm package.
estonian
MCP server "estonian", hosted remotely at estonian-mcp.fly.dev, as configured in Elnora-AI/elnora-ai-agent-hackathon-starter-kit.
prime-silo-nexus
MCP server "prime-silo-nexus" as configured in binary16labs/prime-silo. Runs mcp/server.js with node.
ideal-harness-guard
MCP server "ideal-harness-guard" as configured in bharat3645/The-Ideal-Harness. Runs dist/guard/cli/index.js with node.
woven
MCP server "woven" as configured in Ducksss/LifeHack-2026. Runs ./node_modules/tsx/dist/cli.mjs with node. Needs 2 environment variables to run.