updated 2026-11-10 04:07 UTC

DMontgomery40 DeepSeek MCP Server

Repository Website

Model Context Protocol server for DeepSeek's advanced language models

MCP Servers TypeScript Listed MIT

Is DMontgomery40 DeepSeek MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 26%
Last push 11d ago
Advisories None known
Compare DMontgomery40 DeepSeek MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: DMontgomery40 DeepSeek MCP Server scores 58.6/100 (Grade C), ranked #736 of 1374 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; 26% of recent commits are signed; no published advisory affects its latest release (deepseek-mcp-server); last pushed 2026-10-30. Every point is earned from checkable signals — never paid placement. How scoring works →

How DMontgomery40 DeepSeek MCP 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships DMontgomery40 DeepSeek MCP 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.

  1. Source Partly signed

    github.com/DMontgomery40/deepseek-mcp-server, MIT, last pushed 2026-10-30. 26% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies6
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 7
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 6
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 2

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: deepseek-mcp-server 1.0.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-08-27 OSSF Scorecard: 2.8/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 DMontgomery40 DeepSeek MCP 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.

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 DMontgomery40 DeepSeek MCP Server compares in MCP Servers

  1. #397 Agent Search MCP 58.6 ±0
  2. #398 ChromaDB Remote MCP Server 58.6 ±0
  3. #399 DMontgomery40 DeepSeek MCP Server 58.6 this agent
  4. #400 Desktop Commander MCP 58.6 ±0
  5. #401 Houtini Ai Gemini MCP 58.5 −0.1

Bars show each HVTrust score; the tick marks DMontgomery40 DeepSeek MCP Server’s 58.6.

Where the 58.6 comes from

HVTrust dimensions vs the MCP Servers average

58.6 / 100 · 100.0% confidence

