updated 2026-10-16 16:07 UTC

Dash MCP Server

Repository

MCP server for Dash, the macOS API documentation browser

MCP Servers Python Listed MIT

Is Dash MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.0 / 10
Provenance None
Signed commits 14%
Last push 77d ago
Advisories None known
Compare Dash MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Dash MCP Server scores 40.6/100 (Grade D), ranked #1204 of 1378 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.0/10; 14% of recent commits are signed; no published advisory affects its latest release (dash-mcp-server); last pushed 2026-07-31. Every point is earned from checkable signals — never paid placement. How scoring works →

How Dash 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 Dash 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/Kapeli/dash-mcp-server, MIT, last pushed 2026-07-31. 14% 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 10, 2026). The checks that decide who can get a change released:

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

  3. Published packages Not linked

    • PyPI dash-mcp-server Source link isn't a GitHub repo No build attestation

    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: dash-mcp-server 1.1.1. No published advisory affects it (OSV, checked 2026-10-15).

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 2.0/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 Dash 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 Dash MCP Server compares in MCP Servers

  1. #692 Multi Gmail MCP 40.8 +0.2
  2. #693 PostgreSQL performance Tuner MCP Server 40.7 +0.1
  3. #694 Dash MCP Server 40.6 this agent
  4. #695 idealo MCP Server 40.3 −0.3
  5. #696 AkTools MCP Server 40.3 −0.3

Bars show each HVTrust score; the tick marks Dash MCP Server’s 40.6.

Where the 40.6 comes from

HVTrust dimensions vs the MCP Servers average

40.6 / 100 · 100.0% confidence

Dash MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.2 / 25
7.3 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
6.9 / 20
5.4 below avg 12.3
AdoptionLog-scaled stars · package downloads
7.8 / 20
in line with avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 11 spots (#1164 → #1175)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 77 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Dash MCP Server View MCP Servers Report missing data
34.9
Activity sub-score · out of 100
#694
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 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-10-16 16:07 UTC · Repo last pushed 77 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
186
Forks
31
Last Push
2026-07-31
77 days ago
Commits (4 wk)
0
Downloads (7d)
52
pypi
HN mentions (30d)
—
Open Issues
11
Rank Change
▼3
was #1201

Analysis

Activity Inputs

34.9 / 100
StarsRepository reach
13.6 / 30
FreshnessLast push recency
14.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.0 / 20

Common questions about Dash MCP Server

Public trust evidence for Dash 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 Dash MCP Server publish package provenance?
No published build provenance is currently detected for Dash 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 Dash MCP Server have an OpenSSF Scorecard?
Dash MCP Server 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 Dash MCP Server actively maintained?
Slowing down. Last push was 77 days ago — keep an eye on whether activity resumes.
What license does Dash MCP Server use?
Dash MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Dash MCP Server's commits signed?
14% of the last 100 commits to Dash 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
Dash MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Dash 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
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Dash MCP Server?

For maintainers

HVTrust scores Dash 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 20Listed 2HVTrust 2Score 1Scorecard 1Delisted 1MCP 1Surface 1
2026-10-09
Rank Moved
Rank dropped 11 spots (#1164 → #1175)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 62 spots (#1196 → #1134)
2026-09-23
HVTrust Changed
HVTrust up 22.3pts (19.3 → 41.6)
2026-09-22
Newly Listed
First tracked at rank #1196
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 16 spots (#1096 → #1112)
2026-09-09
Rank Moved
Rank dropped 15 spots (#1078 → #1093)
2026-09-07
Rank Moved
Rank dropped 29 spots (#1040 → #1069)
2026-09-06
Rank Moved
Rank dropped 16 spots (#1024 → #1040)
2026-09-05
Rank Moved
Rank dropped 47 spots (#977 → #1024)
2026-09-04
Rank Moved
Rank dropped 26 spots (#951 → #977)
2026-09-03
Rank Moved
Rank dropped 59 spots (#892 → #951)
2026-09-02
Rank Moved
Rank dropped 45 spots (#847 → #892)
2026-09-01
Rank Moved
Rank dropped 30 spots (#817 → #847)
2026-08-31
Rank Moved
Rank dropped 35 spots (#782 → #817)
2026-08-30
Scorecard Added
OSSF Scorecard: 2.0/10
2026-08-30
Rank Moved
Rank rose 241 spots (#1023 → #782)
2026-08-30
HVTrust Changed
HVTrust up 15.4pts (28.1 → 43.5)
2026-08-30
Activity Score Changed
Activity score down 6pts (48 → 41)
2026-08-29
Rank Moved
Rank dropped 51 spots (#972 → #1023)
2026-08-28
Rank Moved
Rank dropped 38 spots (#934 → #972)
2026-08-27
Rank Moved
Rank dropped 23 spots (#911 → #934)
2026-08-26
Rank Moved
Rank dropped 110 spots (#801 → #911)
2026-08-24
Rank Moved
Rank dropped 10 spots (#789 → #799)
2026-08-16
Rank Moved
Rank dropped 16 spots (#781 → #797)
2026-08-10
Rank Moved
Rank dropped 41 spots (#738 → #779)
2026-08-08
Newly Listed
First tracked at rank #734
GitHub → PyPI: dash-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 40.6 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/dash-mcp-server.svg)](https://hvtracker.net/agents/dash-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/dash-mcp-server"><img src="https://hvtracker.net/badge/dash-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON