Miro has an HVTrust score of 54.9/100 (Grade C), ranked #788 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Miro?

Miro scores 54.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 28 GitHub stars and is categorized under MCP Servers.

Miro

olgasafonova/miro-mcp-server

MCP server for controlling Miro whiteboards with AI assistants

MCP Servers Go Listed MIT

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

OSSF Scorecard 5.8 / 10

Provenance None

Signed commits 22%

Last push 5d ago

Compare Miro

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Miro scores 54.9/100 (Grade C), ranked #788 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.8/10; 22% of recent commits are signed; last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Miro compares in MCP Servers

Bars show each HVTrust score; the tick marks Miro’s 54.9.

Where the 54.9 comes from

HVTrust dimensions vs the MCP Servers average

54.9 / 100 · 100.0% confidence

Miro MCP Servers average (775 agents)

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

8.3 / 25

2.0 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

13.4 / 17

1.2 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

18.2 / 20

6.1 above avg 12.1

AdoptionLog-scaled stars · package downloads

3.5 / 20

3.7 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-24

Rank Moved

Rank rose 10 spots (#790 → #780)

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 5.8/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 Miro View MCP Servers Report missing data

58.6

Activity sub-score · out of 100

#436

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

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-21

5 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #785

Analysis

Activity Inputs

58.6 / 100

StarsRepository reach

8.8 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

20.4 / 25

CommunityFork signal

5.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.8 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

22%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 8

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Common questions about Miro

Public trust evidence for Miro 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 Miro publish package provenance?

No published build provenance is currently detected for Miro. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Miro have an OpenSSF Scorecard?

Miro has an OpenSSF Scorecard score of 5.8/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 Miro actively maintained?

Actively maintained. The repository was pushed to within the last 5 day(s).

What license does Miro use?

Miro ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Miro's commits signed?

22% of the last 100 commits to Miro 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

Implemented

Miro appears to expose MCP server capabilities.

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

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

How this surface has changed

Detected changes to Miro'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 Miro?

For maintainers

HVTrust scores Miro 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 10 spots (#790 → #780)

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

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 25 spots (#765 → #790)

2026-09-23

HVTrust Changed

HVTrust up 25.1pts (29.7 → 54.8)

2026-09-22

Newly Listed

First tracked at rank #765

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Grade Changed

Trust grade D → C

2026-09-19

Rank Moved

Rank rose 431 spots (#1212 → #781)

2026-09-19

HVTrust Changed

HVTrust up 18.0pts (36.8 → 54.8)

2026-09-18

Grade Changed

Trust grade C → D

2026-09-18

Rank Moved

Rank dropped 369 spots (#843 → #1212)

2026-09-18

HVTrust Changed

HVTrust down 16.0pts (52.8 → 36.8)

2026-09-18

Activity Score Changed

Activity score up 8pts (51 → 59)

2026-09-17

Rank Moved

Rank dropped 30 spots (#813 → #843)

2026-09-16

Rank Moved

Rank dropped 23 spots (#790 → #813)

2026-09-14

Rank Moved

Rank dropped 23 spots (#764 → #787)

2026-09-13

Rank Moved

Rank dropped 20 spots (#744 → #764)

2026-09-09

Grade Changed

Trust grade D → C

2026-09-09

Rank Moved

Rank rose 468 spots (#1187 → #719)

2026-09-09

HVTrust Changed

HVTrust up 18.7pts (37.2 → 55.9)

2026-09-08

Grade Changed

Trust grade C → D

2026-09-08

Rank Moved

Rank dropped 463 spots (#724 → #1187)

2026-09-08

HVTrust Changed

HVTrust down 18.2pts (55.4 → 37.2)

2026-09-07

Grade Changed

Trust grade D → C

2026-09-07

Rank Moved

Rank rose 436 spots (#1160 → #724)

2026-09-07

HVTrust Changed

HVTrust up 18.2pts (37.2 → 55.4)

2026-09-06

Grade Changed

Trust grade C → D

2026-09-06

Rank Moved

Rank dropped 485 spots (#675 → #1160)

2026-09-06

HVTrust Changed

HVTrust down 18.4pts (55.6 → 37.2)

2026-09-05

Rank Moved

Rank dropped 81 spots (#594 → #675)

2026-09-04

Rank Moved

Rank dropped 18 spots (#576 → #594)

2026-09-03

Rank Moved

Rank dropped 40 spots (#536 → #576)

2026-09-02

Rank Moved

Rank dropped 18 spots (#518 → #536)

2026-09-01

Rank Moved

Rank dropped 11 spots (#507 → #518)

2026-08-31

Rank Moved

Rank dropped 20 spots (#487 → #507)

2026-08-30

Scorecard Added

OSSF Scorecard: 5.5/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 630 spots (#1117 → #487)

2026-08-30

HVTrust Changed

HVTrust up 33.3pts (22.5 → 55.8)

2026-08-29

Rank Moved

Rank dropped 40 spots (#1077 → #1117)

2026-08-28

Rank Moved

Rank dropped 29 spots (#1048 → #1077)

2026-08-27

Rank Moved

Rank dropped 26 spots (#1022 → #1048)

2026-08-26

Rank Moved

Rank dropped 80 spots (#942 → #1022)

2026-08-17

Rank Moved

Rank rose 18 spots (#959 → #941)

2026-08-16

Rank Moved

Rank dropped 31 spots (#928 → #959)

2026-08-15

Rank Moved

Rank rose 14 spots (#942 → #928)

2026-08-12

Rank Moved

Rank rose 16 spots (#954 → #938)

2026-08-10

Rank Moved

Rank dropped 53 spots (#898 → #951)

2026-08-08

Newly Listed

First tracked at rank #887

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/miro.svg)](https://hvtracker.net/agents/miro)
            
HTML:
            <a href="https://hvtracker.net/agents/miro"><img src="https://hvtracker.net/badge/miro.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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