Skip to content

Zovo Photo to PDF MCP server

io.github.theluckystrike/image-to-pdftheluckystrikestreamable-httpv1.0.0Scanned

Turns JPG and PNG images into one PDF document.

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

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.
Govern this server →

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 Photo to PDF MCP server can do

The Zovo Photo to PDF MCP server is published by the GitHub account theluckystrike. It has 2 tools. It can create or change data (1 tool: images_to_pdf), but cannot delete data. 1 tool only reads.

1 tool reads private data (inspect_images); 1 tool brings in text other people can write (inspect_images).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

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
  • images_to_pdfUse this when the user wants to convert JPG to PDF, PNG to PDF, combine photos into one PDF, turn scanned pages or phone photos of documents into a PDF, or make a PDF from pictures…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Use this when the user wants to convert JPG to PDF, PNG to PDF, combine photos into one PDF, turn scanned pages or phone photos of documents into a PDF, or make a PDF from pictures or screenshots. It places 1 to 60 JPG or PNG images in the given order, one per page, turns each photo upright from its EXIF orientation, and returns a PDF download that is kept for about 1 hour. Page size fit (each page matches its image), letter, a4 or legal; orientation auto, portrait or landscape; margin 0 to 25 mm; fit contain or cover. Does not read HEIC, WebP, GIF or TIFF (the result says how to export them), does not run OCR and does not edit pixels. Do not use for merging existing PDF files or for converting a PDF into images.

    Annotations the server declares

    • title: Images to PDF
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
Only reads 1Show 1 read-only tool
  • inspect_imagesUse this when the user wants to check photos or scans before making a PDF: it lists each attached JPG or PNG with its type, pixel size, EXIF orientation and the rotation it needs, …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "inspect_images" says "inspect": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe description's first sentence says "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Use this when the user wants to check photos or scans before making a PDF: it lists each attached JPG or PNG with its type, pixel size, EXIF orientation and the rotation it needs, DPI, colour mode, and the page size it would get, and flags files that are not usable (HEIC, WebP, GIF, TIFF, damaged or too large). Makes no file. Takes the same page options as images_to_pdf. Do not use for reading text in an image (no OCR) or for editing images.

    Annotations the server declares

    • title: Inspect images
    • 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.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:23 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.

    Matched text

    https://image-to-pdf.zovo.one/mcp: tools/list returned 2 tools to an anonymous client, including images_to_pdf (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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 image-to-pdf https://image-to-pdf.zovo.one/mcp
claude mcp add --transport http image-to-pdf https://image-to-pdf.zovo.one/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__image-to-pdf__inspect_images"
    ],
    "ask": [
      "mcp__image-to-pdf__images_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 image-to-pdf. Review it before you use it.

Capability tags behind 1 rule
  • mcp__image-to-pdf__inspect_images 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/image-to-pdf/verify?hash=6447709839e463b1164c27a59a9cca5b334603d0a9064edef05330077df4f678" | jq -e '.changed == false'

Pinned hash 6447709839e4, from Nov 8, 2026, 02:18 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/image-to-pdf/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/image-to-pdf
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/image-to-pdf.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/image-to-pdf)

Source: MCP Registry. Synced Nov 8, 2026, 03:17 UTC.

Zovo Photo to PDF MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Zovo Photo 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 0 findings 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 Photo 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 Photo 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 Photo to PDF MCP server have?

2 tools: 1 write, 1 read. images_to_pdf and inspect_images.

Does the Zovo Photo 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 Photo 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 Photo to PDF MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.