mcp-registry/io.github.nyuchi/nyuchi-docs · v1.0.0
As of 2026-10-26 18:42 UTC, the Nyuchi Docs MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Search, read, and ask the Nyuchi docs (docs.nyuchi.com); send feedback or raise issues.
Point your MCP client at this streamable-http endpoint: https://docs.nyuchi.com/mcp
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
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 →
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.nyuchi%2Fnyuchi-docs/fixes
{
"name": "read_page",
"description": "Fetch a docs.nyuchi.com page and return its readable text content. Accepts a path (e.g. /kweli/verification/) or a full docs.nyuchi.com URL.",
"inputSchema": {
"type": "object",
"required": [
"path"
],
"properties": {
"path": {
"type": "string",
"description": "Page path or full docs.nyuchi.com URL"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Read a docs page"
}{
"name": "search_docs",
"description": "Keyword/semantic search over docs.nyuchi.com. Returns matching pages with titles, URLs and snippets.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "What to search for"
},
"top_k": {
"type": "number",
"description": "Max results (default 5, max 10)"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Search the docs"
}{
"name": "submit_feedback",
"description": "Send feedback about the documentation — a correction, something confusing, something missing. Stored for the docs team.",
"inputSchema": {
"type": "object",
"required": [
"message"
],
"properties": {
"kind": {
"enum": [
"correction",
"confusing",
"missing",
"praise",
"other"
],
"type": "string",
"description": "What kind of feedback this is"
},
"page": {
"type": "string",
"description": "Page path or URL the feedback is about"
},
"contact": {
"type": "string",
"description": "Optional contact (email/handle) for follow-up"
},
"message": {
"type": "string",
"description": "The feedback itself"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Submit docs feedback"
}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.nyuchi/nyuchi-docs"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.nyuchi/nyuchi-docs"}) over MCP.
submit_feedback ~167 tokensraise_issue ~145 tokenssearch_docs ~95 tokensread_page ~90 tokensask_docs ~75 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fio.github.nyuchi%2Fnyuchi-docs?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.nyuchi%2Fnyuchi-docs?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.nyuchi%2Fnyuchi-docs.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.nyuchi%2Fnyuchi-docs.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.nyuchi%2Fnyuchi-docs?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3b4f01a33ccebe71…, first seen 2026-10-17, included at leaf 12059 of 74,789. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable other servers · most reliable web servers · most reliable search servers · most reliable communication servers
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.
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"
}
}
}
As of 2026-10-26 18:42 UTC, the Nyuchi Docs MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Nyuchi Docs MCP server advertises 5 tools, including ask_docs, raise_issue, read_page, search_docs, submit_feedback.
Point your MCP client at this streamable-http endpoint: https://docs.nyuchi.com/mcp
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.
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.