# Decodo (npm · @pipeworx/mcp-decodo)

Decodo MCP — wraps the Decodo Web Scraping API (decodo.com, formerly Smartproxy). Rotating…

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-decodo/decodo-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-decodo/decodo-mcp)
- npm · `@pipeworx/mcp-decodo`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-decodo/pipeworx-mcp-decodo.md), [page](https://verifymcp.io/servers/pipeworx-io-decodo/pipeworx-mcp-decodo)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-decodo`
- Version: `0.2.1`
- 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**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-decodo).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 815 tokens (~271/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 3 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 Decodo MCP server?

Decodo runs locally as an npm package, launched with npx -y @pipeworx/mcp-decodo. 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 pipeworx-io-decodo -- npx -y @pipeworx/mcp-decodo
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-decodo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-decodo"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-decodo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-decodo"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-decodo -- npx -y @pipeworx/mcp-decodo
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-decodo --command npx --arg -y --arg @pipeworx/mcp-decodo
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-decodo:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-decodo"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-decodo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-decodo"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-decodo -t stdio -c npx -a -y @pipeworx/mcp-decodo
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-decodo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-decodo"
      ]
    }
  }
}
```

## 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 82, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-04 (score 81, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-03 (score 81, +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-01 (score 80, +2)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `decodo_scrape` (~272 tokens)

Scrape any web page through Decodo (formerly Smartproxy) rotating proxies and return its content. Handles anti-bot pages; use render_js:true for JavaScript-heavy sites (headless-browser rendering) and markdown:true for clean LLM-ready markdown instead of raw HTML. BYOK — _apiKey is your Decodo Web Scraping API "username:password" credentials. Example: decodo_scrape({ url: "https://example.com", render_js: true, _apiKey: "user:pass" })

Input parameters:

- `_apiKey` (string, required): Decodo Web Scraping API credentials as "username:password" (from the dashboard at https://dashboard.decodo.com — free plan available).
- `geo` (string): Proxy exit location as a location name, e.g. "United States", "Germany", "Japan". Default: randomized.
- `markdown` (boolean): Return the page as clean markdown instead of raw HTML (ideal for feeding an LLM). Default false.
- `render_js` (boolean): Render the page in a headless browser (executes JavaScript) before returning content. Default false (faster raw fetch of static pages).
- `url` (string, required): The absolute URL of the page to scrape, e.g. "https://example.com/products"

### `decodo_google_search` (~233 tokens)

Google search results scraping via Decodo (formerly Smartproxy) — runs a Google search through rotating proxies and returns structured organic results (position, title, url, snippet) plus related searches when parsing succeeds. BYOK — _apiKey is your Decodo Web Scraping API "username:password" credentials. Example: decodo_google_search({ query: "best running shoes 2026", geo: "United States", _apiKey: "user:pass" })

Input parameters:

- `_apiKey` (string, required): Decodo Web Scraping API credentials as "username:password" (from https://dashboard.decodo.com).
- `geo` (string): Location name to geotarget the search, e.g. "United States", "United Kingdom". Optional.
- `locale` (string): Language code for the Google interface, e.g. "en-US", "de-DE". Optional.
- `page_count` (number): Number of result pages to retrieve (1-10). Default 1.
- `query` (string, required): The Google search query, e.g. "best running shoes 2026"

### `decodo_amazon_product` (~258 tokens)

Get structured Amazon product data via Decodo (formerly Smartproxy) — title, pricing, rating, reviews, images, availability — parsed into JSON. Pass either a full Amazon product URL or an ASIN. BYOK — _apiKey is your Decodo Web Scraping API "username:password" credentials. Example: decodo_amazon_product({ asin: "B09H74FXNW", _apiKey: "user:pass" })

Input parameters:

- `_apiKey` (string, required): Decodo Web Scraping API credentials as "username:password" (from https://dashboard.decodo.com).
- `asin` (string): Amazon ASIN (product identifier), e.g. "B09H74FXNW". Used to build the product URL when `url` is omitted.
- `domain` (string): Amazon marketplace domain used with `asin`, e.g. "com" (default), "co.uk", "de".
- `geo` (string): Proxy exit location as a location name, e.g. "United States". Optional.
- `url` (string): Full Amazon product page URL, e.g. "https://www.amazon.com/dp/B09H74FXNW". Provide this or `asin`.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-decodo/pipeworx-mcp-decodo#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Decodo MCP server?

Decodo is an MCP server listed in the public MCP registry as io.github.pipeworx-io/decodo. Decodo MCP, wraps the Decodo Web Scraping API (decodo.com, formerly Smartproxy). Rotating… This page covers its npm package (@pipeworx/mcp-decodo).

### Is the Decodo MCP server safe to use?

Decodo scores 82 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 Decodo MCP server expose?

Decodo exposes 3 tools: decodo_scrape, decodo_google_search, decodo_amazon_product. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.

### Is the Decodo MCP server still maintained?

Decodo 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 Decodo MCP server under?

Decodo 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/@pipeworx/mcp-decodo
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-decodo
- Repository: https://github.com/pipeworx-io/mcp-decodo
- Website: https://pipeworx.io/packs/decodo
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-decodo/pipeworx-mcp-decodo.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-decodo/pipeworx-mcp-decodo.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-decodo/pipeworx-mcp-decodo