原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Fetch MCP Server

作者:YawLabs版本 0.8.6i★ –i在你的电脑上运行
注册名称io.github.YawLabs/fetch-mcp

安装

概览

作者提供的说明(英文原文)

HTTP fetch MCP server: SSRF protection, HTML-to-markdown, reader mode, metadata extraction

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 文档、表格与办公

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@yawlabs/fetch-mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add fetch -- npx -y @yawlabs/fetch-mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@yawlabs/fetch-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "fetch": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@yawlabs/fetch-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 YawLabs 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“文档、表格与办公”中的其他服务器比较i

  • 星标数多于此分类中其他 3605 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 3605 个服务器的 76% 更新
  • 基础检查结果等于或优于此分类中其他 3605 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Fetch MCP Server 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.8.6)于9天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Agent-Native Calendar

Agent-Native Google Calendar - manage events, sync, and public booking

作者:BuilderIO广泛使用★ 76202个月前更新

在云端运行

Excel MCP Server

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

作者:haris-musa广泛使用↓ 5万/周★ 42768天前更新

在你的电脑上运行

MCP Server for Excel

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

作者:sbroenne正在增长↓ 4321/周★ 8476天前更新

在你的电脑上运行

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

@yawlabs/fetch-mcp

One click adds this to your local Yaw MCP config so it's available in every Yaw Terminal session. Or install manually below.

A comprehensive HTTP fetch MCP server for AI assistants. Bring-your-own client: runs as a stdio MCP server so any MCP-compatible client (Claude Code, Claude Desktop, Cursor, mcph, …) can fetch web content safely.

What it gives the model

ToolWhat it does
http_get / http_head / http_optionsBare HTTP requests with headers, auth, timeout, size cap, retry
http_post / http_put / http_patch / http_deleteWrite-method HTTP with JSON or raw body
fetch_html_to_markdownGET a page and convert to clean markdown (3–8× smaller than raw HTML)
fetch_html_to_textGET a page and convert to plain text with block structure preserved
fetch_readerReader-mode extraction — isolates the article body and returns title + markdown
fetch_metaExtract metadata: title, description, OpenGraph, Twitter cards, JSON-LD, feeds, icons
fetch_linksExtract every outbound link, resolved to absolute URLs, classified internal/external
fetch_sitemapParse sitemap.xml (including gzipped and sitemap-index chaining)
fetch_feedParse an RSS 2.0 or Atom 1.0 feed into entries
fetch_robotsParse a site's robots.txt, return the verdict for a given path & user-agent

Safety

