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

Bing search results as JSON: SERPs with the ad block and Copilot answer, geo and market targeting.

- Trust score: 72/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/bingdata`
- 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-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 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 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 504 tokens (~504/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 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/bingdata MCP server?

io.github.CloudCorpRecords/bingdata runs locally as an npm package, launched with npx -y @reneturcios/bingdata mcp. 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-bingdata -- npx -y @reneturcios/bingdata mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-20 (score 72, +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.

### 2026-11-19 (score 71, +4)

- [functional improvement] Stability: unverified → 0.30

### 2026-11-11 (score 67, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-10 (score 67)

First indexed and scored.

## MCP tools (1)

### `hasdata_bing_serp_getSearchResults` (~504 tokens)

bing_serp: GET /

Get Bing Search Results

Fetches Bing SERPs for a query with geo targeting (location/lat/lon), market (mkt), country (cc), safesearch (off/moderate/strict), interface language (setLang), time/custom filters, device type, and pagination (first offset). Returns organic results (title, url, snippet, displayed url, position) and related searches. Use for SEO rank tracking, SERP feature monitoring, Bing-specific visibility audits, and training/eval data for search agents.

Input parameters:

- `cc` (string): The two-letter country code for the country to search from.
- `deviceType` (string): Specify the device type for the search.
- `filters` (string): Allows applying various filters to narrow search results, including date-based options:   - `ex1:"ez1"` – past 24 hours   - `ex1:"ez2"` – past week   - `ex1:"ez3"` – past month For complex filters,…
- `first` (number): This parameter specifies the number of search results to skip and is used for implementing pagination. For example, a value of 1 (default) indicates the first page of results, 11 refers to the second…
- `lat` (string): GPS latitude for the search origin.
- `location` (string): Defines the search’s origin location as free text (e.g. `Austin, Texas`). It is resolved to coordinates to localize the results. For realistic results, set location at the city level. If both `lat` a…
- `lon` (string): GPS longitude for the search origin.
- `mkt` (string): The two-letter country code for the country to search from.
- `q` (string, required): Specify the search term for which you want to scrape the SERP.
- `safeSearch` (string): Adult Content Filtering option.
- `setLang` (string): The language of the user interface and preferred result language. Accepts a two-letter language code (e.g. `en`, `de`) or a locale/script variant (e.g. `en-gb`, `zh-hans`, `pt-br`).

## Diagnostics

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

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 67
- 2026-11-12: 67
- 2026-11-11: 67
- 2026-11-10: 67

## Common questions

### What is the io.github.CloudCorpRecords/bingdata MCP server?

io.github.CloudCorpRecords/bingdata is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/bingdata. Bing search results as JSON: SERPs with the ad block and Copilot answer, geo and market targeting. This page covers its npm package (@reneturcios/bingdata).

### Is the io.github.CloudCorpRecords/bingdata MCP server safe to use?

io.github.CloudCorpRecords/bingdata scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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/bingdata MCP server expose?

io.github.CloudCorpRecords/bingdata exposes 1 tool: hasdata_bing_serp_getSearchResults. Their descriptions and schemas cost roughly 504 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/bingdata MCP server still maintained?

io.github.CloudCorpRecords/bingdata is still listed as active in the MCP registry. We last reached this channel on 21 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/bingdata MCP server under?

io.github.CloudCorpRecords/bingdata declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/bingdata MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/bingdata, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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