Is MCP Document Reader safe to use?

MCP Document Reader has an HVTrust score of 49.6/100 (Grade D), ranked #951 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Document Reader?

MCP Document Reader scores 49.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 23 GitHub stars and is categorized under MCP Servers.

MCP Document Reader

xt765/mcp_documents_reader

Model Context Protocol (MCP) server exposes tools to read multiple document types including DOCX, PDF, Excel, and TXT. This has been tested on Trae Desktop.

MCP Servers Python Listed MIT

Is MCP Document Reader safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.6 / 10

Provenance Attested

Signed commits 4%

Last push 197d ago

Compare MCP Document Reader

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Document Reader scores 49.6/100 (Grade D), ranked #951 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 2.6/10; 4% of recent commits are signed; last pushed 2026-03-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Document Reader compares in MCP Servers

#546 SharpLens 49.6 ±0
#547 MCP Turso Cloud 49.6 ±0
#548 MCP Document Reader 49.6 this agent
#549 Sap Adt MCP 49.5 −0.1
#550 Druid MCP Server 49.4 −0.2

Bars show each HVTrust score; the tick marks MCP Document Reader’s 49.6.

Where the 49.6 comes from

HVTrust dimensions vs the MCP Servers average

49.6 / 100 · 100.0% confidence

MCP Document Reader MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

10.9 / 25

0.6 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

10.7 / 17

1.5 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.1 below avg 12.1

AdoptionLog-scaled stars · package downloads

6.0 / 20

1.2 below avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-25

Rank Moved

Rank dropped 14 spots (#938 → #952)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.6/10. Tighten the weakest checks to improve public safety evidence.

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 197 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for MCP Document Reader View MCP Servers Report missing data

12.5

Activity sub-score · out of 100

#548

In MCP Servers

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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-03-13

197 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #952

Analysis

Activity Inputs

12.5 / 100

StarsRepository reach

8.3 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

4.2 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

2.6 / 10

OpenSSF Scorecard · scanned Sep 21, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about MCP Document Reader

Public trust evidence for MCP Document Reader 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 MCP Document Reader publish package provenance?

Yes. MCP Document Reader's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does MCP Document Reader have an OpenSSF Scorecard?

MCP Document Reader has an OpenSSF Scorecard score of 2.6/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 MCP Document Reader actively maintained?

Stale. The repository has not been pushed to in 197 days. Consider whether the project is still being maintained.

What license does MCP Document Reader use?

MCP Document Reader ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Document Reader's commits signed?

3% of the last 100 commits to MCP Document Reader 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

low confidence

Declared

MCP support appears present, but direct server implementation is less certain.

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

high confidence

Match

Published package metadata matches the tracked repo

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 MCP Document Reader'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 → declared

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain MCP Document Reader?

For maintainers

HVTrust scores MCP Document Reader 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-25

Rank Moved

Rank dropped 14 spots (#938 → #952)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Rank Moved

Rank rose 361 spots (#1299 → #938)

2026-09-23

HVTrust Changed

HVTrust up 36.6pts (13.0 → 49.6)

2026-09-22

Newly Listed

First tracked at rank #1299

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-09

Rank Moved

Rank dropped 16 spots (#915 → #931)

2026-09-08

Rank Moved

Rank dropped 11 spots (#904 → #915)

2026-09-07

Rank Moved

Rank dropped 40 spots (#864 → #904)

2026-09-06

Rank Moved

Rank dropped 17 spots (#847 → #864)

2026-09-05

Rank Moved

Rank dropped 61 spots (#786 → #847)

2026-09-04

Rank Moved

Rank dropped 27 spots (#759 → #786)

2026-09-03

Grade Changed

Trust grade C → D

2026-09-03

Rank Moved

Rank dropped 70 spots (#689 → #759)

2026-09-02

Rank Moved

Rank dropped 34 spots (#655 → #689)

2026-09-01

Rank Moved

Rank dropped 25 spots (#630 → #655)

2026-08-31

Rank Moved

Rank dropped 34 spots (#596 → #630)

2026-08-29

Rank Moved

Rank dropped 37 spots (#551 → #588)

2026-08-28

Rank Moved

Rank dropped 12 spots (#539 → #551)

2026-08-27

Rank Moved

Rank dropped 15 spots (#524 → #539)

2026-08-26

Scorecard Added

OSSF Scorecard: 2.6/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

HVTrust Changed

HVTrust up 5.3pts (45.9 → 51.2)

2026-08-24

Rank Moved

Rank dropped 11 spots (#507 → #518)

2026-08-22

Rank Moved

Rank rose 10 spots (#519 → #509)

2026-08-19

Rank Moved

Rank dropped 10 spots (#509 → #519)

2026-08-17

Rank Moved

Rank rose 10 spots (#517 → #507)

2026-08-13

Rank Moved

Rank dropped 13 spots (#492 → #505)

2026-08-10

Rank Moved

Rank dropped 17 spots (#483 → #500)

2026-08-08

Newly Listed

First tracked at rank #478

GitHub → PyPI: mcp-documents-reader

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-document-reader.svg)](https://hvtracker.net/agents/mcp-document-reader)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-document-reader"><img src="https://hvtracker.net/badge/mcp-document-reader.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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