MCP context service for Ershu.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ershu-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Ershu MCP [简体中文](README-CN.md) Ershu MCP is the authenticated Model Context Protocol endpoint for Ershu projects. It is intended for coding agents and maintainers who need to discover projects, inspect published documents and repository snapshots, search indexed source, trace project relationships, and read consumer contracts. The service exposes 27 tools over stateless Streamable HTTP. It reads Ershu data through `ershu-core` instead of routing queries through the Ershu API. It does not run the Worker analysis loop or generate AI-authored documents. ## Scope Ershu MCP provides: - project and repository discovery; - document, section, repository tree, and code-index navigation; - bounded source reads after a path has been identified; - indexed search, internal API lookup, project graph queries, change-surface discovery, and static runtime-flow tracing; - source-derived consumer contract, public interface, and schema reads; - queued refreshes for repository trees, code indexes, search indexes, and knowledge graphs. The service does not create projects, repositories, users, or MCP keys. It also does not replace source inspection. Search and graph responses can be partial, stale, or truncated, and published prose can be secondary evidence. ## How it fits into Ershu ```text MCP client | | Streamable HTTP + Bearer token v ershu-mcp | +-- ershu-core services and schemas +-- shared PostgreSQL data +-- repository cache +-- Milvus-backed retrieval when configured ``` `ershu-mcp` depends on `ershu-core`. It does not import or call `ershu-api` or `ershu-worker`. A full Ershu installation combines the independently versioned components in the `ershu` deployment repository. ## Requirements - Python 3.14 or newer - [uv](https://docs.astral.sh/uv/) - PostgreSQL with the Ershu schema - Git when the service needs to read remote repositories - Milvus for semantic retrieval; search responses report when they use a weaker fallback ## Inst…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.