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.

io.github.atarkowska/fastmcp-pdftools

PYPI · FASTMCP-PDFTOOLS

An MCP server that provides [describe what your server does]

Available components

0 this week 83 Trust /100

Last scanned (17 hours ago)

Scores higher than 86% of PyPI servers

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 16 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency31
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 313 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 71 tokens (~35/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 31 Oct 26 +1
    • Stability: 0.97 → pass security
  • 30 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 +1
    • Stability: 0.97 → pass security
  • 23 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 21 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 20 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 17 Oct 26 +1
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

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

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 5 Nov 2026 · Analysed pypi/fastmcp-pdftools@0.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 16 packages
Packages resolved 16
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~71 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
list_pdf_files ~36

List all PDF files in a given directory.

NameTypeReqDescription
directorystring–Directory path to search for PDFs (default: current directory)

Structured output declared, but exposes no named fields.

No examples provided.

read_local_pdf ~35

Read and extract text content from a local PDF file.

NameTypeReqDescription
pathstringyesAbsolute or relative path to the PDF file

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.atarkowska/fastmcp-pdftools MCP server?

io.github.atarkowska/fastmcp-pdftools runs locally as a PyPI package, launched with uvx fastmcp-pdftools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · fastmcp-pdftools

# add to Claude Code
claude mcp add atarkowska-fastmcp-pdftools -- uvx fastmcp-pdftools
Common questions

What is the io.github.atarkowska/fastmcp-pdftools MCP server?

io.github.atarkowska/fastmcp-pdftools is an MCP server listed in the public MCP registry as io.github.atarkowska/fastmcp-pdftools. An MCP server that provides [describe what your server does]. This page covers its PyPI package (fastmcp-pdftools).

Is the io.github.atarkowska/fastmcp-pdftools MCP server safe to use?

io.github.atarkowska/fastmcp-pdftools scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.atarkowska/fastmcp-pdftools MCP server expose?

io.github.atarkowska/fastmcp-pdftools exposes 2 tools: read_local_pdf, list_pdf_files. Their descriptions and schemas cost roughly 71 tokens of context every time the server is loaded.

Is the io.github.atarkowska/fastmcp-pdftools MCP server still maintained?

io.github.atarkowska/fastmcp-pdftools is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.atarkowska/fastmcp-pdftools MCP server?

VerifyMCP ran 15 checks on io.github.atarkowska/fastmcp-pdftools, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.atarkowska/fastmcp-pdftools: License. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.