# Fetch Router (remote · fetchrouter.dev)

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

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

## Components

- remote · `fetchrouter.dev`: 73/100 (this document), [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, [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

- Endpoint: `https://fetchrouter.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-04.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **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**: 7/100
  - Stability observed for 2 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 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.

## Install

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

Fetch Router is a hosted endpoint at https://fetchrouter.dev/mcp, so there is nothing to install locally. 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 --transport http dev-fetchrouter-fetchrouter-mcp 'https://fetchrouter.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-fetchrouter-fetchrouter-mcp": {
      "url": "https://fetchrouter.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-fetchrouter-fetchrouter-mcp": {
      "type": "http",
      "url": "https://fetchrouter.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-fetchrouter-fetchrouter-mcp]
url = "https://fetchrouter.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-fetchrouter-fetchrouter-mcp": {
      "type": "remote",
      "url": "https://fetchrouter.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-fetchrouter-fetchrouter-mcp --url 'https://fetchrouter.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-fetchrouter-fetchrouter-mcp:
    url: "https://fetchrouter.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-fetchrouter-fetchrouter-mcp": {
      "Transport": "http",
      "Url": "https://fetchrouter.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-fetchrouter-fetchrouter-mcp -t streamable-http -u 'https://fetchrouter.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-fetchrouter-fetchrouter-mcp": {
      "type": "http",
      "url": "https://fetchrouter.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-03 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “fetch_page” reworded the description of “max_cost”

### 2026-11-02 (score 72)

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: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-fetchrouter-fetchrouter-mcp/fetchrouter#diagnostics

## Score history

- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72

## 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 hosted endpoint (https://fetchrouter.dev/mcp).

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

Fetch Router scores 73 out of 100 on VerifyMCP. 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.

### Does the Fetch Router MCP server require authentication?

No. We connected to Fetch Router without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://fetchrouter.dev/mcp
- Authorisation metadata: https://fetchrouter.dev/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/JonnoGit/fetchrouter-mcp
- Website: https://fetchrouter.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-fetchrouter-fetchrouter-mcp/fetchrouter.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-fetchrouter-fetchrouter-mcp/fetchrouter.json
- HTML version of this page: https://verifymcp.io/servers/dev-fetchrouter-fetchrouter-mcp/fetchrouter