fetchira
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Quota-aware router over free web-search/scrape providers. Tools: search, read, deep_research, browser, create_image, usage. Pass provider to restrict routing to a specific backend (quota and retry limits still apply); otherwise providers are tried in the user's priority order with automatic failover.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browserB | Load a URL in a headless browser (hyperbrowser, browserless, steel) and return the page as markdown. |
| create_imageA | Generate or edit an image via a logged-in web session. For a new image pass |
| deep_researchA | Deep research over multiple sources (parallel, exa, tavily, tinyfish, linkup, you, gemini_web, grok_web, chatgpt_web); may take minutes. gemini_web and chatgpt_web first return a research PLAN plus a |
| readA | Read a URL and return its main content as clean markdown; auto-escalates to a headless browser when the plain read comes back empty. Provider-specific extras via |
| searchA | Web search across quota-aware providers. API providers return ranked title/url/snippet results; web providers (gemini_web, grok_web, chatgpt_web) return a synthesized answer with sources and a |
| usageA | Show remaining free quota per account and provider for the current period, plus each account's assigned proxy. For logged-in web sessions (grok/gemini/chatgpt) also includes live per-tier limits and the selectable model/mode catalog with thinking levels — a locked mode (e.g. grok Expert/Heavy on a lapsed sub) reads 0/0. Pass |
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 6 tools
Most tools target clearly different actions (search, deep_research, create_image, usage), but browser and read overlap heavily since both load a URL and return markdown. The read description's note that it auto-escalates to browser helps, but an agent could still reasonably pick either for a simple fetch.
All names are lowercase snake_case and readable, but conventions are mixed: bare verbs (read, search), bare nouns (browser, usage), a verb_noun (create_image), and a compound (deep_research). No single predictable pattern guides naming.
Six tools is well within a healthy range and each earns its place: fetching, searching, deep research, image generation, and quota inspection. No obvious filler or missing companion tool.
The surface covers the core domain well: URL fetch via read/browser, search, multi-source research, image generation/editing, and quota introspection. Minor gaps include no explicit batch/multi-URL crawl tool (only available via provider-specific modes) and no dedicated session or result management beyond opaque tokens.