io.github.labtools-studio/fetchmcp
NPM · @LABTOOLSSTUDIO/FETCHMCP
Drop-in fetch MCP: clean Markdown from any URL, with JS rendering and anti-bot.
Available components
Last scanned (11 hours ago)
Scores higher than 55% of npm servers
Category Web Scraping
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 Security74
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 36 of 120 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 85 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 461 tokens (~230/item across 2 items; 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 2 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
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
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +1
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
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/@labtoolsstudio/fetchmcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node scripts/postinstall.mjs |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 7 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 120 packages
| Packages resolved | 120 |
|---|---|
| Stale | 36 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
read_docs Read Documentation Page as Markdown ~179
Fetch a documentation or reference page and return only its main content as clean Markdown, stripping navigation sidebars, headers, footers, and other page chrome. Use this for API docs, guides, and reference pages. For general web pages use read_url. Same JS-rendering, anti-bot, and honest-error behavior as read_url.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | object | – | Extra HTTP headers, e.g. an Authorization token or Cookie for docs behind a login. |
| max_length | integer | – | Maximum characters to return. Default 0 = unlimited. |
| render | boolean | – | JS rendering: true = always, false = never, default = automatic (only for empty SPA shells). |
| start_index | integer | – | Character offset to start from. Default: 0. |
| url | string | yes | The documentation URL to fetch (http or https). |
No output schema declared.
No examples provided.
read_url Read URL as Markdown ~282
Fetch a web page and return its content as clean, LLM-ready Markdown. Full content by default (no truncation). Handles HTML, plain text, Markdown, and JSON responses. JavaScript-heavy pages are rendered automatically in a real browser when the static HTML is an empty SPA shell. Returns an honest typed error when the site blocks access or the content cannot be read — it never silently returns partial or fake content.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | object | – | Extra HTTP headers to send, e.g. an Authorization bearer token or a Cookie for pages behind a login. Example: {"Authorization": "Bearer ...", "Cookie": "session=..."}. |
| max_length | integer | – | Maximum number of characters to return. Default 0 = unlimited (full page). If output is truncated, the response says so and tells you how to continue. |
| raw | boolean | – | If true, return the raw page HTML instead of extracted Markdown. Default: false. |
| render | boolean | – | JS rendering in a real browser: true = always render, false = never render. Default: automatic — renders only when the static HTML turns out to be an empty SPA shell. |
| start_index | integer | – | Character offset to start from, for paging through a long page. Default: 0. |
| url | string | yes | The URL to fetch (http or https). |
No output schema declared.
No examples provided.
How do I install the io.github.labtools-studio/fetchmcp MCP server?
io.github.labtools-studio/fetchmcp runs locally as an npm package, launched with npx -y @labtoolsstudio/fetchmcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @labtoolsstudio/fetchmcp
claude mcp add labtools-studio-fetchmcp -- npx -y @labtoolsstudio/fetchmcp
What is the io.github.labtools-studio/fetchmcp MCP server?
io.github.labtools-studio/fetchmcp is an MCP server listed in the public MCP registry as io.github.labtools-studio/fetchmcp. Drop-in fetch MCP: clean Markdown from any URL, with JS rendering and anti-bot. This page covers its npm package (@labtoolsstudio/fetchmcp).
Is the io.github.labtools-studio/fetchmcp MCP server safe to use?
io.github.labtools-studio/fetchmcp scores 77 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 5 November 2026. 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 io.github.labtools-studio/fetchmcp MCP server expose?
io.github.labtools-studio/fetchmcp exposes 2 tools: read_url, read_docs. Their descriptions and schemas cost roughly 461 tokens of context every time the server is loaded.
Is the io.github.labtools-studio/fetchmcp MCP server still maintained?
io.github.labtools-studio/fetchmcp 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 io.github.labtools-studio/fetchmcp MCP server under?
io.github.labtools-studio/fetchmcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.