fetcher.sh — web data for agents

sh.fetcherPublished by fetcher.shOfficial publisherv1.0.0Updated Oct 24, 2026

111 web-data endpoints across 11 services. Pay per call in USDC via x402.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP endpoint, fetcher.sh, that gives an assistant access to 111 web-data endpoints across 11 services, billed per call in USDC via x402.

What you can do
Access 111 web-data endpoints grouped into 11 services, exposed to the assistant as tools (individual tools are not listed in the manifest). Retrieve web data on demand through a single remote endpoint. Pay for each call in USDC through the x402 payment scheme.
When to use it
When an assistant needs web data from many different sources and you prefer a single hosted endpoint over installing local servers, and you are prepared to pay per call in USDC.
Requirements
A remote MCP connection to the fetcher.sh endpoint over streamable HTTP. No packages, environment variables or headers are declared. A USDC-capable x402 payment setup is needed, since calls are billed per use.
Before you install
Every call is paid in USDC via x402, so usage spends real funds; set limits before connecting. The manifest declares no authentication, so payment and access handling should be confirmed with the provider. Data is fetched from third-party web sources.

Installation

In SourceWeft

  1. Open fetcher.sh — web data for agents in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/sh.fetcher%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "fetcher-sh-web-data-for-agents": {
      "type": "http",
      "url": "https://fetcher.sh/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.