# WeasyPrint by pagespool (remote · api.pagespool.com)
Hosted WeasyPrint: render HTML and print CSS to PDF, with PDF/A output on the paid plans.
- Trust score: 82/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05
## Components
- remote · `api.pagespool.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-pagespool-weasyprint/mcp-weasyprint.md), [page](https://verifymcp.io/servers/com-pagespool-weasyprint/mcp-weasyprint)
## Channel facts
- Endpoint: `https://api.pagespool.com/mcp/weasyprint/`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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-11-05.
- **Endpoint Security**: 97/100
- The endpoint's TLS certificate is valid, in date, and uses a strong key.
- 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.
- HTTPS is enforced; there's no plaintext access path.
- The HSTS (Strict-Transport-Security) header is present.
- DNSSEC check failed: this domain isn't protected by DNSSEC.
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
- Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
- AI-judged instruction clarity (excellent).
- Context-footprint check failed: tool/resource definitions use about 211 tokens (~211/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
- Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
## Install
### How do I install the WeasyPrint by pagespool MCP server?
WeasyPrint by pagespool is a hosted endpoint at https://api.pagespool.com/mcp/weasyprint/, 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 com-pagespool-weasyprint 'https://api.pagespool.com/mcp/weasyprint/'
```
### Cursor
```json
{
"mcpServers": {
"com-pagespool-weasyprint": {
"url": "https://api.pagespool.com/mcp/weasyprint/"
}
}
}
```
### VS Code
```json
{
"servers": {
"com-pagespool-weasyprint": {
"type": "http",
"url": "https://api.pagespool.com/mcp/weasyprint/"
}
}
}
```
### Codex
```toml
[mcp_servers.com-pagespool-weasyprint]
url = "https://api.pagespool.com/mcp/weasyprint/"
```
### opencode
```json
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-pagespool-weasyprint": {
"type": "remote",
"url": "https://api.pagespool.com/mcp/weasyprint/",
"enabled": true
}
}
}
```
### OpenClaw
```bash
openclaw mcp add com-pagespool-weasyprint --url 'https://api.pagespool.com/mcp/weasyprint/' --transport streamable-http
```
### Hermes
```yaml
mcp_servers:
com-pagespool-weasyprint:
url: "https://api.pagespool.com/mcp/weasyprint/"
```
### Netclaw
```json
{
"McpServers": {
"com-pagespool-weasyprint": {
"Transport": "http",
"Url": "https://api.pagespool.com/mcp/weasyprint/"
}
}
}
```
### Vellum
```bash
assistant mcp add com-pagespool-weasyprint -t streamable-http -u 'https://api.pagespool.com/mcp/weasyprint/'
```
### Other
```json
{
"mcpServers": {
"com-pagespool-weasyprint": {
"type": "http",
"url": "https://api.pagespool.com/mcp/weasyprint/"
}
}
}
```
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-11-05 (score 82, +7)
- [security improvement] Authorization: partial → pass
- [security] First check of Authorization: pass
- [functional improvement] Stability: unverified → 0.03
### 2026-11-04 (score 75)
First indexed and scored.
## MCP tools (1)
### `render_pdf` (~211 tokens)
Render an HTML document to a PDF
Render up to 256 KB of HTML to a PDF with WeasyPrint. Returns a download link.
Give the user the `download_url` so they can open the PDF. The link
works for 15 minutes; after that, render again. The result is
\`{"download_url": "", "pages": , "size_bytes": ,
"expires_in_minutes": 15}`.
Only HTML and CSS are rendered; JavaScript is not run.
For documents larger than 256 KB, use the REST API
(`POST /v1/weasyprint/render`).
Credits: 1 per call.
Input parameters:
- `html` (string, required): A complete HTML document, up to 256 KB. Inline images, fonts and CSS as data: URIs; external resources are not loaded.
- `pdf_variant`: Write the PDF as PDF/A-2b or PDF/A-3b, for archiving. Paid plans only. Leave it out for a regular PDF.
## Diagnostics
Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-pagespool-weasyprint/mcp-weasyprint#diagnostics
## Score history
- 2026-11-05: 82
- 2026-11-04: 75
## Common questions
### What is the WeasyPrint by pagespool MCP server?
WeasyPrint by pagespool is an MCP server listed in the public MCP registry as com.pagespool/weasyprint. Hosted WeasyPrint: render HTML and print CSS to PDF, with PDF/A output on the paid plans. This page covers its hosted endpoint (https://api.pagespool.com/mcp/weasyprint/).
### Is the WeasyPrint by pagespool MCP server safe to use?
WeasyPrint by pagespool scores 82 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 WeasyPrint by pagespool MCP server expose?
WeasyPrint by pagespool exposes 1 tool: render_pdf. Their descriptions and schemas cost roughly 211 tokens of context every time the server is loaded.
### Does the WeasyPrint by pagespool MCP server require authentication?
Yes. WeasyPrint by pagespool 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 WeasyPrint by pagespool MCP server still maintained?
WeasyPrint by pagespool 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.
## Links
- Remote endpoint: https://api.pagespool.com/mcp/weasyprint/
- Website: https://pagespool.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-pagespool-weasyprint/mcp-weasyprint.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pagespool-weasyprint/mcp-weasyprint.json
- HTML version of this page: https://verifymcp.io/servers/com-pagespool-weasyprint/mcp-weasyprint