Mondaycom MCP

Enable AI agents to work reliably - giving them secure access to structured data, tools to take action, and the context

MCP Servers TypeScript Grade D Listed MIT
23.6/100
Rank #1302 of 1328
Compare Mondaycom MCP

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-09-07 · 1d ago
Recent change
Rank +4

Is Mondaycom MCP safe? Mondaycom MCP scores 23.6/100 (Grade D), ranked #1302 of 1328 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 100% of recent commits are signed; last pushed 2026-09-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-05
Rank Moved
Rank dropped 12 spots (#1275 → #1287)
2026-09-04
Rank Moved
Rank dropped 13 spots (#1262 → #1275)
2026-09-03
Rank Moved
Rank dropped 31 spots (#1231 → #1262)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
66.1
Activity sub-score · out of 100
#770

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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-08 16:17 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
423
Forks
96
Last Push
2026-09-07
yesterday
Commits (4 wk)
19
Downloads (7d)
HN mentions (30d)
Open Issues
20
Rank Change
▼6
was #1296

Analysis

HVTrust Dimensions vs MCP Servers

23.6 / 100 · 50.0% confidence

Mondaycom MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
4.9 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
8.5 / 17
3.5 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
17.1 / 20
4.9 above avg 12.2
AdoptionLog-scaled stars · package downloads
6.3 / 20
0.6 below avg 6.9

Activity Inputs

66.1 / 100
StarsRepository reach
15.8 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
16.2 / 25
CommunityFork signal
9.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
Not available
Signed Commits
100%
of last 100 commits verified

Is Mondaycom MCP safe?

Public trust evidence for Mondaycom 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 Mondaycom MCP publish package provenance?
No published build provenance is currently detected for Mondaycom 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 Mondaycom MCP have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Mondaycom MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Mondaycom MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Mondaycom MCP use?
Mondaycom MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Mondaycom MCP's commits signed?
100% of the last 100 commits to Mondaycom 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
high confidence
Implemented
Mondaycom MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Mondaycom MCP?

For maintainers

HVTrust scores Mondaycom 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 17Listed 1
2026-09-05
Rank Moved
Rank dropped 12 spots (#1275 → #1287)
2026-09-04
Rank Moved
Rank dropped 13 spots (#1262 → #1275)
2026-09-03
Rank Moved
Rank dropped 31 spots (#1231 → #1262)
2026-09-02
Rank Moved
Rank dropped 36 spots (#1195 → #1231)
2026-09-01
Rank Moved
Rank dropped 32 spots (#1163 → #1195)
2026-08-31
Rank Moved
Rank dropped 32 spots (#1131 → #1163)
2026-08-30
Rank Moved
Rank dropped 46 spots (#1085 → #1131)
2026-08-29
Rank Moved
Rank dropped 41 spots (#1044 → #1085)
2026-08-28
Rank Moved
Rank dropped 32 spots (#1012 → #1044)
2026-08-27
Rank Moved
Rank dropped 27 spots (#985 → #1012)
2026-08-26
Rank Moved
Rank dropped 95 spots (#890 → #985)
2026-08-25
Rank Moved
Rank rose 17 spots (#907 → #890)
2026-08-21
Rank Moved
Rank rose 10 spots (#916 → #906)
2026-08-19
Rank Moved
Rank dropped 13 spots (#898 → #911)
2026-08-17
Rank Moved
Rank rose 23 spots (#914 → #891)
2026-08-16
Rank Moved
Rank dropped 29 spots (#885 → #914)
2026-08-10
Rank Moved
Rank dropped 49 spots (#831 → #880)
2026-08-08
Newly Listed
First tracked at rank #824

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON