Is the Liz6 Docs MCP server down?

mcp-registry/com.liz6/docs · v3.1.4

degraded
Last checked 2026-10-25 15:07 UTC · handshake 2s

As of 2026-10-25 15:07 UTC, the Liz6 Docs MCP server is degraded with a Glimind reliability score of 46/100 (grade D). Over the last 30 days it answered 81.3% of Glimind's liveness checks. It had 1617 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
81.3%
checks observed
5,221
outages (90d)
1617
tools
5

Read-only search and Markdown access to liz's public docs, prompts, resources, and an MCP App.

Install Liz6 Docs MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http liz6-docs-mcp-server https://doc.liz6.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "liz6-docs-mcp-server": {
      "type": "http",
      "url": "https://doc.liz6.com/mcp"
    }
  }
}

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

Agent-readiness: B (83/100)

B (83/100): 1 error(s), 2 warning(s) across 5 tool(s); ~968 tokens of tool definitions.
Scores higher than 40% of 15,706 MCP servers Glimind has audited.
Its tool list costs an agent ~968 tokens per session — lighter than 75% of servers.
82 → 83 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions62
Safety hints100
Token cost100
Client compatibility100
Protocol100
Reliability5
Stability100

What to fix (3)

Reachable 81.3% of the time over the last 30 days; median recovery 7 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

5 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: list_documents, related_documents

Handshake + tools/list takes ~3,876 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.

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/com.liz6/docs"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.liz6/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%2Fcom.liz6%2Fdocs.svg)](https://glimind.com/server/mcp-registry%2Fcom.liz6%2Fdocs?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fcom.liz6%2Fdocs?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.liz6%2Fdocs.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.liz6%2Fdocs.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.liz6%2Fdocs?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:a1f25a1fa01f8b76…, first seen 2026-10-17, included at leaf 6658 of 66,889. Version history · verify what your client received.

Working alternatives

Tools (5)

Compare: most reliable knowledge 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 Liz6 Docs MCP server down right now?

As of 2026-10-25 15:07 UTC, the Liz6 Docs MCP server is degraded with a Glimind reliability score of 46/100 (grade D). Over the last 30 days it answered 81.3% of Glimind's liveness checks. It had 1617 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Liz6 Docs MCP server provide?

Liz6 Docs MCP server advertises 5 tools, including list_documents, read_document, read_document_section, related_documents, search_documents.

How do I install Liz6 Docs MCP server?

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

Is the Liz6 Docs MCP server safe to connect to an AI agent?

Glimind scanned all 5 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 Liz6 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