updated 2026-09-08 16:17 UTC

DMontgomery40 DeepSeek MCP Server

DMontgomery40/deepseek-mcp-server

Model Context Protocol server for DeepSeek's advanced language models

MCP Servers TypeScript Grade C Listed MIT
51.9/100
Rank #837 of 1328
Compare DMontgomery40 DeepSeek MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-19 · 20d ago
Recent change
Grade Changed +8

Is DMontgomery40 DeepSeek MCP Server safe? DMontgomery40 DeepSeek MCP Server scores 51.9/100 (Grade C), ranked #837 of 1328 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 2.2/10; 28% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#460 Kibana — 52.2 (C) → #461 Apollo.io — 51.9 (C) → #463 SearXNG HTTP MCP — 51.8 (C) → #464 Codex MCP Go — 51.8 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.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 DMontgomery40 DeepSeek MCP Server View MCP Servers Report missing data
49.4
Activity sub-score · out of 100
#462
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-09-08 16:17 UTC · Repo last pushed 20 days ago

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
351
Forks
55
Last Push
2026-08-19
20 days ago
Commits (4 wk)
1
Downloads (7d)
411
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼7
was #830

Analysis

HVTrust Dimensions vs MCP Servers

51.9 / 100 · 100.0% confidence

DMontgomery40 DeepSeek MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.2 / 25
5.7 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
10.4 / 17
1.6 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
11.9 / 20
in line with avg 12.2
AdoptionLog-scaled stars · package downloads
9.6 / 20
2.7 above avg 6.9

Activity Inputs

49.4 / 100
StarsRepository reach
15.3 / 30
FreshnessLast push recency
22.2 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
8.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.2 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
28%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 1
Contributors 3
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging -1
Pinned-Dependencies 4
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 4

Is DMontgomery40 DeepSeek MCP Server safe?

Public trust evidence for DMontgomery40 DeepSeek MCP 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 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 2.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 20 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?
28% 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-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 17HVTrust 3Listed 1Score 1Fresh 1Scorecard 1Grade 1
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
HVTrust 51.9 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.3 · Raw JSON