dev.fetchgate/fetchgate
REMOTE · FETCHGATE.DEV · SCANNED SEP 27
Fetch any URL as clean Markdown or metadata, and buy digital goods via x402 — for AI agents.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- 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. 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · fetchgate.dev
claude mcp add --transport http dev-fetchgate-fetchgate 'https://fetchgate.dev/mcp'
{
"mcpServers": {
"dev-fetchgate-fetchgate": {
"url": "https://fetchgate.dev/mcp"
}
}
} {
"servers": {
"dev-fetchgate-fetchgate": {
"type": "http",
"url": "https://fetchgate.dev/mcp"
}
}
} [mcp_servers.dev-fetchgate-fetchgate] url = "https://fetchgate.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-fetchgate-fetchgate": {
"type": "remote",
"url": "https://fetchgate.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-fetchgate-fetchgate --url 'https://fetchgate.dev/mcp' --transport streamable-http
mcp_servers:
dev-fetchgate-fetchgate:
url: "https://fetchgate.dev/mcp" {
"McpServers": {
"dev-fetchgate-fetchgate": {
"Transport": "http",
"Url": "https://fetchgate.dev/mcp"
}
}
} assistant mcp add dev-fetchgate-fetchgate -t streamable-http -u 'https://fetchgate.dev/mcp'
{
"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.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 +1
- Stability: 0.97 → pass security
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 8 Sept 26 +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.
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 27 Sept 2026 · Probed https://fetchgate.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fetchgate.dev | CN=WE1,O=Google Trust Services,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 71b1469691db504a13df7a8f2eda34ba |
| SANs: fetchgate.dev, *.fetchgate.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fetchgate.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fetchgate.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fetchgate.dev/mcp | Verified | 200 | |
| http (plaintext) | http://fetchgate.dev/mcp | Inconclusive | 405 |
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 →
get_agent_census Get Agent Web Crawler Census ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional. Return only agents in this behavioural category, e.g. "price-scraper" or "liveness-monitor". Omit for the full census. |
No output schema declared.
No examples provided.
get_metadata Get URL Metadata ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL to fetch. |
No output schema declared.
No examples provided.
get_purchase_info Get Purchase Info ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | Product id, from list_products' `id` field. |
No output schema declared.
No examples provided.
list_products List Products ~71
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_url Read URL as Markdown ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL to fetch. |
No output schema declared.
No examples provided.
scan_mcp_server Scan an MCP server's tool descriptions for poisoning patterns ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The MCP server's Streamable HTTP endpoint URL, e.g. https://example.com/mcp |
No output schema declared.
No examples provided.
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.