fetcher.sh MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FETCHER_API_KEY | No | Prepaid bby_live_... API key used for authenticating to the fetcher.sh API | |
| FETCHER_SERVICE | No | Restrict the server to one service slug (e.g., twitter, youtube, reddit) | |
| FETCHER_API_BASE | No | Override the API origin (default https://fetcher.sh) | https://fetcher.sh |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_endpointsA | 🎯 START HERE. Free. Search fetcher.sh's web-data endpoints (Twitter/X, YouTube, TikTok, Instagram, Reddit, Google Search, Google Maps, Google News, Google Play, App Store, Yelp) by keyword and/or service. Returns paths, descriptions and per-call prices. Then call describe_endpoint, then fetch_data. |
| describe_endpointA | Free. Show the full call signature for one endpoint: required and optional parameters, allowed values, price, and response shape. Call this before fetch_data if you are unsure about parameters. |
| fetch_dataA | Paid. Fetch live data from any fetcher.sh endpoint. Pass the endpoint path plus its parameters (path and query parameters together in |
| check_balanceA | Free. Show the remaining credit balance for FETCHER_API_KEY. Call this before a long run of paid requests. |
| topup_creditsA | Prepaid credits are bought on the web, not over stdio. Returns the top-up URL (minimum $1). After topping up, put the bby_live_… key in FETCHER_API_KEY. |
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 5 tools
Each tool has a clearly distinct role: billing, discovery, documentation, data fetching, and balance checking. There is no overlap or ambiguity about which tool to select for a given step.
All tool names follow a consistent verb_noun snake_case pattern (topup_credits, search_endpoints, describe_endpoint, fetch_data, check_balance). The naming is predictable and easy to infer.
Five tools is well-scoped for this server's purpose: providing access to fetcher.sh's API with discovery, documentation, execution, and account management. Each tool earns its place without redundancy.
The tool set covers the full user workflow: find endpoints, inspect their signatures, fetch data, check balance, and top up credits. There are no obvious dead ends or missing operations for the stated domain.