_ registry / mcp streamable-http · checked 18m ago

nyuchi-docs

https://docs.nyuchi.com

Registry code: 68a8e8a6d4168411

api record

Read and search the Nyuchi engineering + product documentation at docs.nyuchi.com, and send feedback or raise issues about it. Prefer search_docs to locate pages, read_page for full page text, ask_docs for synthesized answers with citations. Use submit_feedback for corrections/comments and raise_issue for actionable problems.

endpoint
https://docs.nyuchi.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is nyuchi-docs live?
Yes — it answered the hub's last check (checked 18m ago). It answered 99% of checks over the last 30 days.
Is nyuchi-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does nyuchi-docs have?
5 tools: ask_docs, read_page, submit_feedback, raise_issue, search_docs.
Is nyuchi-docs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99%· all time 99%

latency
121ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 291 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
knowledge & reference documentation & docs search
used for
  • search nyuchi documentation
  • read a docs page
  • ask a question over the docs
  • raise an issue about the docs
takes → gives
text → text
tools
3 reads2 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • ask_docs reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "question"
  ],
  "properties": {
    "question": {
      "type": "string",
      "description": "The question to answer"
    }
  }
}
    arguments 12 lines
  • read_page reads unknown 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "Page path or full docs.nyuchi.com URL"
    }
  }
}
    arguments 12 lines
  • submit_feedback changes data unknown never probed

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

    mcp-tool

    {
  "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"
    }
  }
}
    arguments 31 lines
  • raise_issue changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title",
    "body"
  ],
  "properties": {
    "body": {
      "type": "string",
      "description": "What is wrong and where"
    },
    "page": {
      "type": "string",
      "description": "Page path or URL the issue is about"
    },
    "title": {
      "type": "string",
      "description": "Short issue title"
    }
  }
}
    arguments 21 lines
  • search_docs reads unknown 7h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "What to search for"
    },
    "top_k": {
      "type": "number",
      "description": "Max results (default 5, max 10)"
    }
  }
}
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 68a8e8a6d4168411.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/68a8e8a6d4168411/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/68a8e8a6d4168411/badge.svg)](https://brick.blue/agent/68a8e8a6d4168411?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.