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/sabbour/agentweaverWrote 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/sabbour/agentweaver/agentweaver_local)<a href="https://agentmods.dev/mcp/sabbour/agentweaver/agentweaver_local"><img src="https://agentmods.dev/badge/mcp/sabbour/agentweaver/agentweaver_local/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/sabbour/agentweaver/agentweaver_local"><img src="https://agentmods.dev/badge/mcp/sabbour/agentweaver/agentweaver_local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentweaver_local 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.
What it actually says
{
"agentweaver_local": {
"command": "dotnet",
"args": [
"run",
"--project",
"apps/Agentweaver.Mcp",
"--",
"--stdio"
],
"env": {
"AGENTWEAVER_API_URL": "http://localhost:5000"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 15 lines scan A 85c7bcd83383
agentweaver_local is an MCP server published in the GitHub repository sabbour/agentweaver (5 stars, last pushed today), 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-09-10.
Other mcp servers, from other repositories
nora
Operate self-hosted OpenClaw and Hermes agent fleets on Docker or Kubernetes from MCP clients. Runs locally from the @noraai/mcp-server npm package. Needs 3 environment variables to run.
nora
MCP server for Nora — deploy, monitor, and operate self-hosted OpenClaw and Hermes agent fleets on Docker or Kubernetes. Runs locally from the @noraai/mcp-server npm package. Needs 1 environment variable to run.
janus-mcp
Secure Kubernetes MCP server: redacted diagnostics and human-approved writes, credentials never leave the process. Runs locally from the janus-mcp-server Python package.
clawdlinux
MCP server "clawdlinux" as configured in Clawdlinux/agentic-operator-core. Launched with agentctl mcp serve --transport stdio --default-namespace agentic-system. Needs 1 environment variable to run.
work-buddy
MCP server "work-buddy", hosted remotely at localhost, as configured in KadenMc/work-buddy.
fluxgit-mcp-server
MCP server "fluxgit-mcp-server" as configured in fluxgit-hq/fluxgit-mcp-server. Launched with fluxgit-mcp-sidecar.