WebExtract
REMOTE · API.WEBEXTRACT.DEV
Web page to clean Markdown or fixed-schema JSON (product/price, tables). Free 20 calls/day.
Available components
Last scanned (2 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Web Scraping
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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 292 tokens (~146/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +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.
- 31 Oct 26 +4
- DNSSEC: fail → pass ▲ security
- HSTS header: fail → pass ▲ security
- Tool “extract_url” rewrote its description, which is the text the model reads security
- Tool “page_markdown” rewrote its description, which is the text the model reads security
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 129 → 143 ▼ functional
- 24 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “extract_url” rewrote its description, which is the text the model reads security
- Tool “page_markdown” rewrote its description, which is the text the model reads security
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 5 Nov 2026 · Probed https://api.webextract.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=webextract.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5fdb25e69b0114885c7cec5206418e0a062 |
| SANs: *.webextract.dev, webextract.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.webextract.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| webextract.dev. | present | 2371 | 13 | Verified |
| api.webextract.dev. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=86400 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.webextract.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.webextract.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 →
extract_url Extract web page ~79
Fetch a public web page (robots.txt respected) and return clean Markdown plus fixed-schema JSON: article metadata, product/price, tables. HTML only, no JS execution, no PDF. Free 20 calls/day per IP; pass 'Authorization: Bearer <key>' for prepaid credits.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) URL |
| Name | Type | Req | Description |
|---|---|---|---|
| content_source | string | – | Where the content came from: raw_html = the HTTP response body, no JavaScript executed (current behaviour); rendered = after headless rendering (not offered yet) |
| fetched_at | string | yes | – |
| final_url | string | yes | – |
| markdown | string | yes | – |
| markdown_truncated | boolean | – | – |
| metadata | object | yes | – |
| product | object|null | yes | – |
| product_unresolved | object|null | – | Only when product is null: why no product was extracted (e.g. listing_page) |
| schema_version | string | yes | – |
| tables | array | yes | – |
| url | string | yes | – |
| word_count | integer | – | – |
No examples provided.
page_markdown Web page to Markdown ~79
Fetch a public web page (robots.txt respected) and return clean Markdown only. HTML only, no JS execution, no PDF. Cheaper than extract_url (0.4 credit). Free 20 calls/day per IP; pass 'Authorization: Bearer <key>' for prepaid credits.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) URL |
| Name | Type | Req | Description |
|---|---|---|---|
| content_source | string | – | Where the content came from: raw_html = the HTTP response body, no JavaScript executed (current behaviour); rendered = after headless rendering (not offered yet) |
| fetched_at | string | – | – |
| final_url | string | yes | – |
| markdown | string | yes | – |
| markdown_truncated | boolean | – | – |
| title | string|null | – | – |
| url | string | yes | – |
| word_count | integer | – | – |
No examples provided.
How do I install the WebExtract MCP server?
WebExtract is a hosted endpoint at https://api.webextract.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 · api.webextract.dev
claude mcp add --transport http dev-webextract-extract 'https://api.webextract.dev/mcp'
What is the WebExtract MCP server?
WebExtract is an MCP server listed in the public MCP registry as dev.webextract/extract. Web page to clean Markdown or fixed-schema JSON (product/price, tables). Free 20 calls/day. This page covers its hosted endpoint (https://api.webextract.dev/mcp).
Is the WebExtract MCP server safe to use?
WebExtract scores 75 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 WebExtract MCP server expose?
WebExtract exposes 2 tools: extract_url, page_markdown. Their descriptions and schemas cost roughly 158 tokens of context every time the server is loaded.
Does the WebExtract MCP server require authentication?
No. We connected to WebExtract without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WebExtract MCP server still maintained?
WebExtract is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.