DMontgomery40 DeepSeek MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.5 / 25
4.3 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
12.1 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
14.4 / 20
2.2 above avg 12.2
AdoptionLog-scaled stars · package downloads
9.8 / 20
2.2 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-08
Rank Moved
Rank rose 66 spots (#800 → #734)
2026-10-31
Rank Moved
Rank rose 10 spots (#798 → #788)
2026-10-27
Rank Moved
Rank rose 19 spots (#806 → #787)
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
View MCP Servers Report missing data
57.0
Activity sub-score · out of 100
#399
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 →

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

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
364
Forks
60
Last Push
2026-10-30
11 days ago
Commits (4 wk)
5
Downloads (7d)
594
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▲1
was #737

Analysis

Activity Inputs

57.0 / 100
StarsRepository reach
15.4 / 30
FreshnessLast push recency
23.5 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
8.3 / 20

Common questions about DMontgomery40 DeepSeek MCP Server

DMontgomery40 DeepSeek MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does DMontgomery40 DeepSeek MCP Server publish package provenance?
No published build provenance is currently detected for DMontgomery40 DeepSeek MCP 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 DMontgomery40 DeepSeek MCP Server have an OpenSSF Scorecard?
DMontgomery40 DeepSeek MCP 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 DMontgomery40 DeepSeek MCP Server actively maintained?
Maintained. Last push was 11 days ago.
What license does DMontgomery40 DeepSeek MCP Server use?
DMontgomery40 DeepSeek MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DMontgomery40 DeepSeek MCP Server's commits signed?
25% of the last 100 commits to DMontgomery40 DeepSeek MCP 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
DMontgomery40 DeepSeek MCP 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.
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
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 DMontgomery40 DeepSeek MCP 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: DeepSeek
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-08-18
Activity Resumed
Activity resumed

Maintain DMontgomery40 DeepSeek MCP Server?

For maintainers

HVTrust scores DMontgomery40 DeepSeek MCP 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
Rank 34HVTrust 7Score 4Grade 2Fresh 1Scorecard 1Delisted 1Listed 1MCP 1Surface 1
2026-11-08
Rank Moved
Rank rose 66 spots (#800 → #734)
2026-10-31
Rank Moved
Rank rose 10 spots (#798 → #788)
2026-10-27
Rank Moved
Rank rose 19 spots (#806 → #787)
2026-10-26
Rank Moved
Rank dropped 40 spots (#766 → #806)
2026-10-23
Rank Moved
Rank dropped 11 spots (#751 → #762)
2026-10-18
Rank Moved
Rank rose 99 spots (#852 → #753)
2026-10-15
Rank Moved
Rank dropped 12 spots (#837 → #849)
2026-10-14
Rank Moved
Rank rose 89 spots (#926 → #837)
2026-10-14
Activity Score Changed
Activity score up 8pts (44 → 52)
2026-10-13
Rank Moved
Rank dropped 32 spots (#894 → #926)
2026-10-11
Rank Moved
Rank dropped 149 spots (#740 → #889)
2026-10-11
HVTrust Changed
HVTrust down 4.4pts (57.4 → 53.0)
2026-10-11
Activity Score Changed
Activity score down 14pts (58 → 44)
2026-10-07
Rank Moved
Rank dropped 17 spots (#710 → #727)
2026-09-24
Rank Moved
Rank rose 123 spots (#787 → #664)
2026-09-24
HVTrust Changed
HVTrust up 3.8pts (54.9 → 58.7)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: DeepSeek
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 248 spots (#1035 → #787)
2026-09-23
HVTrust Changed
HVTrust up 30.8pts (24.1 → 54.9)
2026-09-22
Newly Listed
First tracked at rank #1035
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-13
Rank Moved
Rank rose 14 spots (#766 → #752)
2026-09-12
Rank Moved
Rank dropped 15 spots (#751 → #766)
2026-09-11
Rank Moved
Rank rose 139 spots (#890 → #751)
2026-09-11
HVTrust Changed
HVTrust up 4.7pts (50.8 → 55.5)
2026-09-11
Activity Score Changed
Activity score up 13pts (49 → 62)
2026-09-10
Rank Moved
Rank dropped 31 spots (#859 → #890)
2026-09-09
Rank Moved
Rank dropped 22 spots (#837 → #859)
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 386 spots (#1216 → #830)
2026-09-07
HVTrust Changed
HVTrust up 17.9pts (34.0 → 51.9)
2026-09-06
Rank Moved
Rank dropped 17 spots (#1199 → #1216)
2026-09-05
Rank Moved
Rank dropped 30 spots (#1169 → #1199)
2026-09-04
Rank Moved
Rank dropped 34 spots (#1135 → #1169)
2026-09-03
Rank Moved
Rank dropped 48 spots (#1087 → #1135)
2026-09-02
Rank Moved
Rank dropped 43 spots (#1044 → #1087)
2026-09-01
Rank Moved
Rank dropped 41 spots (#1003 → #1044)
2026-08-31
Rank Moved
Rank dropped 32 spots (#971 → #1003)
2026-08-30
Rank Moved
Rank dropped 50 spots (#921 → #971)
2026-08-29
Rank Moved
Rank dropped 50 spots (#871 → #921)
2026-08-28
Rank Moved
Rank dropped 31 spots (#840 → #871)
2026-08-27
Scorecard Added
OSSF Scorecard: 2.8/10
2026-08-27
Rank Moved
Rank rose 266 spots (#1106 → #840)
2026-08-27
HVTrust Changed
HVTrust up 14.4pts (20.8 → 35.2)
2026-08-26
Rank Moved
Rank dropped 69 spots (#1037 → #1106)
2026-08-19
Rank Moved
Rank rose 22 spots (#1052 → #1030)
2026-08-18
Activity Resumed
Activity resumed
2026-08-18
Rank Moved
Rank rose 145 spots (#1197 → #1052)
2026-08-18
HVTrust Changed
HVTrust up 3.1pts (17.4 → 20.5)
2026-08-18
Activity Score Changed
Activity score up 16pts (32 → 48)
2026-08-16
Rank Moved
Rank dropped 28 spots (#1174 → #1202)
GitHub → Website → npm: deepseek-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 58.6 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/dmontgomery40-deepseek-mcp-server.svg)](https://hvtracker.net/agents/dmontgomery40-deepseek-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/dmontgomery40-deepseek-mcp-server"><img src="https://hvtracker.net/badge/dmontgomery40-deepseek-mcp-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.4 · Raw JSON