io.github.Jackalope-Dev/moxie-docs

Est-ce que io.github.Jackalope-Dev/moxie-docs est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.Jackalope-Dev/moxie-docs » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 12 outils

• moxie.get_ai_context≈ 249 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.

  Exemple d'appel

  {"name": "moxie.get_ai_context", "arguments": {"repository": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• moxie.get_api_context≈ 254 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • paths · array · optionnel
    Repository-relative file paths to inspect for API endpoint context.
  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.

  Exemple d'appel

  {"name": "moxie.get_api_context", "arguments": {"paths": [], "repository": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• moxie.get_conventions≈ 294 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • category · string · optionnel
    Optional category filter, such as testing, structure, docs, or review.
  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.

  Exemple d'appel

  {"name": "moxie.get_conventions", "arguments": {"category": "texte", "repository": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• moxie.get_doc_gaps≈ 281 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • severity · string · optionnel
    Optional severity filter: high, medium, low, or info.
  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.

  Exemple d'appel

  {"name": "moxie.get_doc_gaps", "arguments": {"severity": "texte", "repository": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• moxie.get_doc_impact≈ 385 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.
  • changedPaths · array · requis
    Repository-relative file paths the agent intends to modify (e.g., apps/web/src/app/api/billing/webhook/route.ts).
  • deletedPaths · array · optionnel
    Subset of paths that are being DELETED. Moxie Docs flags any doc whose every cited source path is in this list as a removal candidate for moxie.propose_doc_removal.

  Exemple d'appel

  {"name": "moxie.get_doc_impact", "arguments": {"changedPaths": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• moxie.get_documentation_opportunities≈ 326 tokens

  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).

  Paramètres, retour & exemple (3)

  Paramètres

  • kind · string · optionnel
    Optional kind filter: documentation_gap, documentation_drift, or pr_template.
  • severity · string · optionnel
    Optional severity filter: high, medium, low, or info.
  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.

  Exemple d'appel

  {"name": "moxie.get_documentation_opportunities", "arguments": {"kind": "texte", "severity": "texte", "repository": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• moxie.get_documentation_patterns≈ 261 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.

  Exemple d'appel

  {"name": "moxie.get_documentation_patterns", "arguments": {"repository": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• moxie.list_docs≈ 395 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · number · optionnel
    Maximum docs to return (1-200, default 50).
  • offset · number · optionnel
    Number of docs to skip for pagination (default 0). Use the cursor in the response to fetch the next page.
  • section · string · optionnel
    Optional section/collection filter (case-insensitive substring), e.g. "Backend" or "Billing". Omit to list every section.
  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.

  Exemple d'appel

  {"name": "moxie.list_docs", "arguments": {"limit": 1, "offset": 1, "section": "texte", "repository": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• moxie.propose_doc_removal≈ 375 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • slug · string · optionnel
    Slug of the existing generated doc to remove.
  • reason · string · optionnel
    Why this doc is no longer relevant.
  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.
  • targetPath · string · optionnel
    Repository-relative path of the doc to remove (must be a Moxie Docs-tracked doc). Use instead of slug.
  • removedSourcePaths · array · optionnel
    Code paths being deleted that made this doc irrelevant, for provenance.

  Exemple d'appel

  {"name": "moxie.propose_doc_removal", "arguments": {"slug": "texte", "reason": "texte", "repository": "texte", "targetPath": "texte", "removedSourcePaths": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• moxie.propose_doc_update≈ 444 tokens

  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.

  Paramètres, retour & exemple (7)

  Paramètres

  • title · string · requis
    Short human title for the documentation update.
  • reason · string · optionnel
    Why this doc is being added or changed.
  • baseSlug · string · optionnel
    Slug of an existing generated doc to update instead of supplying targetPath.
  • markdown · string · requis
    The documentation content (Markdown) to write to the target file.
  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.
  • targetPath · string · optionnel
    Repository-relative path to write the doc to (e.g., docs/billing.md). Omit to resolve from baseSlug.
  • sourcePaths · array · optionnel
    Code paths this doc documents, for provenance.

  Exemple d'appel

  {"name": "moxie.propose_doc_update", "arguments": {"title": "texte", "markdown": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• moxie.review_change≈ 540 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.
  • changedFiles · array · requis
    The files your change adds or modifies, in their PROPOSED new state. Provide newContent (the full new file text) for each; you may also/instead provide patch (a unified diff). Max 20 files per call.
  • deletedPaths · array · optionnel
    Repository-relative paths your change DELETES, so Moxie Docs can flag docs whose references break.

  Exemple d'appel

  {"name": "moxie.review_change", "arguments": {"changedFiles": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• moxie.search_docs≈ 336 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · number · optionnel
    Maximum matches to return (1-20, default 8).
  • query · string · optionnel
    Search phrase or topic. Omit to return recent context for the repository.
  • repository · string · optionnel
    The target repository as "owner/name" (e.g. "acme/app"). Always pass this unless your token is scoped to a single repository. Matching is case-insensitive. If omitted when the token serves multiple repos, the call returns the list of repositories to choose from instead of an answer.

  Exemple d'appel

  {"name": "moxie.search_docs", "arguments": {"limit": 1, "query": "texte", "repository": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://moxiedocs.com/api/mcp