Skip to content

Zovo PDF Form Fill MCP server

io.github.theluckystrike/pdf-form-filltheluckystrikestreamable-httpv1.0.0Scanned

List and fill the fields of a PDF form document from your answers in the chat.

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 · 0
  • 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.
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 PDF Form Fill MCP server can do

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

1 tool reads private data (list_form_fields).

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
  • fill_pdf_formUse this when the user wants to fill in a fillable PDF form with given answers.1 finding

    Why it is in this group

    • The name "fill_pdf_form" says "fill": 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 "fill_pdf_form" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "fill_pdf_form" says "fill": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Use this when the user wants to fill in a fillable PDF form with given answers. Pass the attached PDF and a list of {field, value} using the field names from list_form_fields: text for text fields, true/false for checkboxes, one listed option for radio groups and dropdowns (case-insensitive matches are reported), a list for multi-select list boxes. Unknown names, options that are not listed and text over a field's maximum length are refused with the reason, and nothing is filled. Returns a new filled PDF (fields editable, or flattened when flatten is true), read back to confirm each value, plus required fields still empty. Does not sign signature fields, does not change the user's original file, and does not fill XFA-only forms.

    Annotations the server declares

    • title: Fill a PDF form
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
Only reads 1Show 1 read-only tool
  • list_form_fieldsUse this when the user attaches a fillable PDF form and wants to see its fields or wants it filled.Reads private dataNo findings

    Why it is in this group

    • The name "list_form_fields" says "list": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.file), and the tool reads: it reads files.
    Description, as the server wrote it
    Use this when the user attaches a fillable PDF form and wants to see its fields or wants it filled. It returns each AcroForm field with its full name, type (text, checkbox, radio, dropdown, listbox, signature), current value, options, required flag, maximum length, page and the printed label next to it, 40 fields at a time (use start for more). Does not change the PDF. Does not read XFA-only forms or scanned paper forms with no fields.

    Annotations the server declares

    • title: List PDF form fields
    • 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 untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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: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.

    Matched text

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

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "fill_pdf_form" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "fill_pdf_form" says "fill": a word for a change.

    What this check looks for

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 pdf-form-fill https://pdf-form-fill.zovo.one/mcp
claude mcp add --transport http pdf-form-fill https://pdf-form-fill.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__pdf-form-fill__list_form_fields"
    ],
    "ask": [
      "mcp__pdf-form-fill__fill_pdf_form"
    ],
    "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 pdf-form-fill. Review it before you use it.

Capability tags behind 1 rule
  • mcp__pdf-form-fill__list_form_fields private-data

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/pdf-form-fill/verify?hash=689eca66cc5aae9fb359e84641fdc8320bc261e618ee85fd2173015a3a66208b" | jq -e '.changed == false'

Pinned hash 689eca66cc5a, 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/pdf-form-fill/changes.xml

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

Badge

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

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

Zovo PDF Form Fill MCP server: questions and answers

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

Is the Zovo PDF Form Fill 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 PDF Form Fill 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 PDF Form Fill 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 PDF Form Fill MCP server have?

2 tools: 1 write, 1 read. fill_pdf_form and list_form_fields.

Does the Zovo PDF Form Fill MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

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

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