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
Is MCP Documentation Server safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare MCP Documentation Server
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: MCP Documentation Server scores 48.8/100 (Grade D), ranked #1046 of 1387 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 3.5/10; 22% of recent commits are signed; no published advisory affects its latest release (@andrea9293/mcp-documentation-server); last pushed 2026-08-27. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP Documentation Server 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.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 63.5 C · #331 of 779
- Raise the OSSF Scorecard from 3.5 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +11.4 → 60.2 C · #380 of 779
- Sign every commit22% signed today +3.9 → 52.7 C · #520 of 779
Chain of custody
Scanners check what the code says. This traces who ships MCP Documentation Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/andrea9293/mcp-documentation-server, MIT, last pushed 2026-08-27. 22% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.5/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies2
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests 8CII-Best-Practices 0Code-Review 0Contributors 3Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 1Packaging 10Pinned-Dependencies 2SAST 0Security-Policy 10Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages Linked, not attested
- npm @andrea9293/mcp-documentation-server Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: @andrea9293/mcp-documentation-server 1.15.3. No published advisory affects it (OSV, checked 2026-11-10).
Changes to this chain
- 2026-08-31 OSSF Scorecard: 4.2/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues MCP Documentation Server’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 MCP Documentation Server compares in MCP Servers
- #588 Funplay Godot MCP 48.9 +0.1
- #589 MCP Odoo 48.9 +0.1
- #590 MCP Documentation Server 48.8 this agent
- #591 x64dbg MCP Server 48.8 ±0
- #592 MCP Document Converter 48.8 ±0
Bars show each HVTrust score; the tick marks MCP Documentation Server’s 48.8.
Where the 48.8 comes from
HVTrust dimensions vs the MCP Servers average
48.8 / 100 · 100.0% confidenceMCP Documentation Server MCP Servers average (779 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
37.5 / 100Common questions about MCP Documentation Server
Does MCP Documentation Server publish package provenance?
Does MCP Documentation Server have an OpenSSF Scorecard?
Is MCP Documentation Server actively maintained?
What license does MCP Documentation Server use?
Are MCP Documentation Server's commits signed?
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
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 →
- filesystem
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcp-documentation-server)
<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
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.4 · Raw JSON