# io.github.labtools-studio/fetchmcp (npm · @labtoolsstudio/fetchmcp)

Drop-in fetch MCP: clean Markdown from any URL, with JS rendering and anti-bot.

- Trust score: 81/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@labtoolsstudio/fetchmcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/labtools-studio-fetchmcp/labtoolsstudio-fetchmcp.md), [page](https://verifymcp.io/servers/labtools-studio-fetchmcp/labtoolsstudio-fetchmcp)

## Channel facts

- Registry: `npm`
- Package: `@labtoolsstudio/fetchmcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 92/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does.
  - 37 of 123 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 39 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add labtools-studio-fetchmcp -- npx -y @labtoolsstudio/fetchmcp
```

### Cursor

```json
{
  "mcpServers": {
    "labtools-studio-fetchmcp": {
      "command": "npx",
      "args": [
        "-y",
        "@labtoolsstudio/fetchmcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "labtools-studio-fetchmcp": {
      "command": "npx",
      "args": [
        "-y",
        "@labtoolsstudio/fetchmcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add labtools-studio-fetchmcp -- npx -y @labtoolsstudio/fetchmcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "labtools-studio-fetchmcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@labtoolsstudio/fetchmcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add labtools-studio-fetchmcp --command npx --arg -y --arg @labtoolsstudio/fetchmcp
```

### Hermes

```yaml
mcp_servers:
  labtools-studio-fetchmcp:
    command: "npx"
    args: ["-y", "@labtoolsstudio/fetchmcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "labtools-studio-fetchmcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@labtoolsstudio/fetchmcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add labtools-studio-fetchmcp -t stdio -c npx -a -y @labtoolsstudio/fetchmcp
```

### Other

```json
{
  "mcpServers": {
    "labtools-studio-fetchmcp": {
      "command": "npx",
      "args": [
        "-y",
        "@labtoolsstudio/fetchmcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 81, +1)

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

### 2026-09-18 (score 80, +1)

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

### 2026-09-17 (score 79, −3)

- [functional] Stability: pass → 0.80

### 2026-09-16 (score 82, 0)

- [security] Stability: 0.97 → pass

### 2026-09-15 (score 82, +1)

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

### 2026-09-13 (score 81, +1)

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

### 2026-09-11 (score 80, −2)

- [functional] Stability: pass → 0.83

### 2026-09-10 (score 82, 0)

- [security] Stability: 0.97 → pass

## MCP tools (2)

### `read_url` (~282 tokens)

Read URL as Markdown

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.

Input parameters:

- `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, required): The URL to fetch (http or https).

### `read_docs` (~179 tokens)

Read Documentation Page as Markdown

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.

Input parameters:

- `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, required): The documentation URL to fetch (http or https).

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/labtools-studio-fetchmcp/labtoolsstudio-fetchmcp#diagnostics

## Score history

- 2026-09-20: 81
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 79
- 2026-09-16: 82
- 2026-09-15: 82
- 2026-09-14: 81
- 2026-09-13: 81
- 2026-09-12: 80
- 2026-09-11: 80
- 2026-09-10: 82
- 2026-09-09: 82
- 2026-09-08: 81
- 2026-09-07: 81
- 2026-09-06: 80
- 2026-09-05: 80
- 2026-09-04: 79
- 2026-09-03: 79
- 2026-09-02: 79
- 2026-09-01: 78
- 2026-08-31: 78
- 2026-08-30: 77
- 2026-08-29: 77
- 2026-08-28: 76
- 2026-08-27: 76
- 2026-08-26: 75
- 2026-08-25: 74
- 2026-08-24: 73
- 2026-08-23: 73
- 2026-08-22: 72

## Common questions

### 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 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.

## Links

- npm package: https://www.npmjs.com/package/@labtoolsstudio/fetchmcp
- Socket report: https://socket.dev/npm/package/@labtoolsstudio/fetchmcp
- Repository: https://github.com/labtoolsstudio/fetchmcp
- Changelog RSS feed: https://verifymcp.io/servers/labtools-studio-fetchmcp/labtoolsstudio-fetchmcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/labtools-studio-fetchmcp/labtoolsstudio-fetchmcp.json
- HTML version of this page: https://verifymcp.io/servers/labtools-studio-fetchmcp/labtoolsstudio-fetchmcp