Mcp Fetch

io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 24, 2026

SSRF-safe URL fetch for AI agents — clean markdown/text/HTML/JSON, plus guarded REST calls.

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

A local MCP server that lets an assistant fetch URLs safely, returning clean markdown, text, HTML or JSON, plus guarded REST calls.

What you can do
Fetch a URL and get its content back as clean markdown, plain text, HTML or JSON for the assistant to read or summarize. Make guarded REST calls against web endpoints, with SSRF protections applied to the requests. No individual tools are listed in the manifest, so the exact tool names and parameters are not documented here.
When to use it
Useful when an assistant needs to read a specific web page or API response during a task and you want the fetching to go through an SSRF-safe layer rather than unrestricted network access.
Requirements
Runs as a local process on the user's machine, installed from the npm package @infoinlet/mcp-fetch over stdio. It is desktop-only and not web-executable. No authentication, environment variables or headers are declared. Network access is needed to reach the URLs being fetched.
Before you install
Fetched content comes from third parties and may be untrusted or misleading, so treat it as data rather than instructions. Guarded REST calls can send requests to external services; check which endpoints and methods are permitted before relying on it. No credentials are declared, but any secrets you add to requests would pass through the server.

Installation

In SourceWeft

  1. Open Mcp Fetch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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 days25 pts

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

  • Auth declared10 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.

  • License10 pts

    Declare a license in the repository or the registry entry.