Hydrafetch
REMOTE · API.HYDRAFETCH.COM · SCANNED SEP 20
Turn any URL into clean Markdown and structured data. Scrape, crawl, search and extract.
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1077 tokens (~82/item across 13 items; 13 tools + 0 resources), lean.Pass
- 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
How do I install the Hydrafetch MCP server?
Hydrafetch is a hosted endpoint at https://api.hydrafetch.com/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 · api.hydrafetch.com
claude mcp add --transport http com-hydrafetch-web 'https://api.hydrafetch.com/mcp'
{
"mcpServers": {
"com-hydrafetch-web": {
"url": "https://api.hydrafetch.com/mcp"
}
}
} {
"servers": {
"com-hydrafetch-web": {
"type": "http",
"url": "https://api.hydrafetch.com/mcp"
}
}
} [mcp_servers.com-hydrafetch-web] url = "https://api.hydrafetch.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-hydrafetch-web": {
"type": "remote",
"url": "https://api.hydrafetch.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-hydrafetch-web --url 'https://api.hydrafetch.com/mcp' --transport streamable-http
mcp_servers:
com-hydrafetch-web:
url: "https://api.hydrafetch.com/mcp" {
"McpServers": {
"com-hydrafetch-web": {
"Transport": "http",
"Url": "https://api.hydrafetch.com/mcp"
}
}
} assistant mcp add com-hydrafetch-web -t streamable-http -u 'https://api.hydrafetch.com/mcp'
{
"mcpServers": {
"com-hydrafetch-web": {
"type": "http",
"url": "https://api.hydrafetch.com/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.
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 6 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 20 Sept 2026 · Probed https://api.hydrafetch.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hydrafetch.com | CN=WE1,O=Google Trust Services,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 116691b555ee080e50b1b033156fb1 |
| SANs: hydrafetch.com, *.hydrafetch.com | ||||||
| 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 secure
Validation of api.hydrafetch.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hydrafetch.com. | present | 2371 | 13 | Verified |
| api.hydrafetch.com. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.hydrafetch.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://api.hydrafetch.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://api.hydrafetch.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.hydrafetch.com/mcp |
| Authorisation server | https://api.hydrafetch.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.hydrafetch.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.hydrafetch.com/mcp | HTTPS enforced | 301 | https://api.hydrafetch.com/mcp |
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 →
batch Batch ~44
Scrape a list of URLs you already have as one job. Returns a batch id straight away; read it with batch_status.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | The URLs to scrape. |
No output schema declared.
No examples provided.
batch_status Batch status ~40
Read a batch started with batch: how far it has got, and the results so far.
| Name | Type | Req | Description |
|---|---|---|---|
| batchId | string | yes | The id returned by batch. |
No output schema declared.
No examples provided.
brand Brand ~68
A company's brand from its domain: logos for light and dark backgrounds, its real colours, name, description and socials. Answers 'what is this company' far better than a raw page dump.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The company domain, e.g. stripe.com. A full URL works too. |
No output schema declared.
No examples provided.
crawl Crawl ~78
Discover and scrape a whole site as one job. Returns a crawl id straight away; read it with crawl_status. Use this instead of calling scrape in a loop.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum pages to scrape. |
| maxDepth | integer | – | How far from the seed to follow. |
| url | string | yes | The site to start from. |
No output schema declared.
No examples provided.
crawl_status Crawl status ~41
Read a crawl started with crawl: how far it has got, and the pages it has scraped.
| Name | Type | Req | Description |
|---|---|---|---|
| crawlId | string | yes | The id returned by crawl. |
No output schema declared.
No examples provided.
extract Extract ~84
Pull typed structured data from one or more URLs by JSON schema or prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| preferStructure | boolean | – | Keep headings, lists and tables in the text handed to the model. |
| prompt | string | – | Natural-language description of what to pull. |
| schema | object | – | A JSON schema the result must conform to. |
| urls | array | yes | The URLs to extract from. |
No output schema declared.
No examples provided.
images Images ~51
Harvest a page's images with their metadata, without rendering it. Cheaper than a screenshot and returns the source images rather than a picture of the page.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The page to harvest images from. |
No output schema declared.
No examples provided.
logo Logo ~115
A company's logo as a directly embeddable image URL, chosen for the background you name. Use this rather than brand when the mark is all you need — it costs a fifth as much and returns one asset instead of the whole record.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The company domain, e.g. stripe.com. A full URL works too. |
| theme | string | – | The background the logo will sit on. Defaults to light. |
| type | string | – | The square mark, or the full logotype. Defaults to icon. |
No output schema declared.
No examples provided.
map Map ~45
Enumerate a site's URLs from its sitemap and links, without scraping them.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max URLs to return. |
| url | string | yes | The seed URL to map. |
No output schema declared.
No examples provided.
scrape Scrape ~103
Turn a URL into clean, LLM-ready markdown and structured data.
| Name | Type | Req | Description |
|---|---|---|---|
| formats | array | – | Which outputs to return. Defaults to markdown. |
| preferStructure | boolean | – | Keep headings, lists and tables as markdown. Default false optimises for raw content and can return unstructured text on marketing and listing pages. Turn on when the document structure matters, or r… |
| url | string | yes | The URL to scrape. |
No output schema declared.
No examples provided.
screenshot Screenshot ~228
Render a page in a real browser and capture a PNG, returning its public URL. Use when the question is what the page looks like rather than what it says.
| Name | Type | Req | Description |
|---|---|---|---|
| fullPage | boolean | – | Capture the whole scrollable page rather than the viewport. |
| maxAge | integer | – | Reuse a stored screenshot younger than this many milliseconds. Defaults to 7 days, so a repeat returns the stored PNG without re-rendering and without applying waitFor. Pass 0 to force a fresh captur… |
| timeout | integer | – | Overall time budget for the capture, in milliseconds. |
| url | string | yes | The URL to capture. |
| viewport | string | – | Screen size to render at. Defaults to desktop (1920x1080). Ignored when width or height are given. |
| viewportHeight | integer | – | Exact viewport height in pixels. Overrides viewport. With fullPage the capture still extends to the full page height. |
| viewportWidth | integer | – | Exact viewport width in pixels. Overrides viewport. |
| waitFor | integer | – | Extra milliseconds to let the page settle before capture. |
No output schema declared.
No examples provided.
search Search ~105
Search the web and return ranked results: title, url and snippet. Set scrapeResults to also fetch each result as markdown, at 1 extra credit per page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 5). |
| preferStructure | boolean | – | Keep headings, lists and tables in each scraped result. |
| query | string | yes | The search query. |
| scrapeResults | boolean | – | Also scrape each result to markdown, 1 extra credit per page (default false). |
No output schema declared.
No examples provided.
styleguide Styleguide ~75
A site's design system read from computed styles in a real browser: colours by role with contrast ratios, the type scale, corner radius and button styling. Values defined through CSS variables come back resolved to the hex actually painted.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to read, e.g. stripe.com. A full URL works too. |
No output schema declared.
No examples provided.
What is the Hydrafetch MCP server?
Hydrafetch is an MCP server listed in the public MCP registry as com.hydrafetch/web. Turn any URL into clean Markdown and structured data. Scrape, crawl, search and extract. This page covers its hosted endpoint (https://api.hydrafetch.com/mcp).
Is the Hydrafetch MCP server safe to use?
Hydrafetch scores 95 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 Hydrafetch MCP server expose?
Hydrafetch exposes 13 tools: scrape, map, crawl, crawl_status, batch, and 8 more. Their descriptions and schemas cost roughly 1,077 tokens of context every time the server is loaded.
Does the Hydrafetch MCP server require authentication?
Yes. Hydrafetch asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Hydrafetch MCP server still maintained?
Hydrafetch 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.