io.github.Jackalope-Dev/moxie-docs

MCPcommunitylive
v0.3.0io.github.Jackalope-DevUnknownUpdated 2mo agoGitHub

Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.

Endpoint healthlive
checked 12 days ago · 1636ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
Authorio.github.Jackalope-Dev
LicenseUnknown
Version0.3.0
Sourcemcp-registry
GitHubJackalope-Dev/Moxie-Docs-MCP
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
Hosted endpoint only: this assessment covers who publishes it and whether it answers, not the code behind it. No CVE, dependency or source analysis applies, so nothing here is a clean bill for that code.
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface19 tools · 1 privileged
Security scan✓ CleanvHEAD · 2mo agoHow well does this scan work?
EvalsNone
IndexedJul 8, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

19 tools · 1 privileged
Statically extracted from the published packagevHEAD · 2mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

document-this-changeNo description published

This tool published no description. Forge does not invent one.

changedPathsNo description published

This tool published no description. Forge does not invent one.

deletedPathsprivilegedNo description published

This tool published no description. Forge does not invent one.

repositoryNo description published

This tool published no description. Forge does not invent one.

fix-stale-docsNo description published

This tool published no description. Forge does not invent one.

severityNo description published

This tool published no description. Forge does not invent one.

review-before-finalizeNo description published

This tool published no description. Forge does not invent one.

moxie.get_conventionsNo description published

This tool published no description. Forge does not invent one.

moxie.search_docsNo description published

This tool published no description. Forge does not invent one.

moxie.list_docsNo description published

This tool published no description. Forge does not invent one.

moxie.get_doc_gapsNo description published

This tool published no description. Forge does not invent one.

moxie.get_documentation_opportunitiesNo description published

This tool published no description. Forge does not invent one.

moxie.get_documentation_patternsNo description published

This tool published no description. Forge does not invent one.

moxie.get_ai_contextNo description published

This tool published no description. Forge does not invent one.

moxie.get_doc_impactNo description published

This tool published no description. Forge does not invent one.

moxie.get_api_contextNo description published

This tool published no description. Forge does not invent one.

moxie.review_changeNo description published

This tool published no description. Forge does not invent one.

moxie.propose_doc_updateNo description published

This tool published no description. Forge does not invent one.

moxie.propose_doc_removalNo description published

This tool published no description. Forge does not invent one.

0 of 19 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

19 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.