fetcher.sh — web data for agents
REMOTE · FETCHER.SH · SCANNED SEP 20
111 web-data endpoints across 11 services. Pay per call in USDC via x402.
Available components
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. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the fetcher.sh — web data for agents MCP server?
fetcher.sh — web data for agents is a hosted endpoint at https://fetcher.sh/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.
remote · fetcher.sh
claude mcp add --transport http sh-fetcher-mcp 'https://fetcher.sh/mcp'
{
"mcpServers": {
"sh-fetcher-mcp": {
"url": "https://fetcher.sh/mcp"
}
}
} {
"servers": {
"sh-fetcher-mcp": {
"type": "http",
"url": "https://fetcher.sh/mcp"
}
}
} [mcp_servers.sh-fetcher-mcp] url = "https://fetcher.sh/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sh-fetcher-mcp": {
"type": "remote",
"url": "https://fetcher.sh/mcp",
"enabled": true
}
}
} openclaw mcp add sh-fetcher-mcp --url 'https://fetcher.sh/mcp' --transport streamable-http
mcp_servers:
sh-fetcher-mcp:
url: "https://fetcher.sh/mcp" {
"McpServers": {
"sh-fetcher-mcp": {
"Transport": "http",
"Url": "https://fetcher.sh/mcp"
}
}
} assistant mcp add sh-fetcher-mcp -t streamable-http -u 'https://fetcher.sh/mcp'
{
"mcpServers": {
"sh-fetcher-mcp": {
"type": "http",
"url": "https://fetcher.sh/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Sept 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- DNSSEC: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 1 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Aug 26 73
- Tool “fetch_data” rewrote its description, which is the text the model reads security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://fetcher.sh/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fetcher.sh | CN=WE1,O=Google Trust Services,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6c47c91c7f5e5d270e17e5e51ff68948 |
| SANs: fetcher.sh | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of fetcher.sh. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 55297 | 8 | Verified |
| fetcher.sh. | present | 2371 | 13 | Verified |
| fetcher.sh. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 308 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fetcher.sh/mcp | Redirected | 308 | https://mcp.fetcher.sh/ |
| http (plaintext) | http://fetcher.sh/mcp | HTTPS enforced | 301 | https://fetcher.sh/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
appstore_apps ~75
Paid ($0.003). Apps — App Store. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional. |
| lang | string | – | Optional. |
| page | string | – | Optional. |
| term | string | yes | Required. |
No output schema declared.
No examples provided.
check_balance ~37
Free. Show the remaining credit balance for the API key sent in this connection's Authorization header. Call this before a long run of paid requests.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
describe_endpoint ~58
Free. Show the full call signature for one endpoint: required and optional parameters, allowed values, price, and response shape.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Endpoint path, e.g. /api/twitter/search or /api/twitter/handle/{handle} |
No output schema declared.
No examples provided.
fetch_data ~138
Paid. Fetch live data from any fetcher.sh endpoint. Pass the endpoint path plus its parameters (path and query parameters together in `params`). Priced per call in USDC on Base, Monad or Solana: pay with x402, or send an Authorization: Bearer bby_live_... header to spend prepaid credits. Call describe_endpoint first if unsure about parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | – | All parameters for the endpoint, path and query alike, e.g. { query: 'x402', sort: 'Latest' } |
| path | string | yes | Endpoint path from search_endpoints, e.g. /api/twitter/search |
No output schema declared.
No examples provided.
google_maps_place_search ~103
Paid ($0.005). Place search — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | – | Optional. |
| languageCode | string | – | Optional. |
| latitude | string | – | Optional. |
| longitude | string | – | Optional. |
| offset | string | – | Optional. |
| query | string | yes | Required. |
| zoom | string | – | Optional. |
No output schema declared.
No examples provided.
google_news_search ~60
Paid ($0.005). Search — Google News. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | Required. |
| languageCode | string | yes | Required. |
No output schema declared.
No examples provided.
google_search ~105
Paid ($0.005). Search — Google Search. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| count | string | – | Optional. One of: 10. |
| country | string | – | Optional. |
| hl | string | – | Optional. |
| noEncode | string | – | Optional. |
| page | string | – | Optional. |
| query | string | yes | Required. |
| safe | string | – | Optional. |
No output schema declared.
No examples provided.
googleplay_apps ~84
Paid ($0.003). Apps — Google Play. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional. |
| lang | string | – | Optional. |
| price | string | – | Optional. One of: all, free, paid. |
| search | string | yes | Required. |
No output schema declared.
No examples provided.
instagram_user_handle ~54
Paid ($0.004). User handle — Instagram. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Required. Path parameter. |
No output schema declared.
No examples provided.
reddit_search_post ~80
Paid ($0.002). Search post — Reddit. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| keyword | string | yes | Required. |
| sort | string | – | Optional. One of: relevance, hot, new, top, comments. |
No output schema declared.
No examples provided.
search_endpoints ~105
Free. Search fetcher.sh's web-data endpoints (Twitter/X, YouTube, TikTok, Instagram, Reddit, Google, Google Maps, Google News, Google Play, App Store, Yelp) by keyword and/or service. Returns paths, descriptions and per-call prices. Start here.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Keywords, e.g. 'twitter followers' or 'reviews' |
| service | string | – | Restrict to one service slug, e.g. 'twitter' |
No output schema declared.
No examples provided.
tiktok_post_search ~132
Paid ($0.004). Post search — TikTok. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| dateRange | string | – | Optional. One of: ALL_TIME, YESTERDAY, THIS_WEEK, THIS_MONTH, LAST_THREE_MONTHS, LAST_SIX_MONTHS. |
| keyword | string | yes | Required. |
| region | string | – | Optional. |
| sortType | string | – | Optional. One of: RELEVANCE, MOST_LIKED, DATE_POSTED. |
No output schema declared.
No examples provided.
topup_credits ~138
Paid (the amount you choose, minimum $1). Buy prepaid credits with x402 so later calls skip the per-call payment round trip. With an Authorization: Bearer bby_live_... header on this connection it recharges that key. Without one, the paying wallet becomes the account and a new API key is minted and returned once — store it as a secret, it cannot be recovered.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to add, in USD. Minimum 1. |
| rotate | boolean | – | Mint a replacement key for the paying wallet, invalidating the old one immediately. Only valid when no Authorization header is sent. |
No output schema declared.
No examples provided.
twitter_search ~74
Paid ($0.005). Search — Twitter / X. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| query | string | yes | Required. |
| sort | string | – | Optional. One of: Latest, Top. |
No output schema declared.
No examples provided.
yelp_search ~85
Paid ($0.003). Search — Yelp. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | Required. |
| page | string | – | Optional. |
| query | string | yes | Required. |
| sortBy | string | – | Optional. One of: recommended, rating, reviewCount. |
No output schema declared.
No examples provided.
youtube_search_video ~178
Paid ($0.005). Search video — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| duration | string | – | Optional. One of: short, medium, long. |
| features | string | – | Optional. One of: hd, subtitles, creative_commons, 3d, live, purchased, 4k, 360, location, hdr, vr180. |
| geo | string | – | Optional. |
| lang | string | – | Optional. |
| query | string | yes | Required. |
| sortBy | string | – | Optional. One of: relevance, rating, upload_date, view_count. |
| uploadDate | string | – | Optional. One of: hour, today, week, month, year. |
No output schema declared.
No examples provided.
What is the fetcher.sh — web data for agents MCP server?
fetcher.sh — web data for agents is an MCP server listed in the public MCP registry as sh.fetcher/mcp. 111 web-data endpoints across 11 services. Pay per call in USDC via x402. This page covers its hosted endpoint (https://fetcher.sh/mcp).
Is the fetcher.sh — web data for agents MCP server safe to use?
fetcher.sh — web data for agents scores 24 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 fetcher.sh — web data for agents MCP server expose?
fetcher.sh — web data for agents exposes 16 tools: search_endpoints, describe_endpoint, fetch_data, check_balance, topup_credits, and 11 more. Their descriptions and schemas cost roughly 1,506 tokens of context every time the server is loaded.
Does the fetcher.sh — web data for agents MCP server require authentication?
No. We connected to fetcher.sh — web data for agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the fetcher.sh — web data for agents MCP server still maintained?
fetcher.sh — web data for agents is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.