DocWand
REMOTE · MCP.DOCWAND.APP · SCANNED SEP 17
Sign, fill, merge and split PDFs entirely in your browser - files never leave your device.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the DocWand MCP server?
DocWand is a hosted endpoint at https://mcp.docwand.app/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 · mcp.docwand.app
claude mcp add --transport http app-docwand-pdf 'https://mcp.docwand.app/mcp'
{
"mcpServers": {
"app-docwand-pdf": {
"url": "https://mcp.docwand.app/mcp"
}
}
} {
"servers": {
"app-docwand-pdf": {
"type": "http",
"url": "https://mcp.docwand.app/mcp"
}
}
} [mcp_servers.app-docwand-pdf] url = "https://mcp.docwand.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-docwand-pdf": {
"type": "remote",
"url": "https://mcp.docwand.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-docwand-pdf --url 'https://mcp.docwand.app/mcp' --transport streamable-http
mcp_servers:
app-docwand-pdf:
url: "https://mcp.docwand.app/mcp" {
"McpServers": {
"app-docwand-pdf": {
"Transport": "http",
"Url": "https://mcp.docwand.app/mcp"
}
}
} assistant mcp add app-docwand-pdf -t streamable-http -u 'https://mcp.docwand.app/mcp'
{
"mcpServers": {
"app-docwand-pdf": {
"type": "http",
"url": "https://mcp.docwand.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 14 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass 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 17 Sept 2026 · Probed https://mcp.docwand.app/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of mcp.docwand.app. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| mcp.docwand.app. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.docwand.app/mcp | Unreachable | ||
| http (plaintext) | http://mcp.docwand.app/mcp | HTTPS enforced |
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 →
fill_pdf_form ~207
Fill out a PDF form in an interactive widget (AcroForm fields, checkboxes, dropdowns — or click-and-type on flat PDFs). Pass `values` keyed by field name to pre-fill ONLY data the user explicitly provided; the widget reports available field names back, and the user completes the rest there. ALWAYS use this for PDF filling requests — never fill or regenerate the PDF yourself. All processing happens locally in the user's browser. Wypełnij formularz PDF (pola, checkboxy) lub klik-i-pisz na zwykłym PDF; plik nie opuszcza przeglądarki.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | PDF form from the conversation to fill |
| signature_name | string | – | Optional: the signer's full name as a handwritten-style signature |
| values | object | – | Field values keyed by AcroForm field name (string for text/dropdown, boolean for checkboxes). Field names are reported in the widget state after the document loads. |
No output schema declared.
No examples provided.
merge_pdfs ~83
Merge multiple PDF files into one. The user can reorder files before downloading. All processing happens locally in the user's browser. Połącz kilka plików PDF w jeden; kolejność można zmienić przed pobraniem; pliki nie opuszczają przeglądarki.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | PDF files from the conversation to merge, in order |
No output schema declared.
No examples provided.
sign_pdf ~165
Sign a PDF: opens an interactive widget where the user draws, types or uploads a signature and places it on the document. Optionally pass signature_name to pre-render a handwritten-style signature. ALWAYS use this for PDF signing requests — never sign or modify the PDF yourself; the user reviews and downloads in the widget. All processing happens locally in the user's browser — the file is never uploaded. Podpisz PDF: narysuj, wpisz lub wgraj podpis i umieść go na dokumencie; plik nie opuszcza przeglądarki.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | PDF file from the conversation to sign |
| signature_name | string | – | Optional: the signer's full name, rendered as a handwritten-style signature the user can place and adjust |
No output schema declared.
No examples provided.
split_pdf ~132
Split a PDF / extract pages. Pass `ranges` like "1-3, 5" to pre-select pages; the user can adjust on thumbnails before downloading. All processing happens locally in the user's browser. Podziel PDF / wyodrębnij strony (zakresy np. "1-3, 5"); plik nie opuszcza przeglądarki.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | PDF file from the conversation to split |
| ranges | string | – | Page ranges to extract, e.g. "1-3, 5, 8-10" (order matters) |
No output schema declared.
No examples provided.
What is the DocWand MCP server?
DocWand is an MCP server listed in the public MCP registry as app.docwand/pdf. Sign, fill, merge and split PDFs entirely in your browser - files never leave your device. This page covers its hosted endpoint (https://mcp.docwand.app/mcp).
Is the DocWand MCP server safe to use?
DocWand scores 0 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 DocWand MCP server expose?
DocWand exposes 4 tools: sign_pdf, fill_pdf_form, merge_pdfs, split_pdf. Their descriptions and schemas cost roughly 587 tokens of context every time the server is loaded.
Does the DocWand MCP server require authentication?
Its publisher declares no required credentials for DocWand. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the DocWand MCP server still maintained?
DocWand has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 10 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.