Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Web Fetch

NPM · @PIPEWORX/MCP-WEB-FETCH · 2 COMPONENTS

web-fetch — fetch ONE public URL live from its origin, verbatim.

Available components

remote · gateway.pipeworx.io 77 npm · @pipeworx/mcp-web-fetch 80
+3 this week 80 Trust /100

Last scanned (2 hours ago)

Scores higher than 65% of npm servers

Category Web Scraping

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-web-fetch). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability53
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 471 tokens (~471/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 77

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-web-fetch@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-web-fetch
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-web-fetch/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3561042563
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:b0c03e9a2be229e04072aefe30a83fbcebea968227de9f21b57c4e77e2c5c344788f531807e1c88c91bdfddf33911a9e569f07619a042ba47c47dbfc5

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~419 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fetch_url ~419

Fetch the exact contents of ONE public web URL live from its origin server and return them verbatim with a SHA-256 hash of the bytes received. Use it to read a specific page, raw data file (CSV, TSV, .dat, JSON, XML), API endpoint or PDF whose address you already know. format "auto" (default) returns readable text for HTML and PDF and the raw body for everything else; "raw" returns the body itself (decoded text, or base64 for binary such as zip/xlsx); "text" forces text extraction. Large bodies page with max_bytes and offset. Also returns url_final, the redirect chain, status, response headers, charset and how it was chosen. Refusals are explicit: blocked_url (private address, disallowed port or scheme, credentials in the URL), upstream_refused (the site answered 401/403/429 or a bot wall; the response names archive_evidence as a place to look for a capture), upstream_down, upstream_status (e.g. 404). Does not run JavaScript, log in, send cookies or search; for a past version of a page use archive_evidence. Keyless.

NameTypeReqDescription
formatstring–auto (default): text for HTML and PDF, raw for everything else. raw: the body as received. text: readable text extracted from HTML/PDF.
max_bytesnumber–Size of the returned window. Default 100000. Maximum 1000000 for text, 512000 for base64 (binary).
offsetnumber–Where the window starts: a byte offset into the body (raw), or a character offset into the extracted text (text). Use next_offset from the previous call to page. Default 0.
urlstringyesThe absolute http(s) URL to fetch, e.g. "https://data.giss.nasa.gov/gistemp/tabledata_v4/GLB.Ts+dSST.csv". http:// is tried over https first.

No output schema declared.

No examples provided.

Install

How do I install the Web Fetch MCP server?

Web Fetch runs locally as an npm package, launched with npx -y @pipeworx/mcp-web-fetch. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-web-fetch

# add to Claude Code
claude mcp add pipeworx-io-web-fetch -- npx -y @pipeworx/mcp-web-fetch
Common questions

What is the Web Fetch MCP server?

Web Fetch is an MCP server listed in the public MCP registry as io.github.pipeworx-io/web-fetch. web-fetch, fetch ONE public URL live from its origin, verbatim. This page covers its npm package (@pipeworx/mcp-web-fetch).

Is the Web Fetch MCP server safe to use?

Web Fetch scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Web Fetch MCP server expose?

Web Fetch exposes 1 tool: fetch_url. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.

Is the Web Fetch MCP server still maintained?

Web Fetch is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Web Fetch MCP server under?

Web Fetch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.