ResearchZosho
OCI · GHCR.IO/WYRDSEKAI/RESEARCHZOSHO · 2 COMPONENTS
Deep research assistant that checks its citations against the sources and keeps what it found.
Available components
Last scanned (10 hours ago)
Scores higher than 71% of OCI servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 14073 tokens (~287/item across 49 items; 49 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "library_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 49 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Package version: 0.6.1 → 0.6.8 functional
- 1 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.6.6 → 0.6.8 functional
- Package version: 0.6.6 → 0.6.7 functional
- 31 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 30 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Provenance: unverified → fail ▼ security
- Package version: 0.6.5 → 0.6.6 functional
- 26 Oct 26 +1
- Provenance: fail → unverified ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/wyrdsekai/researchzosho@0.6.8
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
library_who ~308
Family history: who, of the people the web shows under a name, is the person in the family. A name is shared, and only somebody in the family can say which entry is their relative. op=list: who waits for an answer. op=show: one person's entries, numbered, each with who they are, their pages, and what those pages say that the family's facts also say. op=answer: the family's word. op=tell: something said of the person, kept in those words for their search. op=find: look one person up now (about half a minute). The answer is the family's own word: show the entries and ask.
| Name | Type | Req | Description |
|---|---|---|---|
| is | string | – | For answer: the numbers of the entries who ARE the person, as "1" or "1,3" when two entries are the same person. |
| later | boolean | – | For answer: they cannot tell now; the question stays answered as unsure. |
| none | boolean | – | For answer: none of the entries is the person. |
| op | string | yes | list, show, answer, tell or find. |
| patron | object | – | Optional: who is asking — {did, name, runtime}. Anonymous when absent. |
| person | string | – | The person in the family, as the library writes the name. For show: empty takes the first who waits. |
| text | string | – | For tell: what was said of the person, as they said it. |
No output schema declared.
No examples provided.
How do I install the ResearchZosho MCP server?
ResearchZosho runs locally as a container image, launched with docker run --rm -i ghcr.io/wyrdsekai/researchzosho:0.6.8. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/wyrdsekai/researchzosho
claude mcp add wyrdsekai-researchzosho -- docker run --rm -i ghcr.io/wyrdsekai/researchzosho:0.6.8
What is the ResearchZosho MCP server?
ResearchZosho is an MCP server listed in the public MCP registry as io.github.Wyrdsekai/researchzosho. Deep research assistant that checks its citations against the sources and keeps what it found. This page covers its container image (ghcr.io/wyrdsekai/researchzosho).
Is the ResearchZosho MCP server safe to use?
ResearchZosho scores 48 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ResearchZosho MCP server expose?
ResearchZosho exposes 49 tools: library_ask, library_search, library_get, library_read, library_established, and 44 more. Their descriptions and schemas cost roughly 14,073 tokens of context every time the server is loaded.
Is the ResearchZosho MCP server still maintained?
ResearchZosho is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ResearchZosho MCP server under?
ResearchZosho declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.