io.github.CloudCorpRecords/deepsearch
NPM · @RENETURCIOS/DEEPSEARCH · 2 COMPONENTS
Neural web search, code context, and page crawling through the Exa API.
Available components
Last scanned (20 hours ago)
Scores higher than 32% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 213 tokens (~71/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 49
First indexed and scored.
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 4 Nov 2026 · Analysed npm/@reneturcios/deepsearch@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
crawling_exa ~74
Fetch the full text content of a specific web page by URL.
| Name | Type | Req | Description |
|---|---|---|---|
| tokensNum | number | – | Optional token budget for the returned page text, clamped to 1000-50000; defaults to 5000. |
| url | string | yes | The URL of the web page to fetch the full text content of. |
No output schema declared.
No examples provided.
get_code_context_exa ~78
Find code examples and documentation for a programming question and return them as context.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The programming question or code search query to find examples and documentation for. |
| tokensNum | number | – | Optional token budget for the returned code context, clamped to 1000-50000; defaults to 5000. |
No output schema declared.
No examples provided.
web_search_exa ~61
Search the web with Exa and return relevant pages with their text content.
| Name | Type | Req | Description |
|---|---|---|---|
| numResults | number | – | Optional number of search results to return; defaults to 8. |
| query | string | yes | The web search query to run with Exa. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/deepsearch MCP server?
io.github.CloudCorpRecords/deepsearch runs locally as an npm package, launched with npx -y @reneturcios/deepsearch. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/deepsearch
claude mcp add cloudcorprecords-deepsearch -- npx -y @reneturcios/deepsearch
What is the io.github.CloudCorpRecords/deepsearch MCP server?
io.github.CloudCorpRecords/deepsearch is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/deepsearch. Neural web search, code context, and page crawling through the Exa API. This page covers its npm package (@reneturcios/deepsearch).
Is the io.github.CloudCorpRecords/deepsearch MCP server safe to use?
io.github.CloudCorpRecords/deepsearch scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/deepsearch MCP server expose?
io.github.CloudCorpRecords/deepsearch exposes 3 tools: web_search_exa, get_code_context_exa, crawling_exa. Their descriptions and schemas cost roughly 213 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/deepsearch MCP server still maintained?
io.github.CloudCorpRecords/deepsearch is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.CloudCorpRecords/deepsearch MCP server under?
io.github.CloudCorpRecords/deepsearch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.