Zearch
NPM · @ZEARCHCOMPUTER/MCP
Research with answers you can check: every paragraph verified against its cited source.
Available components
Last scanned (1 hour ago)
Scores higher than 95% of npm servers
Category Search and Retrieval
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to zearchcomputer/zearch-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 926 tokens (~115/item across 8 items; 6 tools + 2 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 Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
- Structured output schemas are declared (83% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 +33
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 92 functional
- First check of Schema quality: fail functional
- First check of Capabilities: pass functional
- First check of Tool coverage: 83 functional
- First check of Schema quality: good functional
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 npm/@zearchcomputer/mcp@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | zearchcomputer/zearch-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/zearchcomputer/zearch-mcp/.github/workflows/release.yml@refs/tags/v0.1.0 |
| Rekor log index | 3241870669 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:428d27f33b668ea33db3698641e48a108920a9d7306f1abf443acd69376e8228cc7cee1534155b4deec97386d4657e091a6505395763dbd1bd89c05cf |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_pricing Zearch pricing ~33
The public Zearch price list: credits per request type, plans and top-ups. Free; no API key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_run Get a research run ~63
Fetch one of your Zearch runs by id: its answer, sources, verification and status. Use it to check on a queued Reverse engineer run, or to reopen an earlier answer. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The run id returned by research or list_runs. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string|null | – | Markdown with [n] citations. |
| answer_type | string|null | – | verified: every paragraph passed Jev. excerpt: the selected source passage, because no draft could be supported. |
| created | number | – | – |
| error | string|null | – | – |
| followups | array | – | – |
| id | string | yes | – |
| mode | string | – | – |
| object | string | – | – |
| parent_id | string|null | – | – |
| query | string | – | – |
| sources | array | – | – |
| status | string | yes | pending, streaming, complete, error, interrupted or redacted. |
| timing_ms | number|null | – | – |
| updated | number | – | – |
| verification | – | – | – |
No examples provided.
get_wallet Credit balance ~73
Show the Zearch credit balance this key spends from: available and held credits, plan, credit lots and when they expire. Optionally include recent ledger entries. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| before | integer | – | next_before cursor from a previous call, for older entries. |
| include_entries | boolean | – | Also return recent ledger entries. |
| Name | Type | Req | Description |
|---|---|---|---|
| entries | object | – | – |
| wallet | object | yes | – |
No examples provided.
list_runs List research runs ~55
List your recent Zearch runs, newest first. The app and the API share one history. Free. Page with starting_after.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| starting_after | string | – | Run id from the previous page. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| has_more | boolean | – | – |
| object | string | – | – |
No examples provided.
research Research with checked answers ~327
Ask Zearch a question. Zearch searches the web (or reads the page or site you give it), Jev selects the passages that answer it, a writer drafts from those passages only, and Jev checks every paragraph against its cited source before the answer is returned. Unsupported paragraphs are cut; if nothing survives you get the selected source passage (answer_type "excerpt"). Modes and credits: standard (1, a direct answer in seconds), deep (5, a cited report from up to 8 sources), compare (2, a side-by-side comparison), scrape (1, what one public HTTPS page says; needs url), crawl (3, up to five pages of one site; needs url), reverse (10, static analysis of how an app, repo or site works; needs url, runs on a queue and can take minutes). A follow-up with parent_id that needs no new search costs 0.3. Errors are free. Returns the answer as Markdown with [n] citations, the sources with the exact excerpt Jev read, per-paragraph support scores, and suggested follow-ups.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | How much research to do. See the tool description for costs. |
| parent_id | string | – | Id of a previous run, to ask a follow-up in the same conversation. |
| query | string | yes | The question, in plain language. |
| url | string | – | Public HTTPS URL. Required for scrape, crawl and reverse; ignored otherwise. |
| use_notes | boolean | – | Also use the account's private Zearch notes and documents as evidence. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string|null | – | Markdown with [n] citations. |
| answer_type | string|null | – | verified: every paragraph passed Jev. excerpt: the selected source passage, because no draft could be supported. |
| created | number | – | – |
| error | string|null | – | – |
| followups | array | – | – |
| id | string | yes | – |
| mode | string | – | – |
| object | string | – | – |
| parent_id | string|null | – | – |
| query | string | – | – |
| sources | array | – | – |
| status | string | yes | pending, streaming, complete, error, interrupted or redacted. |
| timing_ms | number|null | – | – |
| updated | number | – | – |
| verification | – | – | – |
No examples provided.
verify Verify text against sources ~177
Check text against the sources it cites, paragraph by paragraph, with Jev (the same check Zearch runs on its own answers). Cite sources inline as [1], [2]… in the order you list them. Use it to gate output from your own model before a person sees it. Limits: text up to 8,000 characters; 1 to 8 sources of up to 20,000 characters each. Costs 1 credit, charged only when the check completes. Returns pass/fail per paragraph with support and attribution probabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | – | The question the text answers, if any. Improves the check. |
| sources | array | yes | Sources in citation order: the first is [1]. |
| text | string | yes | Markdown to check. Every paragraph should cite at least one source as [n]. |
| Name | Type | Req | Description |
|---|---|---|---|
| model | string|null | – | – |
| object | string | – | – |
| paragraphs | array | yes | – |
| passed | boolean | yes | True when every paragraph met the support threshold. |
| threshold | number | – | – |
No examples provided.
How do I install the Zearch MCP server?
Zearch runs locally as an npm package, launched with npx -y @zearchcomputer/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @zearchcomputer/mcp
claude mcp add zearchcomputer-zearch-mcp -- npx -y @zearchcomputer/mcp
What is the Zearch MCP server?
Zearch is an MCP server listed in the public MCP registry as io.github.zearchcomputer/zearch-mcp. Research with answers you can check: every paragraph verified against its cited source. This page covers its npm package (@zearchcomputer/mcp).
Is the Zearch MCP server safe to use?
Zearch scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Zearch MCP server expose?
Zearch exposes 6 tools: research, verify, get_run, list_runs, get_wallet, get_pricing. Their descriptions and schemas cost roughly 728 tokens of context every time the server is loaded.
Is the Zearch MCP server still maintained?
Zearch 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 Zearch MCP server under?
Zearch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.