fetchrouter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FETCHROUTER_API_KEY | Yes | Your Fetch Router API key. Required for the local stdio server. | |
| FETCHROUTER_BASE_URL | No | The Fetch Router base URL. | https://fetchrouter.dev |
| FETCHROUTER_MAX_CHARS | No | Maximum number of characters returned; longer pages are truncated. | 60000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_pageA | 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. |
| domain_reliabilityA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve clearly different roles: fetch_page performs an actual fetch, while domain_reliability reports historical route performance for a domain. An agent can easily choose between acting and planning/choosing settings.
Both names are snake_case and readable, but fetch_page follows a verb_noun pattern while domain_reliability follows noun_noun. This is a minor deviation rather than an inconsistency.
Two tools is thin even for a narrow fetch-routing server. Each tool is meaningful, but the surface could reasonably include batch fetching or provider listing without bloating.
The core lifecycle is covered: fetch a URL and inspect route reliability to choose settings. Minor gaps exist, such as batch fetching or explicit route/provider inspection, but agents can work around them.