Skip to content
External endpointresponds

DocWand

Sign, fill, merge and split PDFs entirely in your browser - files never leave your device.

Endpoint URL
https://mcp.docwand.app/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:03 AM UTC
Check
MCP initialize · 8s limit
Latency
229 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
app.docwand/pdf

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
docwand-mcp
Version
0.1.0
Capability keys
tools, resources
Tool names
sign_pdf, fill_pdf_form, merge_pdfs, split_pdf
Instructions excerpt

DocWand signs, fills, merges and splits PDFs ENTIRELY inside an interactive widget running in the user's browser. The document never leaves their device. Hard rules: 1. For ANY request to sign, fill, merge or split a PDF, call the matching DocWand tool. NEVER edit, fill, sign, convert or regenerate the PDF yourself (no code execution, no attaching files) — that destroys document integrity and violates the user's privacy expectations. 2. The widget is the workspace: the user reviews everything, completes remaining fields, adjusts the signature and downloads the final file THERE. After a tool call, reply with one short sentence pointing the user to the widget. Do not produce a PDF, do not paste field contents into the chat. 3. fill_pdf_form: after the document loads, the widget reports the available form field names in widget state. To pre-fill, call fill_pdf_form with `values` keyed by those EXACT names — but only values the user explicitly stated or confirmed. Leave everything els

Reported Aug 17, 2026, 05:03 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 145ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 545ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 98ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 229ms