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/Jackalope-Dev/Moxie-Docs-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/jackalope-dev/moxie-docs-mcp/moxie-docs)<a href="https://agentmods.dev/mcp/jackalope-dev/moxie-docs-mcp/moxie-docs"><img src="https://agentmods.dev/badge/mcp/jackalope-dev/moxie-docs-mcp/moxie-docs/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/jackalope-dev/moxie-docs-mcp/moxie-docs"><img src="https://agentmods.dev/badge/mcp/jackalope-dev/moxie-docs-mcp/moxie-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
moxie-docs 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
{
"moxie-docs": {
"type": "http",
"url": "https://moxiedocs.com/api/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.
- 1mo ago First seen · 6 lines scan A 482a7a89fe96
moxie-docs is an MCP server published in the GitHub repository Jackalope-Dev/Moxie-Docs-MCP (2 stars, last pushed 2d 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
fonto-docs
Fonto (FontoXML) documentation for AI tools. Converts DITA XML to Markdown on demand. Remote server at fonto-docs.elliat.nl.
mcp-office-excel
Local-first MCP servers for Microsoft Office — Excel, PowerPoint, and Word automation via the Model Context Protocol. Runs on Windows. Runs locally from the mcp-office Python package. Needs 4 environment variables to run.
honest-drive-mcp
Local MCP server for Google Drive with full permission management — read, write, share files with your Google account. Runs locally from the honest-drive-mcp Python package.
PDF File Context Protocol — semantic PDF operations for LLMs. Runs locally from the fcp-pdf Python package.
a2aidentitytoll-mcp
Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history. Remote server at a2aidentitytoll.clauxel.com.
google-sheets
MCP server "google-sheets" as configured in ringo380/claude-google-sheets-mcp. Runs claude_google_sheets.server with /path/to/claude-google-sheets-mcp/venv/bin/python.