Fetch MCP Server (zcaceres)

70/100

Capped at 70: core tools not tested: blocked in sandbox; the tests add up to 80. Why scores are capped

Last tested 2026-11-18 UTC (Fresh: tested within 30 days) Connects · tools listedNo tool call tested yet No key to connect

Advisories: not yet checked

Security review: not tested

Test points add up to 80; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology

Test points before the cap (80/100)

  • Install20/20
  • Handshake30/30
  • Maintenance5/25
  • Docs15/15
  • License10/10

Tested npm mcp-fetch-server 1.1.2 (MIT; repo zcaceres/fetch-mcp). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 6 tools (no tool annotations). Real calls: 0 of 3 real function calls passed. No passing real call: the test box resolves every hostname to a private address (198.18.0.1), so the server's own SSRF guard refuses all fetches. Core tools not tested: 70 cap.
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): fail. 0 of 3 real function calls passed. No passing real call: the test box resolves every hostname to a private address (198.18.0.1), so the server's own SSRF guard refuses all fetches. Evidence: local test run, Nov 18, 2026 UTC.

Transport (tested 2026-11-18 UTC): stdio

Token cost (estimate): approx. 837 tokens, cl100k estimate (6 tools, measured 2026-11-18 UTC, version 1.1.2). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 6 read, 0 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • fetch_html — read
  • fetch_json — read
  • fetch_markdown — read
  • fetch_readable — read
  • fetch_txt — read
  • fetch_youtube_transcript — read

handshake and tools listed without a recorded key or OAuth

Score 70/100 · Tools 6 · Token cost approx. 837 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 1.1.2 · Package mcp-fetch-server · Repo zcaceres/fetch-mcp

Summary: Fetch MCP Server (zcaceres) completed an MCP handshake without credentials and exposed 6 tools.

Evidence summary

Handshake
pass
Tools listed
6
Context cost
approx. 837 tokens, cl100k estimate (6 tools, measured 2026-11-18 UTC, version 1.1.2; an estimate) ranking · add up your servers' context cost
API key
No key to connect (handshake passed)
Tested
2026-11-18 UTC

Test results

TestResultPointsEvidence
installpass20npm install mcp-fetch-server --ignore-scripts (Node v24.22.1, Linux) succeeded in 2s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 6 tools listed in 5.3s.
maintenancepartial5Repo pushed 250 days before test.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package).
licensepass10MIT (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 837 tokens, cl100k estimate for 6 tools · about 10% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-18 UTC

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 6 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Not yet checked.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-18 UTC test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

52ea6c406cac: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "mcp-fetch-server",
  "version": "1.1.2",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-18",
  "tools_count": 6,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install mcp-fetch-server --ignore-scripts` (Node v24.22.1, Linux) succeeded in 2s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 6 tools listed in 5.3s."
    ],
    "maintenance": [
      "partial",
      5,
      "Repo pushed 250 days before test."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  },
  "testedAt": "2026-11-18T04:17:48.179Z"
}

Install

npx -y mcp-fetch-server

Pin the version we tested

npx -y --ignore-scripts mcp-fetch-server@1.1.2

tested 2026-11-18 UTC. Newer versions may differ and were not tested by us.

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

Tools listed

fetch_html, fetch_markdown, fetch_txt, fetch_json, fetch_readable, fetch_youtube_transcript

Quick config

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

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run npm install mcp-fetch-server --ignore-scripts (Node v24.22.1). This is the exact command we ran on 2026-11-18 UTC.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (6 in our test).
{
  "mcpServers": {
    "mcp-fetch-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-fetch-server"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best dev MCP servers

FAQ

Is Fetch MCP Server (zcaceres) deprecated?

No. Fetch MCP Server (zcaceres) was not deprecated or archived when we last tested it on 2026-11-18 UTC.

What replaces Fetch MCP Server (zcaceres)?

Nothing; Fetch MCP Server (zcaceres) is not deprecated as of 2026-11-18 UTC.

Does Fetch MCP Server (zcaceres) need an API key?

No. It completed an MCP handshake with no credentials and listed 6 tools.

Embed the badge

TestedMCP: 70/100, tested 2026-11-18 UTC

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue