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/razzant/claudexorWrote 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/razzant/claudexor/copilot-claudexor)<a href="https://agentmods.dev/mcp/razzant/claudexor/copilot-claudexor"><img src="https://agentmods.dev/badge/mcp/razzant/claudexor/copilot-claudexor/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/razzant/claudexor/copilot-claudexor"><img src="https://agentmods.dev/badge/mcp/razzant/claudexor/copilot-claudexor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claudexor 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 9d 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
{
"claudexor": {
"command": "claudexor",
"args": [
"mcp",
"serve"
]
}
}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.
- 9d ago First seen · 9 lines scan A e181cfeaf05b
claudexor is an MCP server published in the GitHub repository razzant/claudexor (433 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-08-30.
Other mcp servers, from other repositories
ctxmem
Git-native, shareable project memory for AI coding agents — fully local, no cloud. Runs locally from the ctxmem Python package.
opencode-export
MCP server "opencode-export" as configured in ZelinZhou-THU/opencode-export. Runs locally from the opencode-export Python package.
context-guardian-mcp
MCP server + proxy that cuts cloud LLM costs 36-42% by indexing context locally with Ollama and giving agents precision retrieval tools instead of raw dumps. Runs locally from the context-guardian-mcp npm package.
react-devtools
MCP server "react-devtools" as configured in qbit-ai/qbit. Runs tools/react-devtools-bridge/dist/cli.js with node.
dos-kernel
Dispatch Operating System — the domain-free trust substrate for fleets of autonomous agents (verdict spine, ship oracle, structured refusal, lane arbiter, correlation spine). Runs locally from the dos-kernel Python package. Needs 1 environment variable to run.
rewynd
MCP server "rewynd" as configured in SrinjoyDev/rewynd. Launched with rewynd mcp.