Skip to main content
mcpSource-backed

Fetch MCP Server

Official MCP server that fetches web content and converts HTML pages into markdown for model-friendly reading.

by Model Context Protocol · submitted by oktofeesh1·added 2026-06-05·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md, https://github.com/modelcontextprotocol/servers
Brand
Fetch MCP Server
Brand domain
github.com
Safety notes
Fetch MCP Server can retrieve arbitrary URLs requested through the MCP client., Upstream warns that the server can access local or internal IP addresses, which can expose sensitive internal services if network access is not constrained., The fetch tool can return raw content or markdown-converted content and supports chunked reads with a start index., Review allowlists, network boundaries, proxy settings, and robots.txt behavior before enabling this server in sensitive environments.
Privacy notes
Requested URLs, page contents, internal hostnames, response text, prompts, tool arguments, and fetch errors may be visible to the MCP client and model provider., Fetching authenticated, private, internal, customer, or confidential pages can expose their content to the model session., Be careful with custom user-agent and proxy settings because they may reveal organization or environment details to requested sites.
Author
Model Context Protocol
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

3 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

4 prerequisites to line up before setup. Includes a review or approval gate.

0/4 ready
Install & runtime2Review & approval1General13 minutes

Safety & privacy surface

Safety & privacy surface

4 safety and 3 privacy notes across 3 risk areas. Review closely: credentials & tokens, network access.

3 areas
  • SafetyNetwork accessFetch MCP Server can retrieve arbitrary URLs requested through the MCP client.
  • SafetyNetwork accessUpstream warns that the server can access local or internal IP addresses, which can expose sensitive internal services if network access is not constrained.
  • SafetyGeneralThe fetch tool can return raw content or markdown-converted content and supports chunked reads with a start index.
  • SafetyNetwork accessReview allowlists, network boundaries, proxy settings, and robots.txt behavior before enabling this server in sensitive environments.
  • PrivacyNetwork accessRequested URLs, page contents, internal hostnames, response text, prompts, tool arguments, and fetch errors may be visible to the MCP client and model provider.
  • PrivacyCredentials & tokensFetching authenticated, private, internal, customer, or confidential pages can expose their content to the model session.
  • PrivacyNetwork accessBe careful with custom user-agent and proxy settings because they may reveal organization or environment details to requested sites.

Safety notes

  • Fetch MCP Server can retrieve arbitrary URLs requested through the MCP client.
  • Upstream warns that the server can access local or internal IP addresses, which can expose sensitive internal services if network access is not constrained.
  • The fetch tool can return raw content or markdown-converted content and supports chunked reads with a start index.
  • Review allowlists, network boundaries, proxy settings, and robots.txt behavior before enabling this server in sensitive environments.

Privacy notes

  • Requested URLs, page contents, internal hostnames, response text, prompts, tool arguments, and fetch errors may be visible to the MCP client and model provider.
  • Fetching authenticated, private, internal, customer, or confidential pages can expose their content to the model session.
  • Be careful with custom user-agent and proxy settings because they may reveal organization or environment details to requested sites.

Prerequisites

  • Python 3.10 or newer available to the MCP client runtime.
  • uvx available for package execution.
  • Network policy that allows the MCP client to fetch approved URLs.
  • Optional Node.js installation if you want the more robust HTML simplifier noted by upstream.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
3 minutes
Difficulty
beginner
Full copyable content
{
  "mcpServers": {
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
  }
}

About this resource

Content

Fetch MCP Server is an official Model Context Protocol reference server for retrieving web content. It exposes a fetch tool that requests a URL, extracts page content, and returns markdown for easier model consumption. It can also return raw content and read long pages in chunks using a start index.

The upstream README documents uvx, pip, and Docker configuration. The PyPI package exposes the mcp-server-fetch command for MCP clients.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live repository and PyPI metadata for current package version, command name, Python requirement, dependencies, tool behavior, robots.txt behavior, and setup guidance.

Features

  • Fetch a URL and extract page content as markdown.
  • Request raw content when markdown conversion is not desired.
  • Limit returned content with a maximum character length.
  • Continue reading long pages by passing a start index.
  • Use optional proxy, user-agent, and robots.txt behavior settings.
  • Run as an official reference MCP server through uvx, pip, or Docker.

Installation

For MCP clients that launch stdio servers:

{
  "mcpServers": {
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
  }
}

Restart the MCP client after adding the server.

Use Cases

  • Ask Claude to retrieve a public documentation page and summarize it.
  • Convert an HTML article or reference page into markdown for review.
  • Let Claude inspect long pages in chunks when the first response is truncated.
  • Use controlled web fetching in workflows where a general browser MCP server is unnecessary.
  • Compare page content across public URLs during research.

Safety and Privacy

Web fetching can become a data exposure path if the server can reach internal services, private pages, or authenticated resources. Keep network access constrained, review proxy and user-agent settings, and consider URL allowlists or policy controls before enabling this server in sensitive environments.

Fetched URLs, response bodies, internal hostnames, prompts, tool arguments, and errors may become part of the model context. Avoid fetching confidential, customer, authenticated, or internal pages unless the data is approved for the current model session.

