Miro has an HVTrust score of 55.4/100 (Grade C), ranked #731 of 1328 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 55.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 26 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 Grade C Listed MIT

55.4/100

Rank #731 of 1328

Compare Miro

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-31 · 8d ago

Recent change

Grade Changed +10

Is Miro safe? Miro scores 55.4/100 (Grade C), ranked #731 of 1328 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.5/10; 40% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#391 Better Notion MCP — 55.6 (C) → #392 Reddit Research MCP — 55.5 (C) → #394 MCP NixOS — 55.4 (C) → #395 Quickbooks MCP — 55.4 (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 436 spots (#1160 → #724)

2026-09-07

HVTrust Changed

HVTrust up 18.2pts (37.2 → 55.4)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/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.9

Activity sub-score · out of 100

#393

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-08

Activity & Reach

Stars

Forks

Last Push

2026-08-31

8 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼7

was #724

Analysis

HVTrust Dimensions vs MCP Servers

55.4 / 100 · 100.0% confidence

Miro MCP Servers average (778 agents)

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

8.9 / 25

1.0 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

13.2 / 17

1.2 above avg 12.0

Maintenance60% last-push freshness · 40% commit activity

18.4 / 20

6.2 above avg 12.2

AdoptionLog-scaled stars · package downloads

3.4 / 20

3.5 below avg 6.9

Activity Inputs

58.9 / 100

StarsRepository reach

8.6 / 30

FreshnessLast push recency

23.9 / 25

ActivityRecent commits

21.6 / 25

CommunityFork signal

4.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.5 / 10

OpenSSF Scorecard · scanned Sep 1, 2026

Signed Commits

40%

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 0

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Is Miro safe?

Miro has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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.5/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?

Maintained. Last push was 8 days ago.

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?

40% 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

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