# dev.fetchgate/fetchgate (remote · fetchgate.dev)

Fetch any URL as clean Markdown or metadata, and buy digital goods via x402 — for AI agents.

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

## Components

- remote · `fetchgate.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dev-fetchgate-fetchgate/fetchgate.md), [page](https://verifymcp.io/servers/dev-fetchgate-fetchgate/fetchgate)

## Channel facts

- Endpoint: `https://fetchgate.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-27.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 884 tokens (~147/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the dev.fetchgate/fetchgate MCP server?

dev.fetchgate/fetchgate is a hosted endpoint at https://fetchgate.dev/mcp, so there is nothing to install locally. 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 --transport http dev-fetchgate-fetchgate 'https://fetchgate.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-fetchgate-fetchgate": {
      "url": "https://fetchgate.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-fetchgate-fetchgate": {
      "type": "http",
      "url": "https://fetchgate.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-fetchgate-fetchgate]
url = "https://fetchgate.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-fetchgate-fetchgate": {
      "type": "remote",
      "url": "https://fetchgate.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-fetchgate-fetchgate --url 'https://fetchgate.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-fetchgate-fetchgate:
    url: "https://fetchgate.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-fetchgate-fetchgate": {
      "Transport": "http",
      "Url": "https://fetchgate.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-fetchgate-fetchgate -t streamable-http -u 'https://fetchgate.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-fetchgate-fetchgate": {
      "type": "http",
      "url": "https://fetchgate.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-25 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-21 (score 73, +1)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 72, +1)

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

### 2026-09-17 (score 71, +1)

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

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

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

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

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

### 2026-09-11 (score 68, +1)

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

### 2026-09-08 (score 67, +1)

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

## MCP tools (6)

### `read_url` (~111 tokens)

Read URL as Markdown

Fetch a URL server-side and return its main content as clean Markdown, with scripts/styles/nav/ads/boilerplate stripped out. Wraps GET /v1/read. Free tier: 30 calls/day per caller; priced at $0.002/call via x402 once that's exhausted (see get_purchase_info for how the x402 flow works). Only http:// and https:// URLs are accepted; private/internal-network hosts are rejected.

Input parameters:

- `url` (string, required): Absolute http(s) URL to fetch.

### `get_metadata` (~88 tokens)

Get URL Metadata

Fetch a URL server-side and return structured metadata: title, description, canonical URL, OpenGraph/Twitter card fields, favicon URL, language, and published/modified timestamps when present. Wraps GET /v1/meta. Same free tier as read_url; priced at $0.001/call via x402 once exhausted.

Input parameters:

- `url` (string, required): Absolute http(s) URL to fetch.

### `list_products` (~71 tokens)

List Products

List Fetchgate's digital-goods catalog: id, name, description, priceUsd, currency, file format, size, sha256, and a walletless humanUrl checkout link for each product for sale. Wraps GET /v1/products. Free, no rate limit, no payment required just to browse.

### `get_purchase_info` (~109 tokens)

Get Purchase Info

Look up a product by id (from list_products) and explain exactly how to buy it: its price, and the x402 purchase flow step by step (the 402 challenge shape, the PAYMENT-SIGNATURE header, and the signed download URL you get back on success). Does not take payment itself — informational only, mirroring the pre-payment leg of GET /v1/buy/:id.

Input parameters:

- `product_id` (string, required): Product id, from list_products' `id` field.

### `get_agent_census` (~200 tokens)

Get Agent Web Crawler Census

Return the Agent Web Crawler Census: every named bot observed crawling a live, publicly-listed x402 + MCP endpoint over a 24-hour window, each with a case-insensitive regex `matcher` and a behavioural `category` (liveness-monitor, directory-crawler, price-scraper, security-research, ai-training, ...) so you can classify your own access log. Observed first-hand, not aggregated from third-party bot lists. Notable finding: of the named agent-web crawlers in the census, zero have ever presented a payment, and several declare that in their own User-Agent string. Wraps GET /v1/agent-census.json. Free, unmetered, no payment required. CC BY 4.0.

Input parameters:

- `category` (string): Optional. Return only agents in this behavioural category, e.g. "price-scraper" or "liveness-monitor". Omit for the full census.

### `scan_mcp_server` (~196 tokens)

Scan an MCP server's tool descriptions for poisoning patterns

Connect to a remote Streamable HTTP MCP server, fetch its tools/list (sends only initialize, notifications/initialized and tools/list — never tools/call) and scan every tool name, description, parameter description and the server's initialize `instructions` string for tool-poisoning patterns: hidden-instruction markers, invisible Unicode, directives aimed at the model, credential/secret references, exfiltration shapes and instructions about other tools. Returns per-tool findings with severity, excerpt and a score band. Use it before installing or trusting a third-party server. Heuristic: a clean result means nothing obvious in what the server declares about itself, not that it is safe. Wraps GET /v1/mcp-scan. Free, rate-limited per caller; private/internal-network hosts are rejected.

Input parameters:

- `url` (string, required): The MCP server's Streamable HTTP endpoint URL, e.g. https://example.com/mcp

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-fetchgate-fetchgate/fetchgate#diagnostics

## Score history

- 2026-09-27: 73
- 2026-09-26: 73
- 2026-09-25: 73
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 73
- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 67
- 2026-09-09: 67
- 2026-09-08: 67
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 65
- 2026-09-04: 65
- 2026-09-03: 64
- 2026-09-02: 64
- 2026-09-01: 63
- 2026-08-31: 63
- 2026-08-30: 62
- 2026-08-29: 62

## Common questions

### What is the dev.fetchgate/fetchgate MCP server?

dev.fetchgate/fetchgate is an MCP server listed in the public MCP registry as dev.fetchgate/fetchgate. Fetch any URL as clean Markdown or metadata, and buy digital goods via x402, for AI agents. This page covers its hosted endpoint (https://fetchgate.dev/mcp).

### Is the dev.fetchgate/fetchgate MCP server safe to use?

dev.fetchgate/fetchgate scores 73 out of 100 on VerifyMCP. 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 dev.fetchgate/fetchgate MCP server expose?

dev.fetchgate/fetchgate exposes 6 tools: read_url, get_metadata, list_products, get_purchase_info, get_agent_census, scan_mcp_server. Their descriptions and schemas cost roughly 775 tokens of context every time the server is loaded.

### Does the dev.fetchgate/fetchgate MCP server require authentication?

No. We connected to dev.fetchgate/fetchgate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the dev.fetchgate/fetchgate MCP server still maintained?

dev.fetchgate/fetchgate is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://fetchgate.dev/mcp
- Website: https://fetchgate.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-fetchgate-fetchgate/fetchgate.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-fetchgate-fetchgate/fetchgate.json
- HTML version of this page: https://verifymcp.io/servers/dev-fetchgate-fetchgate/fetchgate