KDAN PDF

Connect Claude and ChatGPT to KDAN PDF — upload, edit, compress, protect, redact, and compare PDFs in chat.

MCP Servers Listed MIT

Is KDAN PDF safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.9 / 10
Provenance None
Signed commits 29%
Last push 48d ago
Compare KDAN PDF
Suggest a correction

In detail: KDAN PDF scores 41.9/100 (Grade D), ranked #1174 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.9/10; 29% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How KDAN PDF could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships KDAN PDF and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/KDAN-PDF/KDAN-PDF-MCP, MIT, last pushed 2026-09-23. 29% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.9/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 2
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 10
  3. Published packages None

    No registry package. KDAN PDF is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-29 OSSF Scorecard: 3.1/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues KDAN PDF’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How KDAN PDF compares in MCP Servers

  1. #672 Kolada MCP Server 42.2 +0.3
  2. #673 Adaptive Cards MCP 42.0 +0.1
  3. #674 KDAN PDF 41.9 this agent
  4. #675 Memory MCP 41.8 −0.1
  5. #676 GitMCP 41.7 −0.2

Bars show each HVTrust score; the tick marks KDAN PDF’s 41.9.

Where the 41.9 comes from

HVTrust dimensions vs the MCP Servers average

41.9 / 100 · 100.0% confidence

KDAN PDF MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.1 / 25
5.7 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.0 / 17
1.3 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
8.8 / 20
3.4 below avg 12.2
AdoptionLog-scaled stars · package downloads
4.2 / 20
3.4 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-28
Rank Moved
Rank dropped 12 spots (#1153 → #1165)
2026-10-23
Rank Moved
Rank dropped 30 spots (#1119 → #1149)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 48 days ago. Fresh activity helps separate stable projects from stale ones.
31.3
Activity sub-score · out of 100
#674

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 48 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
57
Forks
2
Last Push
2026-09-23
48 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #1174

Analysis

Activity Inputs

31.3 / 100
StarsRepository reach
10.6 / 30
FreshnessLast push recency
18.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.2 / 20

Common questions about KDAN PDF

Public trust evidence for KDAN PDF is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does KDAN PDF publish package provenance?
No published build provenance is currently detected for KDAN PDF. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does KDAN PDF have an OpenSSF Scorecard?
KDAN PDF has an OpenSSF Scorecard score of 2.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is KDAN PDF actively maintained?
Slowing down. Last push was 48 days ago — keep an eye on whether activity resumes.
What license does KDAN PDF use?
KDAN PDF ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are KDAN PDF's commits signed?
28% of the last 100 commits to KDAN PDF are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
KDAN PDF appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to KDAN PDF's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain KDAN PDF?

For maintainers

HVTrust scores KDAN PDF from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 28Score 2HVTrust 2Scorecard 1Delisted 1Listed 1MCP 1
2026-10-28
Rank Moved
Rank dropped 12 spots (#1153 → #1165)
2026-10-23
Rank Moved
Rank dropped 30 spots (#1119 → #1149)
2026-10-09
Rank Moved
Rank dropped 13 spots (#1062 → #1075)
2026-10-03
Rank Moved
Rank rose 14 spots (#1060 → #1046)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 344 spots (#689 → #1033)
2026-09-23
HVTrust Changed
HVTrust up 14.9pts (31.0 → 45.9)
2026-09-23
Activity Score Changed
Activity score up 9pts (33 → 42)
2026-09-22
Newly Listed
First tracked at rank #689
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Rank Moved
Rank dropped 30 spots (#1054 → #1084)
2026-09-15
Rank Moved
Rank dropped 11 spots (#1052 → #1063)
2026-09-12
Rank Moved
Rank dropped 13 spots (#1038 → #1051)
2026-09-09
Rank Moved
Rank dropped 17 spots (#1015 → #1032)
2026-09-08
Rank Moved
Rank dropped 10 spots (#1005 → #1015)
2026-09-07
Rank Moved
Rank dropped 36 spots (#969 → #1005)
2026-09-06
Rank Moved
Rank dropped 14 spots (#955 → #969)
2026-09-05
Rank Moved
Rank dropped 49 spots (#906 → #955)
2026-09-04
Rank Moved
Rank dropped 27 spots (#879 → #906)
2026-09-03
Rank Moved
Rank dropped 56 spots (#823 → #879)
2026-09-02
Rank Moved
Rank dropped 61 spots (#762 → #823)
2026-09-01
Rank Moved
Rank dropped 29 spots (#733 → #762)
2026-08-31
Rank Moved
Rank dropped 34 spots (#699 → #733)
2026-08-30
Rank Moved
Rank dropped 25 spots (#674 → #699)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.1/10
2026-08-29
Rank Moved
Rank rose 462 spots (#1136 → #674)
2026-08-29
HVTrust Changed
HVTrust up 25.5pts (21.0 → 46.5)
2026-08-28
Rank Moved
Rank dropped 27 spots (#1109 → #1136)
2026-08-27
Rank Moved
Rank dropped 17 spots (#1092 → #1109)
2026-08-26
Rank Moved
Rank dropped 104 spots (#988 → #1092)
2026-08-26
Activity Score Changed
Activity score down 5pts (46 → 40)
2026-08-24
Rank Moved
Rank dropped 13 spots (#966 → #979)
2026-08-19
Rank Moved
Rank dropped 13 spots (#971 → #984)
2026-08-18
Rank Moved
Rank rose 41 spots (#1012 → #971)
2026-08-16
Rank Moved
Rank dropped 30 spots (#989 → #1019)
2026-08-13
Rank Moved
Rank dropped 11 spots (#981 → #992)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 41.9 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/kdan-pdf.svg)](https://hvtracker.net/agents/kdan-pdf)
HTML:
<a href="https://hvtracker.net/agents/kdan-pdf"><img src="https://hvtracker.net/badge/kdan-pdf.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON