# io.github.nyuchi/nyuchi-docs (remote · docs.nyuchi.com)

Search, read, and ask the Nyuchi docs (docs.nyuchi.com); send feedback or raise issues.

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `docs.nyuchi.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/nyuchi-nyuchi-docs/docs.md), [page](https://verifymcp.io/servers/nyuchi-nyuchi-docs/docs)
- npm · `nyuchi-docs-mcp`: 39/100, [markdown](https://verifymcp.io/servers/nyuchi-nyuchi-docs/nyuchi-docs-mcp.md), [page](https://verifymcp.io/servers/nyuchi-nyuchi-docs/nyuchi-docs-mcp)

## Channel facts

- Endpoint: `https://docs.nyuchi.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 395 tokens (~79/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http nyuchi-nyuchi-docs https://docs.nyuchi.com/mcp
```

### Codex

```toml
[mcp_servers.nyuchi-nyuchi-docs]
url = "https://docs.nyuchi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nyuchi-nyuchi-docs": {
      "type": "remote",
      "url": "https://docs.nyuchi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nyuchi-nyuchi-docs --url https://docs.nyuchi.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nyuchi-nyuchi-docs:
    url: "https://docs.nyuchi.com/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (5)

### `search_docs` (~58 tokens)

Search the docs

Keyword/semantic search over docs.nyuchi.com. Returns matching pages with titles, URLs and snippets.

Input parameters:

- `query` (string, required): What to search for
- `top_k` (number): Max results (default 5, max 10)

### `ask_docs` (~39 tokens)

Ask the docs

Ask a question and get a synthesized answer grounded in docs.nyuchi.com, with source citations.

Input parameters:

- `question` (string, required): The question to answer

### `read_page` (~64 tokens)

Read a docs page

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.

Input parameters:

- `path` (string, required): Page path or full docs.nyuchi.com URL

### `submit_feedback` (~84 tokens)

Submit docs feedback

Send feedback about the documentation — a correction, something confusing, something missing. Stored for the docs team.

Input parameters:

- `contact` (string): Optional contact (email/handle) for follow-up
- `kind` (string): What kind of feedback this is
- `message` (string, required): The feedback itself
- `page` (string): Page path or URL the feedback is about

### `raise_issue` (~86 tokens)

Raise a docs issue

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.

Input parameters:

- `body` (string, required): What is wrong and where
- `page` (string): Page path or URL the issue is about
- `title` (string, required): Short issue title

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nyuchi-nyuchi-docs/docs#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 66
- 2026-07-31: 66
- 2026-07-30: 65
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 63
- 2026-07-26: 63

## Links

- Remote endpoint: https://docs.nyuchi.com/mcp
- Repository: https://github.com/nyuchi/nyuchi-docs
- Website: https://docs.nyuchi.com/integrations/docs-mcp/
- Changelog RSS feed: https://verifymcp.io/servers/nyuchi-nyuchi-docs/docs/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/nyuchi-nyuchi-docs/docs/changelog.json
- HTML version of this page: https://verifymcp.io/servers/nyuchi-nyuchi-docs/docs