Data · Local MCP server
ResearchZosho
Deep research assistant that checks its citations against the sources and keeps what it found.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Wyrdsekai/researchzosho- Version
- 0.5.2
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- npm, OCI image (Docker)
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- Wyrdsekai (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Wyrdsekai) · how
- Website
- researchzosho.org
- Repository
- github.com/Wyrdsekai/researchzosho
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @wyrdsekai/researchzosho-mcp | 0.5.2 | stdio |
| OCI image (Docker)runtime: docker | ghcr.io/wyrdsekai/researchzosho:0.5.2 | - | stdio |
How to connect ResearchZosho
ResearchZosho runs locally from a Node.js package published to the npm registry: @wyrdsekai/researchzosho-mcp version 0.5.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @wyrdsekai/researchzosho-mcp@0.5.2. It reads the environment variable RESEARCHZOSHO_LIBRARY; set it in the client's configuration for this server.
ResearchZosho runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/wyrdsekai/researchzosho:0.5.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm ghcr.io/wyrdsekai/researchzosho:0.5.2. Required arguments: -i, --rm and -v.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"researchzosho": {
"command": "npx",
"args": [
"-y",
"@wyrdsekai/researchzosho-mcp@0.5.2"
],
"env": {
"RESEARCHZOSHO_LIBRARY": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from Wyrdsekai (GitHub)
| Server | Runs |
|---|---|
| CodeZaikuA coding and development harness on local models or hosted APIs, for code, review, research and ops. | Local · stdio |
More data servers
| Server | Runs |
|---|---|
| Research ScanResearch Scan finds and verifies the 5-10 recent papers that matter most for a research question. | Local · stdio |
| Research Synthesis Price IndexBioBricks: the median advertised gene synthesis price per base pair, read from verified vendor... | Local · stdio |
| ResearchoracleResearchOracle - 11 financial research tools: 10-K parsing, equity, macro, citation graph. | Remote · HTTPLive check: ✓ handshake |
| ResearchTwinFederated research discovery with S-Index metrics across a network of digital twins. | Local · stdio |
| Resell ProObserved Vinted market analytics: compare brands, research niches, and discover trends via OAuth. | Remote · HTTPLive check: sign-in required |
| Resollo Agent APIResollo marketplace: search, seller lookup, offers, orders, draft listings. All human-approved. | Remote · HTTPLive check: ✓ handshake |
| REST Countries MCP by UnClickCountry data: flags, currencies, languages, regions, capitals, and more. No API key. By UnClick. | Local · stdio |
| Resy MCPResy reservation management - search, book, cancel, favorites, and Priority Notify for Claude. | Local · stdio |