PageWire
REMOTE · PAGEWIRE.DEV
Web pages to Markdown, metadata and small crawls for agents. Free daily calls, then USDC x402/MPP.
Available components
Last scanned (4 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 23 Oct 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 Security63
- 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 979 tokens (~326/item across 3 items; 3 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 Management57
- Stability observed for 17 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 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.
- 18 Oct 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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 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.
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 10. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 64
First indexed and scored.
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 23 Oct 2026 · Probed https://pagewire.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pagewire.dev | CN=WE1,O=Google Trust Services,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c7649dafd98ade413001b8064e81f71 |
| SANs: pagewire.dev, *.pagewire.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 pagewire.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| pagewire.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://pagewire.dev/mcp | Verified | 200 | |
| http (plaintext) | http://pagewire.dev/mcp | Served over HTTP | 200 |
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 →
crawl_site Read a page + 4 linked pages ($0.03/call) ~299
Fetch a public web page plus up to 4 pages on the same host that it links to (in link order, or only those whose path starts with `prefix`), and return each one as title + clean Markdown. Good for reading a docs section or a small site in one call. No model call, deterministic. For a single page use page_to_markdown (cheaper), for metadata only use page_metadata. Plain HTTP fetch (no JavaScript rendering, 15 s timeout, only the first 2 MB is read). Errors (non-public URL, upstream HTTP error, timeout, non-text content) return isError with the reason and are never charged. Price: $0.03 USDC per call via x402 (USDC on Base or Solana, no account; nothing is charged for a bad input). First $0.1 of calls per day per client are free (no payment needed).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Linked pages to read (default 4) |
| payment | string | – | x402 payment: the base64 PAYMENT-SIGNATURE value (x402 v2 payment payload signed for one entry of the `accepts` list returned when this tool is called without it). Omit to get the price and payment r… |
| prefix | string | – | Only follow links whose path starts with this, e.g. /docs/ |
| url | string | yes | Public http(s) page to fetch |
No output schema declared.
No examples provided.
page_metadata Web page metadata ($0.005/call) ~247
Fetch a public web page and return its metadata: title, description, canonical URL, language, OpenGraph and Twitter card tags, icons and parsed JSON-LD blocks. Use it for link previews, SEO checks or structured data (JSON-LD) without the page body; use page_to_markdown when you need the readable text and links. Plain HTTP fetch (no JavaScript rendering, 15 s timeout, only the first 2 MB is read). Errors (non-public URL, upstream HTTP error, timeout, non-text content) return isError with the reason and are never charged. Price: $0.005 USDC per call via x402 (USDC on Base or Solana, no account; nothing is charged for a bad input). First $0.1 of calls per day per client are free (no payment needed).
| Name | Type | Req | Description |
|---|---|---|---|
| payment | string | – | x402 payment: the base64 PAYMENT-SIGNATURE value (x402 v2 payment payload signed for one entry of the `accepts` list returned when this tool is called without it). Omit to get the price and payment r… |
| url | string | yes | Public http(s) page to fetch |
No output schema declared.
No examples provided.
page_to_markdown Web page → Markdown ($0.01/call) ~260
Fetch a public web page and return its title, description, clean Markdown (scripts, styles, nav chrome removed) and the list of links. No model call, deterministic. Use it to read the content of one page; use page_metadata if you only need title/OpenGraph/JSON-LD (cheaper), or crawl_site to read the page plus the pages it links to in one call. Plain HTTP fetch (no JavaScript rendering, 15 s timeout, only the first 2 MB is read). Errors (non-public URL, upstream HTTP error, timeout, non-text content) return isError with the reason and are never charged. Price: $0.01 USDC per call via x402 (USDC on Base or Solana, no account; nothing is charged for a bad input). First $0.1 of calls per day per client are free (no payment needed).
| Name | Type | Req | Description |
|---|---|---|---|
| payment | string | – | x402 payment: the base64 PAYMENT-SIGNATURE value (x402 v2 payment payload signed for one entry of the `accepts` list returned when this tool is called without it). Omit to get the price and payment r… |
| url | string | yes | Public http(s) page to fetch |
No output schema declared.
No examples provided.
How do I install the PageWire MCP server?
PageWire is a hosted endpoint at https://pagewire.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 · pagewire.dev
claude mcp add --transport http dev-pagewire-web 'https://pagewire.dev/mcp'
What is the PageWire MCP server?
PageWire is an MCP server listed in the public MCP registry as dev.pagewire/web. Web pages to Markdown, metadata and small crawls for agents. Free daily calls, then USDC x402/MPP. This page covers its hosted endpoint (https://pagewire.dev/mcp).
Is the PageWire MCP server safe to use?
PageWire scores 71 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 PageWire MCP server expose?
PageWire exposes 3 tools: page_to_markdown, page_metadata, crawl_site. Their descriptions and schemas cost roughly 806 tokens of context every time the server is loaded.
Does the PageWire MCP server require authentication?
No. We connected to PageWire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PageWire MCP server still maintained?
PageWire is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.