REPORT 01M7CNXWJP3MTFWK03YS3P3K3H · checks-v2

PdfPecker MCP server: automated checks

What HostedMCP checked on 14 Nov 2026, 09:24 UTC for pdfpecker 1.25.0. Every result links to the public source it came from, so you can check it yourself.

Passed HostedMCP checks v2

93/100

8 of 11 checks ran · 0 high findings · not a security audit

Checked: 14 Nov 2026, 09:24 UTC
Commit: —
Package: pypi · 1.25.0
Methodology: checks-v2

Origin

25 / 30 points

Source repository linked and reachable10 pts
moonwalker1307/pdfpecker.python is public and reachable
github.com/moonwalker1307/pdfpecker.python ↗
Pass
Package names this repository as its source5 pts
pdfpecker names https://github.com/Moonwalker1307/PdfPecker as its source
pypi.org/project/pdfpecker/ ↗
Finding
Build provenance (Sigstore attestation)10 pts
Sigstore attestation for pdfpecker
pypi.org/project/pdfpecker/ ↗
Pass
Open source license (OSI)5 pts
MIT
spdx.org/licenses/MIT.html ↗
Pass

Practices

5 / 5 points

Commit or release in the last year5 pts
Last commit or release 2026-11-12
github.com/moonwalker1307/pdfpecker.python ↗
Pass
OpenSSF Scorecard15 pts
Not checked

Supply chain

25 / 25 points

Package name not close to a popular package10 pts
No popular package one edit away from pdfpecker
Pass
No critical advisory in the package or its dependencies15 pts
the package checked; no critical advisory
osv.dev ↗
Pass

Tool safety

15 / 15 points

No hidden instructions to the model15 pts
0 tool descriptions and the README read; no override phrases, credential paths or hidden characters
Pass
Destructive tools are labelled5 pts
Not checked

Endpoint

not checked

Remote endpoint answers the MCP handshake5 pts
Not checked

What these checks do not cover

The server's code is not run and its logic is not audited.
Results describe the state on the date above and pdfpecker 1.25.0; a later release can differ.
A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.