updated 2026-10-16 20:06 UTC

DevDocs

Repository Website

Completely free, private, UI based Tech Documentation MCP server. Designed for coders and software developers in mind. Easily integrate into Cursor, Windsurf, Cline, Roo Code, Claude Desktop App

MCP Servers TypeScript Listed Apache-2.0

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

OSSF Scorecard 2.0 / 10
Provenance None
Signed commits 53%
Last push 254d ago
Compare DevDocs

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: DevDocs scores 35.1/100 (Grade D), ranked #1292 of 1378 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.0/10; 53% of recent commits are signed; last pushed 2026-02-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How DevDocs 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships DevDocs 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/cyberagiinc/DevDocs, Apache-2.0, last pushed 2026-02-04. 53% 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.0/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

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

  3. Published packages None

    No registry package. DevDocs 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-26 OSSF Scorecard: 2.0/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 DevDocs’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.

Signed credential (JSON) How to verify

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 DevDocs compares in MCP Servers

  1. #748 MCP Skills Server 35.2 +0.1
  2. #749 MCP Language Server 35.1 ±0
  3. #750 DevDocs 35.1 this agent
  4. #751 MCP Drawthings 35.1 ±0
  5. #752 Jotform MCP Server 34.5 −0.6

Bars show each HVTrust score; the tick marks DevDocs’s 35.1.

Where the 35.1 comes from

HVTrust dimensions vs the MCP Servers average

35.1 / 100 · 100.0% confidence

DevDocs MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.1 / 25
5.4 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
10.2 / 17
2.1 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.3 below avg 12.3
AdoptionLog-scaled stars · package downloads
8.0 / 20
0.6 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 171 spots (#1069 → #1240)
2026-09-23
HVTrust Changed
HVTrust up 12.1pts (23.0 → 35.1)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.0/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.
Refresh maintenance signals The repo was last pushed 254 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for DevDocs View MCP Servers Report missing data
30.7
Activity sub-score · out of 100
#750
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 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-10-16 20:06 UTC · Repo last pushed 254 days ago — may be stale

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
2.1k
Forks
207
Last Push
2026-02-04
254 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
10
Rank Change
▼3
was #1289

Analysis

Activity Inputs

30.7 / 100
StarsRepository reach
19.9 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.8 / 20

Common questions about DevDocs

Public trust evidence for DevDocs 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 DevDocs publish package provenance?
No published build provenance is currently detected for DevDocs. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does DevDocs have an OpenSSF Scorecard?
DevDocs has an OpenSSF Scorecard score of 2.0/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 DevDocs actively maintained?
Stale. The repository has not been pushed to in 254 days. Consider whether the project is still being maintained.
What license does DevDocs use?
DevDocs ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DevDocs's commits signed?
52% of the last 100 commits to DevDocs 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
DevDocs appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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 DevDocs'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
2026-09-02
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain DevDocs?

For maintainers

HVTrust scores DevDocs 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
Rank 16Listed 2HVTrust 2Scorecard 1Surface 1Delisted 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 171 spots (#1069 → #1240)
2026-09-23
HVTrust Changed
HVTrust up 12.1pts (23.0 → 35.1)
2026-09-22
Newly Listed
First tracked at rank #1069
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-08
Rank Moved
Rank dropped 12 spots (#1208 → #1220)
2026-09-07
Rank Moved
Rank dropped 16 spots (#1192 → #1208)
2026-09-06
Rank Moved
Rank dropped 16 spots (#1176 → #1192)
2026-09-05
Rank Moved
Rank dropped 31 spots (#1145 → #1176)
2026-09-04
Rank Moved
Rank dropped 14 spots (#1131 → #1145)
2026-09-03
Rank Moved
Rank dropped 47 spots (#1084 → #1131)
2026-09-02
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-09-02
Rank Moved
Rank dropped 64 spots (#1020 → #1084)
2026-09-01
Rank Moved
Rank dropped 40 spots (#980 → #1020)
2026-08-31
Rank Moved
Rank dropped 30 spots (#950 → #980)
2026-08-30
Rank Moved
Rank dropped 43 spots (#907 → #950)
2026-08-29
Rank Moved
Rank dropped 49 spots (#858 → #907)
2026-08-28
Rank Moved
Rank dropped 28 spots (#830 → #858)
2026-08-27
Rank Moved
Rank dropped 22 spots (#808 → #830)
2026-08-26
Scorecard Added
OSSF Scorecard: 2.0/10
2026-08-26
Rank Moved
Rank rose 408 spots (#1216 → #808)
2026-08-26
HVTrust Changed
HVTrust up 19.2pts (16.6 → 35.8)
2026-08-16
Rank Moved
Rank dropped 26 spots (#1196 → #1222)
2026-08-10
Newly Listed
First tracked at rank #1202
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 35.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/devdocs.svg)](https://hvtracker.net/agents/devdocs)
HTML:
<a href="https://hvtracker.net/agents/devdocs"><img src="https://hvtracker.net/badge/devdocs.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