4 findingsStatic scanned
Lets your coding agent hand coding, review and ops tasks to CodeZaiku on local or hosted models.
2.2k installs/moApache-2.0
Researchzosho MCP
wyrdsekai · MCP server
Researchzosho MCP launches ResearchZosho, a research librarian, as an MCP server so an AI client can use its deep research with citations and memory. The package holds no copy of the program: it finds an installed ResearchZosho or downloads the matching release from GitHub. A library folder is created on a machine that has none, and a setup command names the model server, installs the service and brings local web pages with it.
Written by ooruby from the README of @wyrdsekai/researchzosho-mcp 0.5.5.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your agent gets a research librarian that works from a library folder on your machine and cites what it finds.
What you could do with it
- Ask your agent for deep research on a topic and get an answer with citations.
- Let your agent work from a research library kept in a folder on your machine.
- Run the setup step to name the model server it should use and install it as a service.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (bin/index.js:22)
- synchronous shell execution (bin/index.js:88)
- synchronous shell execution (bin/index.js:149)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
- Licence and provenance
- finding
- no LICENCE file at the root (.)
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Deep research MCP server with citations and memory. Starts ResearchZosho for Claude Code, Codex, Gemini CLI or any MCP client that can run npx, and fetches the release if it is not installed.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.5.5, the file with digest sha512-+40YohDAfrQj6oSRU7eXL/sVZQs8+xIkIf9vU5El1w1JX2hm1Oxn3eVhgkRuxm1fhTK0ctKhIoM51ec5A4TG4Q==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"researchzosho-mcp": {
"command": "npx",
"args": [
"-y",
"@wyrdsekai/researchzosho-mcp@0.5.5"
]
}
}
}Or run it directly.
npx -y @wyrdsekai/researchzosho-mcp@0.5.5Pinned to 0.5.5, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @wyrdsekai/researchzosho-mcp
- Version read
- 0.5.5
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/wyrdsekai/researchzosho
- Commit
- b09fb0f71eaf
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/wyrdsekai-researchzosho-mcp)About this listing
- Kind
- MCP server
- Category
- Research
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-08
More from wyrdsekai
See the storefrontSimilar MCP servers
All MCP servers1 findingStatic scanned
Lets your assistant reason through a problem in numbered steps, revising and branching as it goes.
484.3k installs/moSEE LICENSE IN LICENSE
1 findingStatic scanned
Lets your agent search the web and recent news through DuckDuckGo, filtered by region and time.
147.5k installs/moMIT
Clean scanStatic scanned
Lets your agent search the web, extract page content, map a website's structure and crawl sites.
117.6k installs/moMIT
Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.