Skip to content

io.github.nyuchi/nyuchi-docs

by nyuchi · remote · local (npm) · no sign-in to list tools · v0.1.0 · published by GitHub user nyuchi

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

Final · 1Changes · 2

5 tools: 1 do something that can't be undone, 2 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Can't be undone 1Claude Code: ask
  • submit_feedbackSend feedback about the documentation — a correction, something confusing, something missing.No findings

    Why it is in this group

    • The name "submit_feedback" says "submit": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    Send feedback about the documentation — a correction, something confusing, something missing. Stored for the docs team.
Changes things 2Claude Code: ask
  • ask_docsAsk a question and get a synthesized answer grounded in docs.nyuchi.com, with source citations.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Ask a question and get a synthesized answer grounded in docs.nyuchi.com, with source citations.
  • raise_issueRaise an actionable issue against the documentation (wrong instructions, broken example, outdated page).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 2Claude Code: allow
  • read_pageFetch a docs.nyuchi.com page and return its readable text content.No findings

    Why it is in this group

    • The name "read_page" says "read": a word for reading.
    Description, as the server wrote it
    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.
  • search_docsKeyword/semantic search over docs.nyuchi.com.No findings

    Why it is in this group

    • The name "search_docs" says "search": a word for reading.
    Description, as the server wrote it
    Keyword/semantic search over docs.nyuchi.com. Returns matching pages with titles, URLs and snippets.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__nyuchi-docs__search_docs",
      "mcp__nyuchi-docs__read_page"
    ],
    "ask": [
      "mcp__nyuchi-docs__ask_docs",
      "mcp__nyuchi-docs__submit_feedback",
      "mcp__nyuchi-docs__raise_issue"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as nyuchi-docs. Review it before you use it.