io.github.nyuchi/nyuchi-docs
REMOTE · DOCS.NYUCHI.COM · 2 COMPONENTS · SCANNED SEP 20
Search, read, and ask the Nyuchi docs (docs.nyuchi.com); send feedback or raise issues.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 395 tokens (~79/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "submit_feedback" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.nyuchi/nyuchi-docs MCP server?
io.github.nyuchi/nyuchi-docs is a hosted endpoint at https://docs.nyuchi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · docs.nyuchi.com
claude mcp add --transport http nyuchi-nyuchi-docs 'https://docs.nyuchi.com/mcp'
{
"mcpServers": {
"nyuchi-nyuchi-docs": {
"url": "https://docs.nyuchi.com/mcp"
}
}
} {
"servers": {
"nyuchi-nyuchi-docs": {
"type": "http",
"url": "https://docs.nyuchi.com/mcp"
}
}
} [mcp_servers.nyuchi-nyuchi-docs] url = "https://docs.nyuchi.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nyuchi-nyuchi-docs": {
"type": "remote",
"url": "https://docs.nyuchi.com/mcp",
"enabled": true
}
}
} openclaw mcp add nyuchi-nyuchi-docs --url 'https://docs.nyuchi.com/mcp' --transport streamable-http
mcp_servers:
nyuchi-nyuchi-docs:
url: "https://docs.nyuchi.com/mcp" {
"McpServers": {
"nyuchi-nyuchi-docs": {
"Transport": "http",
"Url": "https://docs.nyuchi.com/mcp"
}
}
} assistant mcp add nyuchi-nyuchi-docs -t streamable-http -u 'https://docs.nyuchi.com/mcp'
{
"mcpServers": {
"nyuchi-nyuchi-docs": {
"type": "http",
"url": "https://docs.nyuchi.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://docs.nyuchi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nyuchi.com | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 2b4f5e5911ba2657132b3c72b38b8ba9 |
| SANs: nyuchi.com, docs.nyuchi.com, *.docs.nyuchi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of docs.nyuchi.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nyuchi.com. | present | 2371 | 13 | Verified |
| docs.nyuchi.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docs.nyuchi.com/mcp | Verified | 200 | |
| http (plaintext) | http://docs.nyuchi.com/mcp | HTTPS enforced | 301 | https://docs.nyuchi.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_docs Ask the docs ~39
Ask a question and get a synthesized answer grounded in docs.nyuchi.com, with source citations.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question to answer |
No output schema declared.
No examples provided.
raise_issue Raise a docs issue ~86
Raise an actionable issue against the documentation (wrong instructions, broken example, outdated page). Files a GitHub issue on nyuchi/nyuchi-docs when configured, otherwise queues it for the docs team.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | What is wrong and where |
| page | string | – | Page path or URL the issue is about |
| title | string | yes | Short issue title |
No output schema declared.
No examples provided.
read_page Read a docs page ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Page path or full docs.nyuchi.com URL |
No output schema declared.
No examples provided.
search_docs Search the docs ~58
Keyword/semantic search over docs.nyuchi.com. Returns matching pages with titles, URLs and snippets.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to search for |
| top_k | number | – | Max results (default 5, max 10) |
No output schema declared.
No examples provided.
submit_feedback Submit docs feedback ~84
Send feedback about the documentation — a correction, something confusing, something missing. Stored for the docs team.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | Optional contact (email/handle) for follow-up |
| kind | string | – | What kind of feedback this is |
| message | string | yes | The feedback itself |
| page | string | – | Page path or URL the feedback is about |
No output schema declared.
No examples provided.
What is the io.github.nyuchi/nyuchi-docs MCP server?
io.github.nyuchi/nyuchi-docs is an MCP server listed in the public MCP registry as io.github.nyuchi/nyuchi-docs. Search, read, and ask the Nyuchi docs (docs.nyuchi.com); send feedback or raise issues. This page covers its hosted endpoint (https://docs.nyuchi.com/mcp).
Is the io.github.nyuchi/nyuchi-docs MCP server safe to use?
io.github.nyuchi/nyuchi-docs scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.nyuchi/nyuchi-docs MCP server expose?
io.github.nyuchi/nyuchi-docs exposes 5 tools: search_docs, ask_docs, read_page, submit_feedback, raise_issue. Their descriptions and schemas cost roughly 331 tokens of context every time the server is loaded.
Does the io.github.nyuchi/nyuchi-docs MCP server require authentication?
No. We connected to io.github.nyuchi/nyuchi-docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.nyuchi/nyuchi-docs MCP server still maintained?
io.github.nyuchi/nyuchi-docs is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.