Moxie Docs MCP server
io.github.Jackalope-Dev/moxie-docsJackalope-Devstreamable-httpv0.4.0Scanned
Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
12 tools: 3 change things and 9 only read.
- Reads private data · 9
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Moxie Docs MCP server can do
The Moxie Docs MCP server is published by the GitHub account Jackalope-Dev. It has 12 tools. It can create or change data (3 tools: moxie.review_change, moxie.propose_doc_update and moxie.propose_doc_removal), but cannot delete data. 9 tools only read.
9 tools read private data (moxie.get_conventions, moxie.search_docs, moxie.list_docs and 6 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 0.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Changes things 3Claude Code: ask
moxie.propose_doc_removalPropose deleting a Moxie Docs-tracked documentation file that your change makes irrelevant, as part of YOUR current change.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Propose deleting a Moxie Docs-tracked documentation file that your change makes irrelevant, as part of YOUR current change. Moxie Docs validates the path and returns it for you to delete in your working branch; Moxie Docs itself does not delete files or open a PR - the deletion happens in your branch, so it lands in the SAME PR as the code. Returns the resolved path to delete. Provide either slug or targetPath.
Annotations the server declares
- title: Propose a doc removal
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
moxie.propose_doc_updatePropose a documentation file to add or update as part of YOUR current change.No findings
Why it is in this group
- The name "moxie.propose_doc_update" says "update": a word for a change.
Description, as the server wrote it 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 Docs resolves the target path and returns the path + Markdown for YOU to write into your working branch, so the docs land in the SAME PR as the code. Returns the resolved target path and the content to write. Provide either targetPath or baseSlug.
Annotations the server declares
- title: Propose a doc to add or update
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
moxie.review_changeSelf-review a change you are about to commit BEFORE opening the PR.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 Docs returns a severity-ranked list of violations to fix: convention breaches, docs your change makes factually false, net-new API/surface added without docs, and doc references broken by deletions. Read-only; no side effects and no writes. Returns a Markdown verdict (clean | warnings | must-fix) with each finding's location, fix, and - for doc issues - the slug to pass to propose_doc_update. Call this as the final step of the edit flow, then fix findings and re-run.
Annotations the server declares
- title: Review a change before the PR
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 9Show 9 read-only tools
moxie.get_ai_contextGet the compact briefing an agent should read before editing this repository: index status, verified commands, agent tips, top conventions, open documentation gaps, and queued docu…Reads private dataNo findings
Why it is in this group
- The name "moxie.get_ai_context" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "repository": it reads repositories.
- private-dataThe input names a repository (input.repository), and the tool reads: it reads repositories.
Description, as the server wrote it 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 opportunities. Read-only; no side effects. Returns a single Markdown document. Call this first at the start of a task; once you know which files you'll change, follow up with get_doc_impact for path-scoped guidance.
Annotations the server declares
- title: Get pre-edit AI context
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
moxie.get_api_contextGiven 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.Reads private dataNo findings
Why it is in this group
- The name "moxie.get_api_context" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
- private-dataThe input names a repository (input.repository), and the tool reads: it reads repositories.
Description, as the server wrote it 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 effects. Call this before editing API route or schema code, alongside get_doc_impact.
Annotations the server declares
- title: Get API endpoint context
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
moxie.get_conventionsGet the coding conventions Moxie Docs inferred for the repository.Reads private dataNo findings
Why it is in this group
- The name "moxie.get_conventions" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "doc": it reads documents.
- private-dataThe input names a repository (input.repository), and the tool reads: it reads repositories.
Description, as the server wrote it Get the coding conventions Moxie Docs 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 title, summary, confidence score, agent guidance, and the source file paths that evidence it. Use this for the general rules to follow; when you already know the files you're about to edit, prefer moxie.get_doc_impact for conventions scoped to those paths.
Annotations the server declares
- title: Get repository conventions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
moxie.get_doc_gapsList the unresolved documentation gaps Moxie Docs found - areas of the codebase that lack docs.Reads private dataNo findings
Why it is in this group
- The name "moxie.get_doc_gaps" says "get": a word for reading.
What it can reach
- private-dataThe name "moxie.get_doc_gaps" says "get" and "doc": it reads documents.
- private-dataThe description's first sentence says "list" and "doc": it reads documents.
- private-dataThe input names a repository (input.repository), and the tool reads: it reads repositories.
Description, as the server wrote it List the unresolved documentation gaps Moxie Docs 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 file paths. This is gaps only; for the full prioritized work queue that also includes drift repairs and PR-template work, use get_documentation_opportunities, and to scope gaps to files you're about to edit use get_doc_impact.
Annotations the server declares
- title: List documentation gaps
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
moxie.get_doc_impactGiven 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 overl…Reads private dataNo findings
Why it is in this group
- The name "moxie.get_doc_impact" says "get": a word for reading.
What it can reach
- private-dataThe name "moxie.get_doc_impact" says "get" and "doc": it reads documents.
- private-dataThe description's first sentence says "file": it reads files.
- private-dataThe input names a repository (input.repository), and the tool reads: it reads repositories.
Description, as the server wrote it 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, plus a net-new/undocumented analysis and any removal candidates. Read-only; no side effects. Returns a Markdown report. Call this BEFORE writing code so doc updates land in the same PR; then use propose_doc_update to write a doc, or propose_doc_removal for an orphaned one.
Annotations the server declares
- title: Analyze documentation impact
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
moxie.get_documentation_opportunitiesList the actionable documentation updates Moxie Docs recommends as a prioritized queue: missing docs, drift repairs, and PR-template work.Reads private dataNo findings
Why it is in this group
- The name "moxie.get_documentation_opportunities" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "doc": it reads documents.
- private-dataThe input names a repository (input.repository), and the tool reads: it reads repositories.
Description, as the server wrote it List the actionable documentation updates Moxie Docs recommends as a prioritized queue: missing docs, drift repairs, and PR-template work. Read-only; no side effects. Returns a Markdown list, each opportunity with a title, kind (documentation_gap | documentation_drift | pr_template), severity, summary, suggested action, estimated files changed, and source paths. Use this to pick the next doc task; it is the superset of get_doc_gaps (which lists gaps only).
Annotations the server declares
- title: List documentation opportunities
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
moxie.get_documentation_patternsGet Moxie Docs' summary of how THIS repository organizes and maintains documentation - where docs live relative to code and how they are kept current.Reads private dataNo findings
Why it is in this group
- The name "moxie.get_documentation_patterns" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "doc": it reads documents.
- private-dataThe input names a repository (input.repository), and the tool reads: it reads repositories.
Description, as the server wrote it Get Moxie Docs' 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 of pattern entries, each with a title, explanation, and source citations. Use this to decide WHERE a new doc should go before calling propose_doc_update; for the list of WHICH docs need work, use get_documentation_opportunities instead.
Annotations the server declares
- title: Get documentation patterns
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
moxie.list_docsList the repository's generated documentation as a browsable table of contents - every doc page, not a query-filtered subset.Reads private dataNo findings
Why it is in this group
- The name "moxie.list_docs" says "list": a word for reading.
What it can reach
- private-dataThe name "moxie.list_docs" says "list" and "doc": it reads documents.
- private-dataThe description's first sentence says "list" and "repository": it reads repositories.
- private-dataThe input names a repository (input.repository), and the tool reads: it reads repositories.
Description, as the server wrote it 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 entry with its title, slug, repository path, and source paths, plus the total count and a pagination cursor so you can tell whether more pages remain (no silent truncation). Use this to see what docs already exist before adding one (so you don't duplicate) or to find the slug to pass to propose_doc_update; when you are hunting for a specific topic, search_docs is more direct.
Annotations the server declares
- title: List documentation pages
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
moxie.search_docsKeyword and semantic search across the connected repository's generated docs, conventions, documentation gaps, AI-context notes, and indexed code.Reads private dataNo findings
Why it is in this group
- The name "moxie.search_docs" says "search": a word for reading.
What it can reach
- private-dataThe name "moxie.search_docs" says "search" and "doc": it reads documents.
- private-dataThe description's first sentence says "repository": it reads repositories.
- private-dataThe input names a repository (input.repository), and the tool reads: it reads repositories.
Description, as the server wrote it 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 Markdown grouped into Documentation and Code sections, each with a title, snippet, and source paths. Use for open-ended lookups when you don't know which category holds the answer; when you do, the specific getters (get_conventions, get_doc_gaps, get_documentation_opportunities) are more direct. Omitting query returns recent context instead.
Annotations the server declares
- title: Search docs and code
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data9
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://moxiedocs.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://moxiedocs.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://moxiedocs.com/api/mcp: tools/list returned 12 tools to an anonymous client, including moxie.review_change (write), moxie.propose_doc_update (write), moxie.propose_doc_removal (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http moxie-docs https://moxiedocs.com/api/mcpclaude mcp add --transport http moxie-docs https://moxiedocs.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__moxie-docs__moxie_get_conventions",
"mcp__moxie-docs__moxie_search_docs",
"mcp__moxie-docs__moxie_list_docs",
"mcp__moxie-docs__moxie_get_doc_gaps",
"mcp__moxie-docs__moxie_get_documentation_opportunities",
"mcp__moxie-docs__moxie_get_documentation_patterns",
"mcp__moxie-docs__moxie_get_ai_context",
"mcp__moxie-docs__moxie_get_doc_impact",
"mcp__moxie-docs__moxie_get_api_context"
],
"ask": [
"mcp__moxie-docs__moxie_review_change",
"mcp__moxie-docs__moxie_propose_doc_update",
"mcp__moxie-docs__moxie_propose_doc_removal"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as moxie-docs. Review it before you use it.
Capability tags behind 9 rules
- mcp__moxie-docs__moxie_get_conventions private-data
- mcp__moxie-docs__moxie_search_docs private-data
- mcp__moxie-docs__moxie_list_docs private-data
- mcp__moxie-docs__moxie_get_doc_gaps private-data
- mcp__moxie-docs__moxie_get_documentation_opportunities private-data
- mcp__moxie-docs__moxie_get_documentation_patterns private-data
- mcp__moxie-docs__moxie_get_ai_context private-data
- mcp__moxie-docs__moxie_get_doc_impact private-data
- mcp__moxie-docs__moxie_get_api_context private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Jackalope-Dev/moxie-docs/verify?hash=2c54def8a64b0abfdc9baa050dda6220d59414f58f48cc5c2922a0c0addaf299" | jq -e '.changed == false'Pinned hash 2c54def8a64b, from Nov 13, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Jackalope-Dev/moxie-docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Jackalope-Dev/moxie-docs)Source: MCP Registry · repository. Synced Nov 13, 2026, 18:17 UTC.
Moxie Docs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Moxie Docs MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Moxie Docs MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Moxie Docs MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Moxie Docs MCP server have?
- 12 tools: 3 write, 9 read. moxie.review_change, moxie.propose_doc_update, moxie.propose_doc_removal, moxie.get_conventions, moxie.search_docs, moxie.list_docs, moxie.get_doc_gaps, moxie.get_documentation_opportunities and 4 more.
Does the Moxie Docs MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Moxie Docs MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Moxie Docs MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.