pagenull/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAGENULL_API_KEY | Yes | Your API key from the pagenull dashboard (https://pagenull.dev/dashboard/keys). Needed for everything except verify_receipt. | |
| PAGENULL_API_BASE | No | Optional. Base URL of the pagenull API. Default https://api.pagenull.dev. | https://api.pagenull.dev |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| render_pdfA | Turn HTML or a public URL into a PDF with pagenull. Send exactly one of html or url. Returns the PDF (base64, or written to save_to), its signed receipt, warnings and quota. Nothing is stored by pagenull. |
| screenshotA | Render HTML or a public URL to a PNG or JPEG image. Send exactly one of html or url. Returns the image (or writes it to save_to). Nothing is stored by pagenull. |
| list_templatesA | List your saved templates (ids and names) and the built-in ones (invoice, receipt, certificate, report). |
| render_templateA | Render a saved or built-in template with JSON data into a PDF. Returns it like render_pdf. |
| verify_receiptA | Check a pagenull receipt's Ed25519 signature with pagenull's published key, and optionally that a file is the exact output it describes. Give the file as file_path, pdf_base64 or its sha256. The file never leaves this machine. |
| get_usageB | This month's render count, limit, what's left and the rate limit for your plan. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools are clearly distinct by action and resource, but render_pdf and render_template both produce PDFs and require the agent to distinguish between HTML/URL input versus template/data input. The descriptions make the boundary clear enough, though the overlap is the main source of potential misselection.
The set mostly follows a verb_noun pattern: get_usage, render_pdf, list_templates, render_template, verify_receipt. The only notable deviation is screenshot, which is a single noun/verb rather than verb_noun, but it remains readable and idiomatic.
Six tools is well-scoped for a focused PDF rendering and verification service. Each tool earns its place, and the set avoids unnecessary surface area.
Core workflows are covered: usage, PDF rendering from HTML/URL, screenshots, template listing and rendering, and receipt verification. The main gap is template lifecycle management, since agents can list and render templates but cannot create, update, or delete saved templates through this MCP surface.