Is DMontgomery40 DeepSeek MCP Server safe to use?

DMontgomery40 DeepSeek MCP Server has an HVTrust score of 58.6/100 (Grade C), ranked #672 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for DMontgomery40 DeepSeek MCP Server?

DMontgomery40 DeepSeek MCP Server scores 58.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 352 GitHub stars and is categorized under MCP Servers.

DMontgomery40 DeepSeek MCP Server

DMontgomery40/deepseek-mcp-server

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 3.7 / 10

Provenance None

Signed commits 22%

Last push 15d ago

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 #672 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 3.7/10; 22% of recent commits are signed; last pushed 2026-09-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How DMontgomery40 DeepSeek MCP Server compares in MCP Servers

#370 Lighthouse MCP 58.8 +0.2
#371 Cisco Modeling Labs CML 58.7 +0.1
#372 DMontgomery40 DeepSeek MCP Server 58.6 this agent
#373 InsForge InsForge 58.5 −0.1
#374 MCP Devkit Server 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 (775 agents)

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

5.7 / 25

4.6 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

11.6 / 17

0.6 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

15.3 / 20

3.2 above avg 12.1

AdoptionLog-scaled stars · package downloads

10.2 / 20

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

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.7/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 DMontgomery40 DeepSeek MCP Server View MCP Servers Report missing data

59.8

Activity sub-score · out of 100

#372

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

352

Forks

Last Push

2026-09-11

15 days ago

Commits (4 wk)

Downloads (7d)

1,154

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼4

was #668

Analysis

Activity Inputs

59.8 / 100

StarsRepository reach

15.3 / 30

FreshnessLast push recency

22.9 / 25

ActivityRecent commits

13.5 / 25

CommunityFork signal

8.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.7 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

22%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 4

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10

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 3.7/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 15 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?

22% 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.

DeepSeek

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

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)

2026-08-10

Rank Moved

Rank dropped 70 spots (#1101 → #1171)

2026-08-08

Newly Listed

First tracked at rank #1099

GitHub → npm: deepseek-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON