Is MCP Documentation Server safe to use?

MCP Documentation Server has an HVTrust score of 52.6/100 (Grade C), ranked #863 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 Documentation Server?

MCP Documentation Server scores 52.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 343 GitHub stars and is categorized under MCP Servers.

MCP Documentation Server

andrea9293/mcp-documentation-server

MCP Documentation Server - Bridge the AI Knowledge Gap. ✨ Features: Document management • Gemini integration • AI-powered semantic search • File uploads • Smart chunking • Multilingual support • Zero-setup 🎯 Perfect for: New frameworks • API docs • Internal guides

MCP Servers TypeScript Listed MIT

Is MCP Documentation Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.2 / 10

Provenance None

Signed commits 22%

Last push 30d ago

Compare MCP Documentation Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Documentation Server scores 52.6/100 (Grade C), ranked #863 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.2/10; 22% of recent commits are signed; last pushed 2026-08-27. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Documentation Server compares in MCP Servers

#487 Nutrition MCP 52.8 +0.2
#488 Dav MCP 52.8 +0.2
#489 MCP Documentation Server 52.6 this agent
#490 SunoMCP 52.4 −0.2
#491 MCP Odoo 52.4 −0.2

Bars show each HVTrust score; the tick marks MCP Documentation Server’s 52.6.

Where the 52.6 comes from

HVTrust dimensions vs the MCP Servers average

52.6 / 100 · 100.0% confidence

MCP Documentation Server MCP Servers average (775 agents)

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

6.3 / 25

4.0 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.1 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

10.0 / 20

2.1 below avg 12.1

AdoptionLog-scaled stars · package downloads

8.7 / 20

1.5 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-26

Rank Moved

Rank dropped 32 spots (#831 → #863)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.2/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.

Compare with another agent Get email alerts for MCP Documentation Server View MCP Servers Report missing data

43.7

Activity sub-score · out of 100

#489

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 C 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

343

Forks

Last Push

2026-08-27

30 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼32

was #831

Analysis

Activity Inputs

43.7 / 100

StarsRepository reach

15.2 / 30

FreshnessLast push recency

20.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

7.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.2 / 10

OpenSSF Scorecard · scanned Sep 18, 2026

Signed Commits

22%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 8

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about MCP Documentation Server

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

No published build provenance is currently detected for MCP Documentation Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Documentation Server have an OpenSSF Scorecard?

MCP Documentation Server has an OpenSSF Scorecard score of 4.2/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 Documentation Server actively maintained?

Maintained. Last push was 30 days ago.

What license does MCP Documentation Server use?

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

Are MCP Documentation Server's commits signed?

22% of the last 100 commits to MCP Documentation Server 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

high confidence

Implemented

MCP Documentation Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

filesystem

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 Documentation Server'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

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain MCP Documentation Server?

For maintainers

HVTrust scores MCP Documentation Server 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-26

Rank Moved

Rank dropped 32 spots (#831 → #863)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 185 spots (#1001 → #816)

2026-09-23

HVTrust Changed

HVTrust up 29.1pts (24.9 → 54.0)

2026-09-22

Newly Listed

First tracked at rank #1001

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 12 spots (#793 → #805)

2026-09-19

Rank Moved

Rank rose 11 spots (#804 → #793)

2026-09-16

Rank Moved

Rank dropped 21 spots (#782 → #803)

2026-09-15

Rank Moved

Rank dropped 10 spots (#772 → #782)

2026-09-13

Rank Moved

Rank dropped 14 spots (#757 → #771)

2026-09-11

Rank Moved

Rank dropped 10 spots (#739 → #749)

2026-09-09

Rank Moved

Rank dropped 13 spots (#726 → #739)

2026-09-08

Rank Moved

Rank dropped 25 spots (#701 → #726)

2026-09-07

Rank Moved

Rank dropped 42 spots (#659 → #701)

2026-09-06

Rank Moved

Rank dropped 14 spots (#645 → #659)

2026-09-05

Rank Moved

Rank dropped 76 spots (#569 → #645)

2026-09-04

Rank Moved

Rank rose 18 spots (#587 → #569)

2026-09-03

Rank Moved

Rank dropped 37 spots (#550 → #587)

2026-09-02

Rank Moved

Rank dropped 17 spots (#533 → #550)

2026-09-01

Rank Moved

Rank dropped 13 spots (#520 → #533)

2026-08-31

Scorecard Added

OSSF Scorecard: 4.2/10

2026-08-31

Grade Changed

Trust grade D → C

2026-08-31

Rank Moved

Rank rose 494 spots (#1014 → #520)

2026-08-31

HVTrust Changed

HVTrust up 22.8pts (32.8 → 55.6)

2026-08-30

Rank Moved

Rank dropped 52 spots (#962 → #1014)

2026-08-29

Rank Moved

Rank dropped 49 spots (#913 → #962)

2026-08-28

Rank Moved

Rank dropped 34 spots (#879 → #913)

2026-08-27

Activity Score Changed

Activity score up 12pts (42 → 54)

2026-08-26

Rank Moved

Rank dropped 108 spots (#777 → #885)

2026-08-16

Rank Moved

Rank dropped 17 spots (#754 → #771)

2026-08-14

Rank Moved

Rank dropped 18 spots (#735 → #753)

2026-08-14

Activity Score Changed

Activity score down 6pts (50 → 44)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-10

Rank Moved

Rank dropped 40 spots (#700 → #740)

2026-08-08

Newly Listed

First tracked at rank #696

GitHub → npm: @andrea9293/mcp-documentation-server

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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