SSRF protection is on by default. The server refuses requests to:

  • Loopback (127.0.0.0/8, ::1)
  • RFC1918 private ranges (10/8, 172.16/12, 192.168/16)
  • Link-local (169.254/16, fe80::/10) — including the cloud metadata endpoint 169.254.169.254
  • CGNAT (100.64/10)
  • Unique-local IPv6 (fc00::/7)
  • Multicast / broadcast
  • IPv4-mapped IPv6 (::ffff:0:0/96) re-checked against the IPv4 rules, and likewise the IPv4 embedded in IPv4-compatible (::/96), IPv4-translated (::ffff:0:0:0/96) and 6to4 (2002::/16) addresses
  • Teredo (2001::/32), NAT64 (64:ff9b::/96, 64:ff9b:1::/48), site-local (fec0::/10) and discard-only (100::/64) IPv6
  • Any other IPv6 outside global unicast (2000::/3), and the non-global blocks inside it (3fff::/20, 2001:2::/48, 2001:10::/28)
  • The Azure WireServer address 168.63.129.16
  • Non-http/https schemes (file://, gopher://, javascript:, …)
  • Hostname localhost and any *.localhost

Every redirect hop is re-validated against all of the above -- scheme, literal IP and localhost* -- before it is dialed, so a 302 from a public host to http://127.0.0.1, http://169.254.169.254 or ftp://… is caught. For hostnames, DNS is resolved once per hop, every returned address is checked, and the verified IP is pinned into the HTTP dispatcher so the subsequent TCP connection dials that exact address — closing the DNS-rebinding TOCTOU window. Authorization, Cookie and Proxy-Authorization headers are stripped on cross-origin redirects.

Reaching private hosts (development)

The model chooses tool arguments, and the model is not trusted: a prompt injected through a fetched page can ask for anything. So the per-call allow_private_hosts: true opt-in is refused unless the operator enables it by launching the server with FETCH_MCP_ALLOW_PRIVATE_HOSTS=1 (true/yes/on also work; any unrecognised value is treated as off and named on stderr). With the variable set, a call still has to ask: requests without allow_private_hosts stay guarded.

{

"mcpServers": { "fetch": { "command": "npx", "args": ["-y", "@yawlabs/fetch-mcp@latest"], "env": { "FETCH_MCP_ALLOW_PRIVATE_HOSTS": "1" } } } }

Only set it where the model may legitimately reach your internal network -- a local dev box, not a cloud VM with a metadata endpoint.

Install & run

# One-off (auto-updates each spawn via @latest)

npx -y @yawlabs/fetch-mcp@latest

Or globally

npm i -g @yawlabs/fetch-mcp fetch-mcp

Requires Node 22.19 or newer when running on Node (the floor of its HTTP client, undici 8; the launcher refuses older Nodes with a clear message instead of crashing). Under oam, which the launcher prefers when installed, the Node version does not matter.

Configure in Claude Code / Claude Desktop

Add to your client's MCP config (usually claude_desktop_config.json or ~/.claude.json):

{

"mcpServers": { "fetch": { "command": "npx", "args": ["-y", "@yawlabs/fetch-mcp@latest"] } } }

Or via mcph:

mcph add fetch

Tool reference

http_get, http_post, http_put, http_patch, http_delete, http_head, http_options

Common parameters:

FieldTypeDefaultMeaning
urlstring—Absolute URL
headersobject—Custom request headers
timeout_msint10000Timeout for each attempt, covering DNS, every redirect hop and the body. Retries get a fresh budget; a whole call is capped at 5 minutes. Cancelling the tool call stops the request
max_bytesint5242880 (5 MiB)Truncate body if larger
max_redirectsint5Redirect hops allowed
retriesint0Retry count on 408/425/429/5xx with backoff (honors Retry-After)
user_agentstring@yawlabs/fetch-mcp/ User-Agent override
basic_auth{username,password}—Injects Authorization: Basic …
bearer_tokenstring—Injects Authorization: Bearer …
allow_private_hostsboolfalseOpt this call into loopback / private / link-local targets. Refused unless the operator set FETCH_MCP_ALLOW_PRIVATE_HOSTS=1 (details)
decode_textbool*auto*When unset, auto-detects by response Content-Type (text for text/*, JSON, XML, JS, form-urlencoded; binary otherwise). Set explicitly true to force text decoding, false to force base64 in body_base64.

Body-capable tools (POST/PUT/PATCH/DELETE) also take:

FieldTypeMeaning
bodystringRaw request body
body_jsonanyStructured body — encoded as JSON, Content-Type: application/json set automatically
content_typestringOverrides Content-Type

Response shape:

{

ok: boolean; status: number; statusText: string; url: string; // final URL after redirects headers: Record ; body_text?: string; body_base64?: string; // when decode_text=false json?: unknown; // auto-parsed when response is application/json truncated?: boolean; // set when max_bytes hit redirects?: string[]; // chain of intermediate URLs duration_ms: number; error?: string; }

fetch_html_to_markdown

GET the URL, strip scripts/styles/iframes/svg/canvas plus , , , convert to atx-headed markdown with fenced code blocks and dash bullets. Intended for feeding pages into an LLM without blowing the context budget.

fetch_html_to_text

Same fetch, but emits plain text with block-level structure preserved as newlines. Useful when the model doesn't need markdown formatting.

fetch_reader

Isolates the main article body using, in order: , , itemprop="articleBody", common CMS class names (post-content, entry-content, etc.), then as fallback. Returns:

{

url: string; // final URL after redirects title?: string; // og:title, then , then byline?: string; // meta[name=author] / article:author wordCount: number; markdown: string; // main content converted to markdown }

fetch_meta

GET a URL and return its head metadata without downloading the full body (caps at 2 MiB by default):

{

url: string; title?: string; description?: string; canonical?: string; language?: string; robots?: string; og: Record ; // first value per key (og:title, og:image, og:type, ...) twitter: Record ; // first value per key article: Record ; // first value per key ogAll: Record ; // only keys that appear > once (e.g. multiple og:image) twitterAll: Record ; articleAll: Record ; icons: Array<{ rel: string; href: string; sizes?: string }>; feeds: Array<{ href: string; title?: string; type?: string }>; // RSS/Atom jsonLd: unknown[]; // parsed application/ld+json blocks }

fetch_links

GET a page and return every with text, resolved to absolute URLs. Respects . Skips #, javascript:, mailto:, tel:, data:, file:. Each link is classified internal or external vs. the page host. Optional filter/dedupe/limit.

fetch_sitemap

Fetch a sitemap.xml or sitemap-index and return the URL list:

{

sitemaps: string[]; // indexes followed, in order urlCount: number; truncated: boolean; // hit max_urls childSitemaps: string[]; // listed but not fetched (past max_depth or max_sitemaps) warnings: Array<{ url: string; error: string }>; urls: Array<{ loc: string; lastmod?: string; changefreq?: string; priority?: number; }>; }

Gzipped .xml.gz sitemaps are auto-decompressed. max_depth controls how many levels of sitemap-index to follow (default 1). Setting max_depth: 0 on a sitemap-index returns the index's childSitemaps list without fetching any child (useful to discover structure cheaply). Partial failures — one child sitemap 500s while others succeed — are returned under warnings rather than aborting the whole call. max_sitemaps (default 50, max 1000) caps how many sitemap documents one call fetches, index included; children past it are listed under childSitemaps with a warning. The whole call is capped at 5 minutes. max_bytes (default 20 MiB) applies to each sitemap, and to the decompressed size of a gzipped one; a sitemap larger than that is an error (a warning for a child) rather than a silently partial URL list.

fetch_feed

Parse an RSS 2.0 or Atom 1.0 feed:

{

kind: "rss" | "atom" | "unknown"; title?: string; description?: string; link?: string; updated?: string; entryCount: number; truncated: boolean; // hit limit entries: Array<{ title?: string; link?: string; id?: string; published?: string; updated?: string; author?: string; summary?: string; content?: string; categories?: string[]; }>; }

fetch_robots

Fetches /robots.txt, parses it, and returns:

{

robotsUrl: string; status: number; userAgent: string; path: string; allowed: boolean; matchedRule: string | null; // the longest-match Allow/Disallow that decided it crawlDelay: number | null; // from the matched group sitemaps: string[]; // top-level Sitemap: declarations rawRobotsText: string; // first 512KB note?: string; // only when robots.txt 404s }

A /robots.txt that returns 404 means there are no rules, so the verdict is allowed: true. The response keeps the same shape: status: 404, matchedRule: null, crawlDelay: null, sitemaps: [], rawRobotsText: "", plus the note. Any other non-2xx status is returned as an error.

The parser follows Google's rules: longest match wins, * is a wildcard segment, $ anchors the end of the path, specific user-agent group beats the * wildcard group when the UA matches (comparison uses the length of the actually-matche

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx