Is the Jackalope Dev Moxie Docs MCP server down?

mcp-registry/io.github.jackalope-dev/moxie-docs · v0.4.0

Also listed as glama/jackalope-dev/moxie-docs-mcp

healthy
Last checked 2026-10-20 19:02 UTC · handshake 1.4s

As of 2026-10-20 19:02 UTC, the Jackalope Dev Moxie Docs MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
3,953
outages (90d)
1
tools
14

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

Install Jackalope Dev Moxie Docs MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http jackalope-dev-moxie-docs-mcp-server https://moxiedocs.com/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "jackalope-dev-moxie-docs-mcp-server": {
      "type": "http",
      "url": "https://moxiedocs.com/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (86/100)

B (86/100): 0 error(s), 2 warning(s) across 12 tool(s); ~3,945 tokens of tool definitions.
Scores higher than 55% of 15,413 MCP servers Glimind has audited.
Its tool list costs an agent ~3,945 tokens per session — more than 55% of servers.
86 → 86 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost100
Client compatibility20
Protocol100
Reliability85
Stability88

What to fix (4)

12 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).

Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →

Tools: moxie.get_ai_context, moxie.get_api_context, moxie.get_conventions, moxie.get_doc_gaps, moxie.get_doc_impact and 7 more

Handshake + tools/list takes ~2,982 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 3 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 12 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.jackalope-dev%2Fmoxie-docs/fixes

moxie.get_ai_context 1 change
{
  "name": "moxie_get_ai_context",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "repository": {
        "type": "string",
        "description": "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."
      }
    }
  },
  "annotations": {
    "title": "Get pre-edit AI context",
    "readOnlyHint": true,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}
moxie.get_api_context 1 change
{
  "name": "moxie_get_api_context",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "paths": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Repository-relative file paths to inspect for API endpoint context."
      },
      "repository": {
        "type": "string",
        "description": "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."
      }
    }
  },
  "annotations": {
    "title": "Get API endpoint context",
    "readOnlyHint": true,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}
moxie.get_conventions 1 change
{
  "name": "moxie_get_conventions",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "category": {
        "type": "string",
        "description": "Optional category filter, such as testing, structure, docs, or review."
      },
      "repository": {
        "type": "string",
        "description": "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."
      }
    }
  },
  "annotations": {
    "title": "Get repository conventions",
    "readOnlyHint": true,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.jackalope-dev/moxie-docs"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.jackalope-dev/moxie-docs"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jackalope-dev%2Fmoxie-docs.svg)](https://glimind.com/server/mcp-registry%2Fio.github.jackalope-dev%2Fmoxie-docs?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.jackalope-dev%2Fmoxie-docs?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jackalope-dev%2Fmoxie-docs.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jackalope-dev%2Fmoxie-docs.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.jackalope-dev%2Fmoxie-docs?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:94707a570d111ad9…, first seen 2026-10-17, included at leaf 4250 of 34,593. Version history · verify what your client received.

Tools (14)

Compare: most reliable knowledge servers · most reliable code servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Jackalope Dev Moxie Docs MCP server down right now?

As of 2026-10-20 19:02 UTC, the Jackalope Dev Moxie Docs MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

How many tools does Jackalope Dev Moxie Docs MCP server provide?

Jackalope Dev Moxie Docs MCP server advertises 14 tools, including moxie.get_ai_context, moxie.get_api_context, moxie.get_conventions, moxie.get_doc, moxie.get_doc_gaps.

How do I install Jackalope Dev Moxie Docs MCP server?

Point your MCP client at this streamable-http endpoint: https://moxiedocs.com/api/mcp

Is the Jackalope Dev Moxie Docs MCP server safe to connect to an AI agent?

Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Jackalope Dev Moxie Docs MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve