# io.github.CloudCorpRecords/researchsearch (npm · @reneturcios/researchsearch)

Web search, page extraction, crawling, and site mapping powered by the Tavily API.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/researchsearch`: 66/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-researchsearch/reneturcios-researchsearch.md), [page](https://verifymcp.io/servers/cloudcorprecords-researchsearch/reneturcios-researchsearch)
- oci · `ghcr.io/cloudcorprecords/researchsearch`: 42/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-researchsearch/ghcr-io-cloudcorprecords-researchsearch.md), [page](https://verifymcp.io/servers/cloudcorprecords-researchsearch/ghcr-io-cloudcorprecords-researchsearch)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/researchsearch`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add cloudcorprecords-researchsearch -- npx -y @reneturcios/researchsearch
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-researchsearch": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/researchsearch"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-researchsearch": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/researchsearch"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-researchsearch -- npx -y @reneturcios/researchsearch
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-researchsearch": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/researchsearch"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-researchsearch --command npx --arg -y --arg @reneturcios/researchsearch
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-researchsearch:
    command: "npx"
    args: ["-y", "@reneturcios/researchsearch"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-researchsearch": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/researchsearch"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-researchsearch -t stdio -c npx -a -y @reneturcios/researchsearch
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-researchsearch": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/researchsearch"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 65, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-11-01 (score 64, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-31 (score 64)

First indexed and scored.

## MCP tools (4)

### `tavily-search` (~202 tokens)

Search the web with Tavily and return ranked results, optionally with an AI-generated answer and raw page content.

Input parameters:

- `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, required): 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".

### `tavily-extract` (~90 tokens)

Extract clean content from one or more web pages with Tavily.

Input parameters:

- `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, required): List of web page URLs to extract clean content from.

### `tavily-crawl` (~137 tokens)

Crawl a website from a starting URL with Tavily, extracting content from the pages it visits.

Input parameters:

- `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, required): The starting URL to crawl from.

### `tavily-map` (~119 tokens)

Map a website's structure with Tavily, returning the URLs reachable from a starting page.

Input parameters:

- `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, required): The starting URL to map the site structure from.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-researchsearch/reneturcios-researchsearch#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 65
- 2026-11-03: 65
- 2026-11-02: 65
- 2026-11-01: 64
- 2026-10-31: 64

## Common questions

### 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 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 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 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.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/researchsearch
- Socket report: https://socket.dev/npm/package/@reneturcios/researchsearch
- Repository: https://github.com/CloudCorpRecords/researchsearch
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-researchsearch/reneturcios-researchsearch.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-researchsearch/reneturcios-researchsearch.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-researchsearch/reneturcios-researchsearch