Skip to content

nyuchi-docs MCP server

io.github.nyuchi/nyuchi-docsnyuchistreamable-httpv0.1.0Scanned

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

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

Tools: 0 delete, 1 irreversible, 2 write, 2 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the nyuchi-docs MCP server can do

The nyuchi-docs MCP server is published by the GitHub account nyuchi. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (submit_feedback) and create or change data (2 tools: ask_docs and raise_issue), but cannot delete data. 2 tools only read.

2 tools read private data (search_docs and read_page).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 6, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

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 2Show 2 read-only tools
  • read_pageFetch a docs.nyuchi.com page and return its readable text content.Reads private dataNo findings

    Why it is in this group

    • The name "read_page" says "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "doc": it reads documents.
    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.Reads private dataNo findings

    Why it is in this group

    • The name "search_docs" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_docs" says "search" and "doc": it reads documents.
    • private-dataThe description's first sentence says "doc": it reads documents.
    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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:09 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: tools/list answered HTTP 400.

Posture changes

  1. Nov 20, 2026
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0; Protocol version: 2025-06-18 -> none.View diff
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

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
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nyuchi-docs. Review it before you use it.

Capability tags behind 2 rules
  • mcp__nyuchi-docs__search_docs private-data
  • mcp__nyuchi-docs__read_page private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.nyuchi/nyuchi-docs/verify?hash=ee2a1ee409db8a26bb9d96f28a87544ff62ee906d537c192e4a76d345f176e4e" | jq -e '.changed == false'

Pinned hash ee2a1ee409db, from Nov 6, 2026, 06:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.nyuchi/nyuchi-docs/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.nyuchi/nyuchi-docs
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.nyuchi/nyuchi-docs.svg)](https://radar.anlyon.com/servers/io.github.nyuchi/nyuchi-docs)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:42 UTC.

nyuchi-docs MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the nyuchi-docs MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the nyuchi-docs MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the nyuchi-docs MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: submit_feedback.

What tools does the nyuchi-docs MCP server have?

5 tools: 1 irreversible, 2 write, 2 read. submit_feedback, ask_docs, raise_issue, search_docs and read_page.

Does the nyuchi-docs MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the nyuchi-docs MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the nyuchi-docs MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 6, 2026.