Loading…
Moxie Docs generates living documentation and MCP context for GitHub repos, citing sources and flagging gaps as code merges.
Do not connect
A critical issue was found. Do not connect this server as-is.
Scanned 1 month ago Due for re-check
A server can change after it's graded. Re-run the automated scan to refresh this report.
This grade is deterministic and reproducible: the same server surface always yields the same grade under a given algorithm version. It is a real automated assessment computed by the MCPGrade engine from what the probe actually observed — not a fabricated or opinion score. It is not a manual human pentest, so it can miss context-specific risks.
Every signal below was measured directly by the automated probe. The grade is derived only from evidence like this — nothing is assumed.
The moxie-docs MCP server exposes 12 tools, focused primarily on general-purpose capabilities. Its published description reads: "Moxie Docs generates living documentation and MCP context for GitHub repos, citing sources and flagging gaps as code merges". It communicates over Streamable HTTP using the 2026-07-28 protocol revision, and does not require authorization to connect. MCPGrade currently rates moxie-docs F — a critical issue was found and the server should not be connected as-is. Its most notable findings include "Cross-tool shadowing" and "Cross-tool shadowing". This report is a deterministic, reproducible automated assessment: the same observed surface always yields the same grade under a given algorithm version, and it is refreshed as new scans arrive and free to read — but it is not a substitute for a manual human security review. Always re-check moxie-docs's advertised tools, transport security, and authorization posture before connecting an autonomous agent or sharing sensitive context with it.
Add moxie-docs to an MCP client using the endpoint below. Review the grade and findings above before granting an autonomous agent access.
MCP endpoint
https://moxiedocs.com/api/mcpStreamable HTTP transport. This is the MCP endpoint, not a website — paste it into your MCP client server list rather than a browser.
Captured passively during the read-only scan. Click any value to find servers that match it.
The tools this server advertises via tools/list — names, purposes, and the parameters each accepts, exactly as enumerated read-only.
Get the coding conventions Moxie inferred for the repository. Read-only; no side effects. Returns a Markdown list grouped by category (e.g. testing, structure, docs, review); each convention has a tit
Keyword and semantic search across the connected repository's generated docs, conventions, documentation gaps, AI-context notes, and indexed code. Read-only; no side effects. Returns ranked matches in
Sorted worst-first. Each finding shows its severity, what it means, its OWASP MCP Top-10 mapping, and a recommended fix — the check id links to the exact methodology row that produced it.
tool: moxie.get_conventions
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: moxie.search_docs
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: moxie.list_docs
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: moxie.get_doc_gaps
A tool exposes a free-text/webhook/feedback parameter with no honest purpose — a classic exfil channel.
his unless your token is scoped to a single repository. Matching is cRecommendationRemove side-channel parameters; constrain tool inputs.
tool: moxie.get_doc_gaps
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: moxie.get_documentation_opportunities
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: moxie.get_documentation_patterns
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: moxie.get_ai_context
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: moxie.get_doc_impact
A tool exposes a free-text/webhook/feedback parameter with no honest purpose — a classic exfil channel.
his unless your token is scoped to a single repository. Matching is cRecommendationRemove side-channel parameters; constrain tool inputs.
tool: moxie.get_doc_impact
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: moxie.get_api_context
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: moxie.review_change
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: moxie.propose_doc_update
Tools that execute commands / write files / make arbitrary requests are exposed without annotations or guards.
t (Markdown) to write to the target file."},"targetPath":{"type":"string","description":RecommendationAnnotate destructive tools and require human approval.
tool: moxie.propose_doc_update
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: moxie.propose_doc_removal
Tools that execute commands / write files / make arbitrary requests are exposed without annotations or guards.
itself does not delete files or open a PR - the deletion happens in your braRecommendationAnnotate destructive tools and require human approval.
tool: moxie.propose_doc_removal
A tool description tries to alter the model’s use of another tool.
RecommendationDescriptions must describe only their own tool.
tool: (server instructions)
A tool description tries to alter the model’s use of another tool.
cs belong, and `moxie.get_conventions` for category-specific rules. 4. After you makeRecommendationDescriptions must describe only their own tool.
The server accepts tool enumeration (and likely invocation) with no authentication.
RecommendationRequire OAuth 2.1 authorization for any server exposing non-public tools.
Vantaj uptime monitoring via MCP — manage monitors, heartbeats, incidents, and status pages.
Unified gateway to Algeria's TKAWEN ecosystem: commerce, certification, and AI tools.
Provides access to the Cohereon Doctrine AI safety framework with governance components, tiered access, and agent onboarding.
Agentic rails for complex workflows with receipts, fees, and MCP tool access.
Structural TC39 spec lookup for ECMA-262 and ECMA-402 in AI agents, SHA-pinned and offline-first.
Structural TC39 spec lookup for ECMA-262 and ECMA-402 in AI agents, SHA-pinned and offline-first.
List the repository's generated documentation as a browsable table of contents - every doc page, not a query-filtered subset. Read-only; no side effects. Returns Markdown grouped by section, each entr
List the unresolved documentation gaps Moxie found - areas of the codebase that lack docs. Read-only; no side effects. Returns a Markdown list, each gap with a title, severity, summary, and suggested
List the actionable documentation updates Moxie recommends as a prioritized queue: missing docs, drift repairs, and PR-template work. Read-only; no side effects. Returns a Markdown list, each opportun
Get Moxie's summary of how THIS repository organizes and maintains documentation - where docs live relative to code and how they are kept current. Read-only; no side effects. Returns a Markdown list o
Get the compact briefing an agent should read before editing this repository: index status, verified commands, agent tips, top conventions, open documentation gaps, and queued documentation opportunit
Given the file paths an agent is about to change (and optionally a subset being deleted), return the conventions, documentation gaps, and existing/related docs whose evidence overlaps those paths, plu
Given file paths an agent is about to touch, return structured context for any API endpoints they map to: method, path, request/response schema, and known consumers/features. Read-only; no side effect
Self-review a change you are about to commit BEFORE opening the PR. Pass the proposed new state of each changed file (and any deleted paths); Moxie returns a severity-ranked list of violations to fix:
Propose a documentation file to add or update as part of YOUR current change. Records a new proposal each call (not idempotent) and does NOT modify your repository or open a PR - Moxie resolves the ta
Propose deleting a Moxie-tracked documentation file that your change makes irrelevant, as part of YOUR current change. Moxie validates the path and returns it for you to delete in your working branch;