io.github.CloudCorpRecords/researchsearch
NPM · @RENETURCIOS/RESEARCHSEARCH · 2 COMPONENTS
Web search, page extraction, crawling, and site mapping powered by the Tavily API.
Available components
Last scanned (21 hours ago)
Scores higher than 33% of npm servers
Category Web Scraping
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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 548 tokens (~137/item across 4 items; 4 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 2 Nov 26 +1
- Stability: unverified → 0.07 ▲ functional
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 64
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/researchsearch@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 →
tavily-crawl ~137
Crawl a website from a starting URL with Tavily, extracting content from the pages it visits.
| Name | Type | Req | Description |
|---|---|---|---|
| extract_depth | string | – | Extraction depth to use during the crawl: "basic" or "advanced". |
| instructions | string | – | Natural-language guidance for which pages to visit during the crawl. |
| limit | number | – | Maximum total number of pages to crawl. |
| max_breadth | number | – | Maximum number of links to follow per page or level during the crawl. |
| max_depth | number | – | Maximum depth of links to follow from the starting URL. |
| url | string | yes | The starting URL to crawl from. |
No output schema declared.
No examples provided.
tavily-extract ~90
Extract clean content from one or more web pages with Tavily.
| Name | Type | Req | Description |
|---|---|---|---|
| extract_depth | string | – | Extraction depth: "basic" or "advanced". |
| include_images | boolean | – | Whether to include images in the extracted content. |
| query | string | – | Query to focus the extraction on content relevant to it. |
| urls | array | yes | List of web page URLs to extract clean content from. |
No output schema declared.
No examples provided.
tavily-map ~119
Map a website's structure with Tavily, returning the URLs reachable from a starting page.
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | – | Natural-language guidance for which pages to include in the map. |
| limit | number | – | Maximum total number of URLs to return from the mapping. |
| max_breadth | number | – | Maximum number of links to follow per page or level during the mapping. |
| max_depth | number | – | Maximum depth of links to follow from the starting URL. |
| url | string | yes | The starting URL to map the site structure from. |
No output schema declared.
No examples provided.
tavily-search ~202
Search the web with Tavily and return ranked results, optionally with an AI-generated answer and raw page content.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Number of days back from today to search, for the news topic. |
| exclude_domains | array | – | List of domains to exclude from the results. |
| include_answer | boolean | – | Whether to include an AI-generated answer summarising the results. |
| include_domains | array | – | List of domains to restrict results to; only results from these domains are returned. |
| include_raw_content | boolean | – | Whether to include the cleaned raw page content for each result. |
| max_results | number | – | Maximum number of search results to return. |
| query | string | yes | The search query to run against the web. |
| search_depth | string | – | Search depth: "basic" or "advanced". Unset lets the service choose. |
| topic | string | – | Search topic: "general", "news", or "finance". |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/researchsearch MCP server?
io.github.CloudCorpRecords/researchsearch runs locally as an npm package, launched with npx -y @reneturcios/researchsearch. 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/researchsearch
claude mcp add cloudcorprecords-researchsearch -- npx -y @reneturcios/researchsearch
What is the io.github.CloudCorpRecords/researchsearch MCP server?
io.github.CloudCorpRecords/researchsearch is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/researchsearch. Web search, page extraction, crawling, and site mapping powered by the Tavily API. This page covers its npm package (@reneturcios/researchsearch).
Is the io.github.CloudCorpRecords/researchsearch MCP server safe to use?
io.github.CloudCorpRecords/researchsearch scores 65 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/researchsearch MCP server expose?
io.github.CloudCorpRecords/researchsearch exposes 4 tools: tavily-search, tavily-extract, tavily-crawl, tavily-map. Their descriptions and schemas cost roughly 548 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/researchsearch MCP server still maintained?
io.github.CloudCorpRecords/researchsearch 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/researchsearch MCP server under?
io.github.CloudCorpRecords/researchsearch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.