Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DocMorph Studio

REMOTE · DOCMORPH.DEV · 2 COMPONENTS

Render Mermaid diagrams, Markdown to PDF and outlines, image OCR, and media metadata cleanup.

64 Trust /100

Last scanned (13 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Documents and Files

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1848 tokens (~168/item across 11 items; 11 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 Management20
  • Stability observed for 6 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "word_remove_password" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 11 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
Changelog

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 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 −2
    • Schema quality: pass → fail ▼ functional
    • Destructive annotations: pass → 0 functional
    • New tool “word_protect” functional
    • New tool “word_remove_password” functional
    • New tool “word_inspect_security” functional
  • 13 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 64

    First indexed and scored.

Diagnostics

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 18 Oct 2026 · Probed https://docmorph.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=docmorph.dev CN=YE1,O=Let's Encrypt,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA384 6ea0f1fdc515c0fdc151e56cb62851140bd
SANs: *.docmorph.dev, docmorph.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of docmorph.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
docmorph.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
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://pagead2.googlesyndication.com https://www.google.com https://www.googletagmanager.com https://adservice.google.com https://ep2.adtrafficquality.google https://hm.baidu.com https://s9.cnzz.com https://cpro.baidustatic.com https://cdn.jsdelivr.net https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; media-src 'self' data: blob:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://pagead2.googlesyndication.com https://www.google.com https://ep2.adtrafficquality.google https://hm.baidu.com https://cdn.jsdelivr.net https://tessdata.projectnaptha.com https://raw.githubusercontent.com https://cloudflareinsights.com blob:; worker-src 'self' blob: https://cdn.jsdelivr.net; frame-ancestors 'self'; object-src 'none'; base-uri 'self';
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(self), microphone=(), geolocation=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://docmorph.dev/mcp Verified 200
http (plaintext) http://docmorph.dev/mcp HTTPS enforced 301 https://docmorph.dev/mcp
MCP tools · 11 exposed · ~1,848 tokens

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 →

Tool Tokens
assist_ocr_text ~59

AI assistant to translate, proofread, or summarize extracted OCR document text.

NameTypeReqDescription
actionstringyesAI action to perform
targetLangstring–Target language for translation
textstringyesExtracted text content

No output schema declared.

No examples provided.

convert_markdown_to_pdf ~86

Compile Markdown text into a styled, publication-ready PDF document with automatic pagination and headers.

NameTypeReqDescription
markdownstringyesMarkdown text to compile
pageSizestring–Page size specification (default: 'A4')
themestring–PDF layout and typography theme (default: 'academic')
titlestring–Document title for the PDF header

No output schema declared.

No examples provided.

extract_markdown_outline ~55

Extract hierarchical headings, table of contents, word/character statistics, and document structure outline from Markdown text.

NameTypeReqDescription
contentstringyesFull Markdown text to analyze
markdownstring–Alternative alias for content property

No output schema declared.

No examples provided.

image_ocr_recognize ~81

Extract multilingual text, complex headings, formulas, and tabular data from images using multimodal AI vision.

NameTypeReqDescription
base64ImagestringyesBase64 encoded image string or data URL
languagestring–Language hint (auto, zh, en, ja, ko, etc.)
modestring–OCR recognition mode

No output schema declared.

No examples provided.

inspect_media_security ~109

Deeply inspect image, video, or audio files for privacy leaks, including GPS physical coordinates, camera/recorder hardware serials, recording timestamps, and editing software signatures.

NameTypeReqDescription
base64DatastringyesBase64 encoded image, video, or audio binary payload (or data URI)
fileNamestring–Optional filename with extension (e.g. photo.jpg, vlog.mp4, interview.mp3)
mediaTypestring–Media classification type (default: auto)

No output schema declared.

No examples provided.

parse_pdf_to_markdown ~56

Extract structured Markdown, tables, and mathematical formulas from a base64 encoded PDF using AI vision OCR.

NameTypeReqDescription
base64PdfstringyesBase64 encoded PDF binary data
fileNamestring–Original filename

No output schema declared.

No examples provided.

render_mermaid_diagram ~114

Render a Mermaid diagram into styled SVG vector image code and node metadata. Supports flowchart/graph and sequenceDiagram (sequence) types. Other types (ER/gantt/mindmap/pie/state) should be rendered on client-side using mermaid.js.

NameTypeReqDescription
syntaxstringyesMermaid chart syntax (e.g. 'graph TD; A[Start]-->B[End];')
themestring–Color palette theme (default: 'default')
titlestring–Optional diagram title

No output schema declared.

No examples provided.

sanitize_media_security ~178

Permanently wipe and sanitize privacy metadata from image, video, or audio files (strip GPS coordinates, device fingerprints, timestamps, and comments) with zero quality loss.

NameTypeReqDescription
base64DatastringyesBase64 encoded image, video, or audio binary payload (or data URI)
clearDevicestring–Whether to erase camera device fingerprints ('true' or 'false', default 'true')
clearGpsstring–Whether to erase GPS coordinates ('true' or 'false', default 'true')
clearTimestampsstring–Whether to zero container recording timestamps ('true' or 'false', default 'true')
fileNamestring–Optional filename with extension (e.g. photo.jpg, vlog.mp4, note.wav)
mediaTypestring–Media classification type (default: auto)

No output schema declared.

No examples provided.

word_inspect_security ~228

Inspect the security and privacy state of a Word .docx: whether it is password-encrypted and with which algorithm, editing restriction mode and whether it is password-protected, presence of a text watermark, and privacy metadata (author, last modified by, company, manager, timestamps, custom properties, comment/revision author names). For encrypted files, pass the password to also inspect the contents. Max input 20MB base64. Privacy: when called remotely (Streamable HTTP / SSE) the file is uploaded to the DocMorph server and processed in memory only; it is not written to disk or retained after processing, and passwords and file contents are never logged. When the MCP server runs locally over stdio, the file is processed entirely on this machine.

NameTypeReqDescription
base64DocxstringyesBase64 encoded .docx binary data (or data URI), encrypted or not
fileNamestring–Optional filename (e.g. report.docx)
passwordstring–Optional open password of an encrypted .docx, to also inspect its contents

No output schema declared.

No examples provided.

word_protect ~675

Protect a Word .docx document in one call: set an open password (Agile AES-256 encryption, opens in Microsoft Word / WPS / LibreOffice), add a native Word text watermark, add copyright info (author/custom property/footer), clean privacy metadata, and restrict editing (read-only / comments only / tracked changes only / forms, optionally password-protected). Returns the protected .docx as base64 plus a summary of applied operations. Max input 20MB base64. Privacy: when called remotely (Streamable HTTP / SSE) the file is uploaded to the DocMorph server and processed in memory only; it is not written to disk or retained after processing, and passwords and file contents are never logged. When the MCP server runs locally over stdio, the file is processed entirely on this machine.

NameTypeReqDescription
base64DocxstringyesBase64 encoded .docx binary data (or data URI). May be an already encrypted .docx if currentPassword is given
cleanPrivacystring–Whether to clean privacy metadata ('true' or 'false', default 'false'). Cleans the items in privacyItems
copyrightAuthorstring–Optional author name written to the document properties (dc:creator / lastModifiedBy)
copyrightFooterstring–Optional copyright line appended to the footer of every section
copyrightTextstring–Optional copyright notice stored as the custom document property 'Copyright'
currentPasswordstring–Only if the input .docx is already password-protected: its current open password, used to unlock it before processing
fileNamestringyesOriginal filename (e.g. report.docx); used to name the output file
openPasswordstring–Optional open password to encrypt the output with (applied last). Omit to leave the file openable without a password
privacyItemsstring–Comma-separated privacy items to clean: author, timestamps, company, customProps, reviewers, or 'all' (default: 'author,company,reviewers'). Setting it implies cleanPrivacy
restrictEditingstring–Restrict editing in Word: readOnly, comments (comments only), trackedChanges (tracked changes only), forms (filling in forms) (default: 'none')
restrictPasswordstring–Optional password required to stop the editing restriction in Word (only with restrictEditing). Without it anyone can stop protection
watermarkColorstring–Watermark color as hex (default: '#C0C0C0')
watermarkFontFamilystring–Watermark font family (default: SimSun for Chinese, MS Mincho for Japanese, otherwise Calibri)
watermarkFontSizestring–Watermark font size in pt (8-200), or 'auto' to fit the page width (default: 'auto')
watermarkLayoutstring–Watermark layout (default: 'diagonal')
watermarkOpacitystring–Watermark opacity from 0.05 to 1 (default: '0.5')
watermarkTextstring–Optional watermark text (max 100 chars), e.g. 'CONFIDENTIAL'. Omit for no watermark. Replaces any existing Word watermark

No output schema declared.

No examples provided.

word_remove_password ~207

Remove the open password from an encrypted Word .docx (Agile encryption, Office 2010+) using the known password, with integrity (HMAC) verification. Returns the decrypted .docx as base64. A wrong password returns a clear WRONG_PASSWORD error; this tool does not crack or guess passwords. Max input 20MB base64. Privacy: when called remotely (Streamable HTTP / SSE) the file is uploaded to the DocMorph server and processed in memory only; it is not written to disk or retained after processing, and passwords and file contents are never logged. When the MCP server runs locally over stdio, the file is processed entirely on this machine.

NameTypeReqDescription
base64DocxstringyesBase64 encoded encrypted .docx binary data (or data URI)
fileNamestring–Optional original filename (e.g. report.docx); used to name the output file
passwordstringyesThe document's current open password

No output schema declared.

No examples provided.

Install

How do I install the DocMorph Studio MCP server?

DocMorph Studio is a hosted endpoint at https://docmorph.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 · docmorph.dev

# add to Claude Code
claude mcp add --transport http dev-docmorph-docmorph-studio 'https://docmorph.dev/mcp'
Common questions

What is the DocMorph Studio MCP server?

DocMorph Studio is an MCP server listed in the public MCP registry as dev.docmorph/docmorph-studio. Render Mermaid diagrams, Markdown to PDF and outlines, image OCR, and media metadata cleanup. This page covers its hosted endpoint (https://docmorph.dev/mcp).

Is the DocMorph Studio MCP server safe to use?

DocMorph Studio scores 64 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 DocMorph Studio MCP server expose?

DocMorph Studio exposes 11 tools: render_mermaid_diagram, extract_markdown_outline, convert_markdown_to_pdf, parse_pdf_to_markdown, image_ocr_recognize, and 6 more. Their descriptions and schemas cost roughly 1,848 tokens of context every time the server is loaded.

Does the DocMorph Studio MCP server require authentication?

No. We connected to DocMorph Studio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DocMorph Studio MCP server still maintained?

DocMorph Studio is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.