Duplicate Check

No dedicated modelcontextprotocol/servers Fetch entry, mcp-server-fetch package entry, or matching source URL was found in content/mcp. The existing Sequential Thinking entry is from the same official server monorepo but covers a separate server and package.

Source citations

Add this badge to your README

Show that Fetch MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/fetch-mcp-server.svg)](https://heyclau.de/entry/mcp/fetch-mcp-server)

How it compares

Fetch MCP Server side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

2 trust signals differ across this comparison (Source provenance, Submitter).

Field

Official MCP server that fetches web content and converts HTML pages into markdown for model-friendly reading.

Open dossier

Artidrop remote MCP server for publishing HTML, Markdown, and multi-file sites from AI agents with shareable URLs via streamable HTTP, optional API keys, and AFAuth agent identities.

Open dossier

Browser-control MCP server and CLI that lets AI agents use a real Chrome session, including logged-in browser state, site adapters, DOM snapshots, authenticated fetches, network traces, screenshots, and page actions.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verified
Source provenanceDiffersSource-backedSubmission linkedSource submissionSource-backed
SubmitterDiffersoktofeesh1kiannidevoktofeesh1
Install riskReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand
Categorymcpmcpmcp
SourceSource-backedSource-backedSource-backed
AuthorModel Context ProtocolArtidropepiral
Added2026-06-052026-06-162026-06-06
Platforms
Harness
Source repo
Safety notesFetch MCP Server can retrieve arbitrary URLs requested through the MCP client. Upstream warns that the server can access local or internal IP addresses, which can expose sensitive internal services if network access is not constrained. The fetch tool can return raw content or markdown-converted content and supports chunked reads with a start index. Review allowlists, network boundaries, proxy settings, and robots.txt behavior before enabling this server in sensitive environments.Publish and update tools create publicly reachable URLs when visibility is public or unlisted. Pass content verbatim through MCP; reformatting can break HTML, script, or markdown rendering per official guidance. Anonymous publishes are limited to five per hour per IP; authenticated keys raise limits but billable access may apply. AFAuth agent signup provisions accounts without portal keys; review attestation and ownership policies before production use.bb-browser can control a real browser session, inspect pages, click elements, fill inputs, evaluate JavaScript, fetch URLs with browser authentication, capture screenshots, and inspect network traffic. Commands may act as the logged-in user on social, finance, job, developer, shopping, and knowledge websites. Keep the daemon bound to trusted local interfaces unless you deliberately configure remote access through a private network. Review community site adapters before using them with authenticated accounts or valuable sessions. Require human approval before posting, submitting forms, changing account settings, applying to jobs, making purchases, or running destructive site actions.
Privacy notesRequested URLs, page contents, internal hostnames, response text, prompts, tool arguments, and fetch errors may be visible to the MCP client and model provider. Fetching authenticated, private, internal, customer, or confidential pages can expose their content to the model session. Be careful with custom user-agent and proxy settings because they may reveal organization or environment details to requested sites.Published artifacts, titles, and content are stored on Artidrop infrastructure according to its privacy terms. API keys and OAuth tokens grant publish and management access; store them in connector headers, not chat logs. Private visibility restricts reads to owners, but MCP tool output may still appear in Claude session history.Tab URLs, titles, DOM snapshots, page content, selected elements, screenshots, network requests, responses, console output, traces, and authenticated fetch results may be exposed to the MCP client and model. Browser login state is used by the page and browser; even if cookies are not extracted directly, commands can act through authenticated sessions. Network request bodies and response data may contain tokens, account data, personal messages, search history, customer information, or internal application data. The upstream privacy doc says communication is local and there is no telemetry or external server, but model providers still receive any data your MCP client sends in prompts or tool results.
Prerequisites
  • Python 3.10 or newer available to the MCP client runtime.
  • uvx available for package execution.
  • Network policy that allows the MCP client to fetch approved URLs.
  • Optional Node.js installation if you want the more robust HTML simplifier noted by upstream.
  • Artidrop API key from https://artidrop.ai for authenticated list, update, and delete tools, or accept anonymous publish rate limits.
  • Claude Pro, Team, or Enterprise with Connectors support, or another MCP client with streamable HTTP transport.
  • Review of Artidrop visibility settings (public, unlisted, private) before publishing sensitive content.
  • Human review of generated HTML or Markdown before publishing externally shareable artifacts.
  • Node.js 18 or newer.
  • Chrome session, local daemon, and Chrome extension or supported OpenClaw browser path configured according to the upstream README.
  • MCP client such as Claude Code, Codex, Cursor, or another compatible host.
  • Explicit approval to let an agent use the active browser's logged-in state.
Install
uvx mcp-server-fetch
claude mcp add --transport http artidrop https://artidrop.ai/mcp
npx -y bb-browser --mcp
Config
{
  "mcpServers": {
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
  }
}
{
  "mcpServers": {
    "artidrop": {
      "url": "https://artidrop.ai/mcp?key=sk_YOUR_KEY",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "bb-browser": {
      "command": "npx",
      "args": ["-y", "bb-browser", "--mcp"]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimed
Open 3 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.