# FetchV2 (pypi · fetchv2-mcp-server)

Fetch and extract web pages, discover links, and read llms.txt documentation indexes.

- Trust score: 77/100 (medium)
- Change this week: +21
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `fetchv2-mcp-server`: 77/100 (this document), [markdown](https://verifymcp.io/servers/praveenc-fetchv2-mcp-server/fetchv2-mcp-server.md), [page](https://verifymcp.io/servers/praveenc-fetchv2-mcp-server/fetchv2-mcp-server)

## Channel facts

- Registry: `pypi`
- Package: `fetchv2-mcp-server`
- Version: `2.0.0`
- 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-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 4 of 51 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 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1191 tokens (~297/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the FetchV2 MCP server?

FetchV2 runs locally as a PyPI package, launched with uvx fetchv2-mcp-server. 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 praveenc-fetchv2-mcp-server -- uvx fetchv2-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "praveenc-fetchv2-mcp-server": {
      "command": "uvx",
      "args": [
        "fetchv2-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "praveenc-fetchv2-mcp-server": {
      "command": "uvx",
      "args": [
        "fetchv2-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add praveenc-fetchv2-mcp-server -- uvx fetchv2-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "praveenc-fetchv2-mcp-server": {
      "type": "local",
      "command": [
        "uvx",
        "fetchv2-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add praveenc-fetchv2-mcp-server --command uvx --arg fetchv2-mcp-server
```

### Hermes

```yaml
mcp_servers:
  praveenc-fetchv2-mcp-server:
    command: "uvx"
    args: ["fetchv2-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "praveenc-fetchv2-mcp-server": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "fetchv2-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add praveenc-fetchv2-mcp-server -t stdio -c uvx -a fetchv2-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "praveenc-fetchv2-mcp-server": {
      "command": "uvx",
      "args": [
        "fetchv2-mcp-server"
      ]
    }
  }
}
```

## 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 77, +1)

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

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

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

### 2026-09-16 (score 75, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-15 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 56, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-09 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-08 (score 56)

First indexed and scored.

## MCP tools (4)

### `fetch` (~386 tokens)

Fetch a single webpage and extract its main content as clean markdown.

USE THIS TOOL WHEN:
\- You need to read an article, documentation page, or blog post
\- You want clean, readable text without boilerplate (navbars, ads, footers)
\- The user provides a specific URL to read

DO NOT USE WHEN:
\- You need to fetch multiple URLs (use fetch_batch instead - fewer round trips)
\- You want to discover what pages exist on a site (use discover_links first)

PAGINATION: Large pages are automatically truncated. The response will include
'use start_index=N to continue' - call again with that value to get more content.

EXAMPLES:
\- fetch(url="https://docs.example.com/guide") → Get documentation page
\- fetch(url="https://example.com/api", max_length=2000) → Shorter response to save context
\- fetch(url="https://example.com/data", include_tables=True) → Preserve tabular data

Input parameters:

- `bypass_robots_txt` (boolean): Skip robots.txt check. Only for user-initiated requests.
- `get_raw_html` (boolean): Skip extraction and return raw HTML. Use when you need original markup or extraction fails.
- `include_links` (boolean): Preserve hyperlinks in markdown. Enable to follow references.
- `include_metadata` (boolean): Include title, author, date at top. Disable to save tokens.
- `include_tables` (boolean): Preserve tables in markdown. Disable for text-only articles.
- `max_length` (integer): Maximum characters to return. Use 1000-2000 for summaries, 5000 (default) for full content.
- `start_index` (integer): Character offset for pagination. Use the value from 'start_index=N' in truncated responses.
- `url` (string, required): The webpage URL to fetch (must be http:// or https://)

Output parameters:

- `result` (string)

### `fetch_batch` (~256 tokens)

Fetch multiple webpages in a single request and return combined content.

USE THIS TOOL WHEN:
\- You have 2-10 URLs to read (e.g., from discover_links results)
\- Comparing content across multiple pages
\- Gathering context from several documentation pages at once

KEY BENEFIT: One tool call instead of multiple fetch() calls = fewer round trips,
faster results, and reduced overhead in supervised/approval workflows.

WORKFLOW EXAMPLE:
1\. discover_links(url="https://docs.example.com", filter_pattern="/api/")
2\. fetch_batch(urls=[...returned links...], max_length_per_url=1500)

NOTES:
\- Each URL's content is separated by '---' dividers
\- Failed URLs show inline errors without stopping other fetches
\- Robots.txt is NOT checked for batch fetches (assumes prior discovery)

Input parameters:

- `get_raw_html` (boolean): Skip content extraction and return raw HTML for all URLs.
- `max_length_per_url` (integer): Character limit per URL. Use 1000-1500 when fetching many pages. Default 2000.
- `urls` (array, required): List of webpage URLs to fetch (max 10). URLs are fetched sequentially and results combined.

Output parameters:

- `result` (string)

### `discover_links` (~279 tokens)

Discover all links on a webpage. Use this BEFORE fetch_batch to find relevant URLs.

USE THIS TOOL WHEN:
\- Exploring a documentation site to find relevant pages
\- Building a list of URLs to fetch in batch
\- Finding all subpages under a section (e.g., all /api/ docs)
\- Checking what content exists before deciding what to read

RECOMMENDED WORKFLOW:
1\. discover_links(url="https://docs.example.com/", filter_pattern="/guide/")
2\. Review the returned links and select relevant ones
3\. fetch_batch(urls=[selected_urls], max_length_per_url=1500)

FILTER EXAMPLES:
\- filter_pattern="/docs/"     → Only links containing '/docs/'
\- filter_pattern="getting-started|quickstart" → Links with either term
\- filter_pattern="\.md$"     → Only markdown file links

NOTES:
\- Returns up to 100 links (more are noted but omitted to save context)
\- Relative URLs are automatically resolved to absolute URLs
\- JavaScript/mailto/anchor links are excluded

Input parameters:

- `filter_pattern` (string): Regex to filter links. Examples: '/docs/', '\.pdf$', 'api|guide'. Leave empty for all links.
- `url` (string, required): The webpage URL to scan for links (e.g., a docs index or sitemap)

Output parameters:

- `result` (string)

### `fetch_llms_txt` (~270 tokens)

Fetch and parse an llms.txt file to discover LLM-friendly documentation.

USE THIS TOOL WHEN:
\- A site provides an llms.txt file for AI-friendly content discovery
\- You need to understand what documentation is available
\- You want to fetch structured docs in a single request

WHAT IS llms.txt:
A proposal for sites to provide LLM-friendly content at /llms.txt.
It's a markdown file listing documentation links with descriptions.
See https://llmstxt.org for the specification.

WORKFLOW:
1\. fetch_llms_txt(url="https://example.com/llms.txt") → Get structure
2\. Review sections and links
3\. Either use include_content=True or fetch_batch for specific pages

EXAMPLES:
\- fetch_llms_txt(url="https://fastht.ml/docs/llms.txt")
\- fetch_llms_txt(url="https://example.com/llms.txt", include_content=True)

Input parameters:

- `include_content` (boolean): If true, also fetch content of all linked pages. Default false.
- `max_length_per_url` (integer): When include_content=True, max chars per linked page. Default 2000.
- `url` (string, required): URL to an llms.txt file (e.g., https://example.com/llms.txt)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/praveenc-fetchv2-mcp-server/fetchv2-mcp-server#diagnostics

## Score history

- 2026-09-21: 77
- 2026-09-20: 77
- 2026-09-19: 76
- 2026-09-18: 76
- 2026-09-17: 75
- 2026-09-16: 75
- 2026-09-15: 71
- 2026-09-14: 56
- 2026-09-13: 71
- 2026-09-12: 71
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 71
- 2026-09-08: 56

## Common questions

### What is the FetchV2 MCP server?

FetchV2 is an MCP server listed in the public MCP registry as io.github.praveenc/fetchv2-mcp-server. Fetch and extract web pages, discover links, and read llms.txt documentation indexes. This page covers its PyPI package (fetchv2-mcp-server).

### Is the FetchV2 MCP server safe to use?

FetchV2 scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 FetchV2 MCP server expose?

FetchV2 exposes 4 tools: fetch, fetch_batch, discover_links, fetch_llms_txt. Their descriptions and schemas cost roughly 1,191 tokens of context every time the server is loaded.

### Is the FetchV2 MCP server still maintained?

FetchV2 is still listed as active in the MCP registry. We last reached this channel on 21 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 FetchV2 MCP server under?

FetchV2 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

- PyPI project: https://pypi.org/project/fetchv2-mcp-server/
- Socket report: https://socket.dev/pypi/package/fetchv2-mcp-server
- Repository: https://github.com/praveenc/fetchv2-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/praveenc-fetchv2-mcp-server/fetchv2-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/praveenc-fetchv2-mcp-server/fetchv2-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/praveenc-fetchv2-mcp-server/fetchv2-mcp-server