Koskamo

Fetch Router MCP

A verified web fetch API for AI agents that routes requests through plain HTTP, headless browsers, and premium unblocking providers. It verifies page content to ensure it is not blocked or empty, falls back automatically, and bills only for successful fetches.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Fetch Router MCP logo, by One + Done LLCVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-02Operated by One + Done LLC
You need:Get a key on the home page (500 free credits)
MCP endpoint (Streamable HTTP)
https://fetchrouter.dev/mcp
Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 2 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to fetchrouter.dev ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Fetch verified web content for AI agents
  • Detect and bypass CAPTCHAs and bot protection
  • Check domain reliability and route pass rates

Source and maintenance

Vendor evidenceRegistry 0.1.0
Maintenance checked

Protocol and capabilities

Server
fetchrouter 0.1.1
MCP protocol negotiated in check
2025-06-18
Tools
2 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Tools

2 advertised

fetch_page — Fetch a web page (verified)
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

fetch_page input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Public http(s) URL"
    },
    "mode": {
      "enum": [
        "markdown",
        "html",
        "rendered"
      ],
      "type": "string",
      "description": "markdown (default, main content), html (raw page), rendered (always use a browser)"
    },
    "max_cost": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Most credits to pay: 1 static only, 5 (default) allows a browser, 10-25 allows premium unblocking"
    },
    "expect_text": {
      "type": "string",
      "description": "Text that must appear on the page for it to count as loaded, e.g. a product name"
    },
    "expect_selector": {
      "type": "string",
      "description": "CSS selector that must match"
    }
  }
}
fetch_page annotations
{
  "readOnlyHint": true,
  "openWorldHint": true
}
domain_reliability — Which fetch routes work for a site
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

domain_reliability input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain or URL, e.g. zillow.com"
    }
  }
}
domain_reliability annotations
{
  "readOnlyHint": true,
  "openWorldHint": true
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-02: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
629 ms
95th percentile latency
629 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 629 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http fetch-router-mcp https://fetchrouter.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add fetch-router-mcp --url https://fetchrouter.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable fetch-router-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "fetch-router-mcp": {
      "url": "https://fetchrouter.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "fetch-router-mcp": {
      "type": "streamableHttp",
      "url": "https://fetchrouter.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start fetch-router-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "fetch-router-mcp": {
      "type": "http",
      "url": "https://fetchrouter.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http fetch-router-mcp https://fetchrouter.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "fetch-router-mcp": {
      "url": "https://fetchrouter.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "fetch-router-mcp": {
      "serverUrl": "https://fetchrouter.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Fetch Router MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Fetch Router MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing