4fetch

io.github.amit755Published by GitHub account amit755v1.0.0Updated Oct 24, 2026

Fetch a URL and get clean Markdown with metadata. No API key required; rate-limited per IP.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that fetches a URL and returns clean Markdown with metadata, with no API key required.

What you can do
Fetch a web page by URL and receive its content converted to clean Markdown, along with metadata about the page. No API key is needed; requests are rate-limited per IP address. The manifest lists no individual tools, so the exact tool names and parameters are not documented here.
When to use it
Useful when an assistant needs readable page content rather than raw HTML, for example to read an article or documentation page and work with its text. It is a lightweight option when you do not want to manage API credentials.
Requirements
A remote MCP endpoint at api.4fetch.com over streamable HTTP; no local runtime, package, account, API key, environment variable or header is declared. Network access to the endpoint is required.
Before you install
Fetched URLs are sent to a third-party service, so avoid passing private or internal addresses. Requests are rate-limited per IP, which may affect heavy use. No authentication is declared, so do not assume requests are private or attributable.

Installation

In SourceWeft

  1. Open 4fetch 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/io.github.amit755%2F4fetch/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": {
    "4fetch": {
      "type": "http",
      "url": "https://api.4fetch.com/mcp/v1/fetch"
    }
  }
}

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.