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/QWED-AI/qwed-mcpWrote 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/qwed-ai/qwed-mcp/qwed-mcp)<a href="https://agentmods.dev/mcp/qwed-ai/qwed-mcp/qwed-mcp"><img src="https://agentmods.dev/badge/mcp/qwed-ai/qwed-mcp/qwed-mcp/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/qwed-ai/qwed-mcp/qwed-mcp"><img src="https://agentmods.dev/badge/mcp/qwed-ai/qwed-mcp/qwed-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
qwed-mcp 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 11d 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
{ "qwed-mcp": { "command": "uvx", "args": [ "qwed-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.
- 11d ago First seen · 8 lines scan A 60d21c15982d
qwed-mcp is an MCP server published in the GitHub repository QWED-AI/qwed-mcp (0 stars, last pushed 15d ago), licensed Apache-2.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-08-31.
Other mcp servers, from other repositories
agentlens
Tamper-evident, SHA-256 hash-chained audit trail and observability for AI agents. Runs locally from the @agentkitai/agentlens-mcp npm package.
boj-server
Bundle of Joy (BoJ) MCP Server — cartridge-based DevOps + multi-agent coordination toolkit with 100 domain cartridges (database, container, git, k8s, observability, secrets, IaC, multi-instance AI coord, and more). Formally verified (Idris2) core; MPL-2.0. Runs locally from the @hyperpolymath/boj-server npm package.…
ethersflow
Model Context Protocol (MCP) server for EthersFlow — run proposed agent actions through federated adversarial multi-model consensus before executing them. Runs locally from the @ethersflow/mcp-server npm package. Needs 1 environment variable to run.
causallayer-mcp
Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split. Remote server at causallayer-mcp-demo.zykm9qkk7j.workers.dev.
causallayer
Deterministic AI liability attribution with Bitcoin-anchored proof certificates. Runs locally from the causallayer-mcp npm package.
guardrails
AI Agent Guardrails MCP server - security layer. Runs locally from the guardrails-mcp-server npm package.