# Fetch Router (npm · fetchrouter-mcp)

Verified web fetch for agents: detects blocks and empty JS pages, falls back, bills only on success.

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

## Components

- remote · `fetchrouter.dev`: 73/100, [markdown](https://verifymcp.io/servers/dev-fetchrouter-fetchrouter-mcp/fetchrouter.md), [page](https://verifymcp.io/servers/dev-fetchrouter-fetchrouter-mcp/fetchrouter)
- npm · `fetchrouter-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/dev-fetchrouter-fetchrouter-mcp/fetchrouter-mcp.md), [page](https://verifymcp.io/servers/dev-fetchrouter-fetchrouter-mcp/fetchrouter-mcp)

## Channel facts

- Registry: `npm`
- Package: `fetchrouter-mcp`
- Version: `0.1.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**: 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.
  - 30 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 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 288 tokens (~144/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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.

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

## Install

### How do I install the Fetch Router MCP server?

Fetch Router runs locally as an npm package, launched with npx -y fetchrouter-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 dev-fetchrouter-fetchrouter-mcp -- npx -y fetchrouter-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-fetchrouter-fetchrouter-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "fetchrouter-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-fetchrouter-fetchrouter-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "fetchrouter-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-fetchrouter-fetchrouter-mcp -- npx -y fetchrouter-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-fetchrouter-fetchrouter-mcp --command npx --arg -y --arg fetchrouter-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-fetchrouter-fetchrouter-mcp:
    command: "npx"
    args: ["-y", "fetchrouter-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-fetchrouter-fetchrouter-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "fetchrouter-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-fetchrouter-fetchrouter-mcp -t stdio -c npx -a -y fetchrouter-mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-fetchrouter-fetchrouter-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "fetchrouter-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-04 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 56)

First indexed and scored.

## MCP tools (2)

### `fetch_page` (~214 tokens)

Fetch a web page (verified)

Fetch a public URL and get its content only if it really loaded. Checks for block pages, CAPTCHAs, login walls and empty JavaScript shells, and retries through other routes (including a headless browser) automatically. Billed only on success. Returns markdown by default. If ok is false, the reason says why (e.g. blocked:cloudflare, http_404, expect_text_missing): don't retry the same URL with the same settings.

Input parameters:

- `expect_selector` (string): CSS selector that must match
- `expect_text` (string): Text that must appear on the page for it to count as loaded, e.g. a product name
- `max_cost` (integer): Most credits to pay: 1 static only, 2 (default) allows a browser, 10-25 allows premium unblocking
- `mode` (string): markdown (default, main content), html (raw page), rendered (always use a browser)
- `url` (string, required): Public http(s) URL

### `domain_reliability` (~74 tokens)

Which fetch routes work for a site

Pass rates per route (plain HTTP, browser, providers) for a domain over the last 30 days, from real verified fetches. Use it to choose mode/max_cost before fetching a hard site. Free, no key needed.

Input parameters:

- `domain` (string, required): Domain or URL, e.g. zillow.com

## Diagnostics

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

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 56

## Common questions

### What is the Fetch Router MCP server?

Fetch Router is an MCP server listed in the public MCP registry as dev.fetchrouter/fetchrouter-mcp. Verified web fetch for agents: detects blocks and empty JS pages, falls back, bills only on success. This page covers its npm package (fetchrouter-mcp).

### Is the Fetch Router MCP server safe to use?

Fetch Router scores 71 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. 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 Fetch Router MCP server expose?

Fetch Router exposes 2 tools: fetch_page, domain_reliability. Their descriptions and schemas cost roughly 288 tokens of context every time the server is loaded.

### Is the Fetch Router MCP server still maintained?

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

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