Zovo Word to PDF MCP server
io.github.theluckystrike/word-to-pdftheluckystrikestreamable-httpv1.0.0Scanned
Word .docx files to PDF
2 tools: 1 change things and 1 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Zovo Word to PDF MCP server can do
The Zovo Word to PDF MCP server is published by the GitHub account theluckystrike. It has 2 tools. It can create or change data (1 tool: convert_word_to_pdf), but cannot delete data. 1 tool only reads.
1 tool reads private data (inspect_word); 1 tool brings in text other people can write (inspect_word).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
convert_word_to_pdfUse this when the user uploads a Word .docx file and wants it as a PDF.1 finding
Why it is in this group
- The name "convert_word_to_pdf" says "convert": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "convert_word_to_pdf" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "convert_word_to_pdf" says "convert": a word for a change.
Description, as the server wrote it Use this when the user uploads a Word .docx file and wants it as a PDF. Carries headings, paragraphs with alignment, bold, italic, underline, strikethrough, text sizes, links, bulleted and numbered lists with Word's numbers (decimal, letter and roman styles; other number styles print as digits and are listed as not carried), simple tables (merged cells, repeated header rows), JPEG and PNG images, page breaks, the page size and margins; footnotes and endnotes are printed at the end and tracked changes are accepted. Returns the PDF link, a read-back check of the PDF text, table cells, images and page size, and a list of each element type not carried (text boxes, shapes, charts, headers, footers, comments) with counts. Does not read .doc, password-protected or macro-enabled files, and does not keep fonts or colors. The link expires in about 1 hour.
Annotations the server declares
- title: Convert Word to PDF
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
Only reads 1Show 1 read-only tool
inspect_wordUse this when the user wants to know what a Word .docx file contains before converting it: counts of headings, paragraphs, list items, tables, cells, images, footnotes and sections…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "inspect_word" says "inspect": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
- private-dataThe input names a file (input.file), and the tool reads: it reads files.
- untrusted-inputThe description's first sentence says "comment": it reads comments, which other people can write.
Description, as the server wrote it Use this when the user wants to know what a Word .docx file contains before converting it: counts of headings, paragraphs, list items, tables, cells, images, footnotes and sections, the page size and margins, and which element types would not be carried into a PDF (text boxes, shapes, charts, headers, footers, comments) with counts. Makes no PDF and does not edit the file.
Annotations the server declares
- title: Inspect Word file
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:24 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://word-to-pdf.zovo.one/mcp: tools/list returned 2 tools to an anonymous client, including convert_word_to_pdf (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "convert_word_to_pdf" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "convert_word_to_pdf" says "convert": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http word-to-pdf https://word-to-pdf.zovo.one/mcpclaude mcp add --transport http word-to-pdf https://word-to-pdf.zovo.one/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__word-to-pdf__inspect_word"
],
"ask": [
"mcp__word-to-pdf__convert_word_to_pdf"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as word-to-pdf. Review it before you use it.
Capability tags behind 1 rule
- mcp__word-to-pdf__inspect_word private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/word-to-pdf/verify?hash=7ce314733880c20d09c79a19770c36d76d7621435f11e1ee6773919e9a87647b" | jq -e '.changed == false'Pinned hash 7ce314733880, from Nov 8, 2026, 02:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.theluckystrike/word-to-pdf/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/word-to-pdf)Source: MCP Registry. Synced Nov 8, 2026, 03:18 UTC.
Zovo Word to PDF MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Zovo Word to PDF MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Zovo Word to PDF MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Zovo Word to PDF MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Zovo Word to PDF MCP server have?
- 2 tools: 1 write, 1 read. convert_word_to_pdf and inspect_word.
Does the Zovo Word to PDF MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Zovo Word to PDF MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Zovo Word to PDF MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.