Dav MCP

Transform AI agents into orchestrating assistants managing calendars, contacts, and tasks

MCP Servers JavaScript Listed MIT

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

OSSF Scorecard 3.9 / 10
Provenance None
Signed commits 21%
Last push 16d ago
Compare Dav MCP
Suggest a correction

In detail: Dav MCP scores 53.4/100 (Grade C), ranked #840 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.9/10; 21% of recent commits are signed; last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Dav MCP compares in MCP Servers

  1. #471 Bimwright 53.7 +0.3
  2. #472 NinjaOne 53.4 ±0
  3. #473 Dav MCP 53.4 this agent
  4. #474 Nse Bse Indian Stock Market Data MCP 53.4 ±0
  5. #475 Mac Control MCP 53.3 −0.1

Bars show each HVTrust score; the tick marks Dav MCP’s 53.4.

Where the 53.4 comes from

HVTrust dimensions vs the MCP Servers average

53.4 / 100 · 100.0% confidence

Dav MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.9 / 25
4.4 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.8 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
15.5 / 20
3.4 above avg 12.1
AdoptionLog-scaled stars · package downloads
6.4 / 20
0.8 below 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-25
Rank Moved
Rank dropped 11 spots (#829 → #840)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.9/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.
51.8
Activity sub-score · out of 100
#473

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-26 06:32 UTC · Repo last pushed 16 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
35
Forks
13
Last Push
2026-09-10
16 days ago
Commits (4 wk)
13
Downloads (7d)
106
npm
HN mentions (30d)
—
Open Issues
4
Rank Change
=
was #840

Analysis

Activity Inputs

51.8 / 100
StarsRepository reach
9.3 / 30
FreshnessLast push recency
22.8 / 25
ActivityRecent commits
14.3 / 25
CommunityFork signal
5.3 / 20

Supply Chain Trust

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

Common questions about Dav MCP

Public trust evidence for Dav MCP 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 Dav MCP publish package provenance?
No published build provenance is currently detected for Dav MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Dav MCP have an OpenSSF Scorecard?
Dav MCP has an OpenSSF Scorecard score of 3.9/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 Dav MCP actively maintained?
Maintained. Last push was 16 days ago.
What license does Dav MCP use?
Dav MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Dav MCP's commits signed?
21% of the last 100 commits to Dav MCP 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
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
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 Dav MCP'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 → declared
2026-08-14
Activity Resumed
Activity resumed

Maintain Dav MCP?

For maintainers

HVTrust scores Dav MCP 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.

Reputation Timeline

Signal history
Rank 25HVTrust 4Score 3Listed 2Grade 2Fresh 1Scorecard 1Delisted 1MCP 1
2026-09-25
Rank Moved
Rank dropped 11 spots (#829 → #840)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 132 spots (#958 → #826)
2026-09-23
HVTrust Changed
HVTrust up 27.9pts (25.7 → 53.6)
2026-09-22
Newly Listed
First tracked at rank #958
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 11 spots (#808 → #819)
2026-09-19
Rank Moved
Rank rose 10 spots (#818 → #808)
2026-09-15
Rank Moved
Rank dropped 29 spots (#778 → #807)
2026-09-13
Rank Moved
Rank dropped 63 spots (#714 → #777)
2026-09-13
Activity Score Changed
Activity score down 5pts (61 → 55)
2026-09-11
Rank Moved
Rank rose 37 spots (#747 → #710)
2026-09-10
Rank Moved
Rank rose 76 spots (#823 → #747)
2026-09-10
Activity Score Changed
Activity score up 6pts (55 → 61)
2026-09-09
Rank Moved
Rank dropped 14 spots (#809 → #823)
2026-09-07
Rank Moved
Rank dropped 53 spots (#747 → #800)
2026-09-06
Rank Moved
Rank dropped 12 spots (#735 → #747)
2026-09-05
Rank Moved
Rank dropped 65 spots (#670 → #735)
2026-09-04
Rank Moved
Rank dropped 26 spots (#644 → #670)
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 459 spots (#1103 → #644)
2026-09-03
HVTrust Changed
HVTrust up 19.4pts (34.4 → 53.8)
2026-09-02
Rank Moved
Rank dropped 45 spots (#1058 → #1103)
2026-09-01
Rank Moved
Rank dropped 40 spots (#1018 → #1058)
2026-08-31
Rank Moved
Rank dropped 33 spots (#985 → #1018)
2026-08-30
Rank Moved
Rank dropped 51 spots (#934 → #985)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.3/10
2026-08-29
Rank Moved
Rank rose 267 spots (#1201 → #934)
2026-08-29
HVTrust Changed
HVTrust up 15.3pts (19.2 → 34.5)
2026-08-28
Rank Moved
Rank dropped 16 spots (#1185 → #1201)
2026-08-27
Rank Moved
Rank dropped 14 spots (#1171 → #1185)
2026-08-26
Rank Moved
Rank dropped 53 spots (#1118 → #1171)
2026-08-16
Rank Moved
Rank dropped 28 spots (#1089 → #1117)
2026-08-14
Activity Resumed
Activity resumed
2026-08-14
Rank Moved
Rank rose 176 spots (#1265 → #1089)
2026-08-14
HVTrust Changed
HVTrust up 6.0pts (13.6 → 19.6)
2026-08-14
Activity Score Changed
Activity score up 38pts (21 → 59)
2026-08-10
Rank Moved
Rank dropped 78 spots (#1186 → #1264)
2026-08-08
Newly Listed
First tracked at rank #1186

Embed Badge Badge guide for maintainers →

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