Is MikroMCP safe to use?

MikroMCP has an HVTrust score of 73.0/100 (Grade B), ranked #264 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MikroMCP?

MikroMCP scores 73.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 68 GitHub stars and is categorized under MCP Servers.

MikroMCP

AliKarami/MikroMCP

Production-grade MCP server for MikroTik RouterOS with secure AI-native network automation.

MCP Servers TypeScript Listed MIT

Is MikroMCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.3 / 10

Provenance Attested

Signed commits 67%

Last push 20d ago

Compare MikroMCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MikroMCP scores 73.0/100 (Grade B), ranked #264 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.3/10; 67% of recent commits are signed; last pushed 2026-09-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How MikroMCP compares in MCP Servers

#156 Brandsystem MCP — Brand Guidelines for AI 73.2 +0.2
#157 Lotus Wisdom 73.1 +0.1
#158 MikroMCP 73.0 this agent
#159 MCP Zuul 72.9 −0.1
#160 db-mcp (SQLite MCP Server) 72.7 −0.3

Bars show each HVTrust score; the tick marks MikroMCP’s 73.0.

Where the 73.0 comes from

HVTrust dimensions vs the MCP Servers average

73.0 / 100 · 100.0% confidence

MikroMCP MCP Servers average (775 agents)

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

16.2 / 25

5.9 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.5 / 20

1.4 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.1 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent Get email alerts for MikroMCP View MCP Servers Report missing data

44.7

Activity sub-score · out of 100

#158

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

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-06

20 days ago

Commits (4 wk)

Downloads (7d)

103

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #264

Analysis

Activity Inputs

44.7 / 100

StarsRepository reach

11.0 / 30

FreshnessLast push recency

22.2 / 25

ActivityRecent commits

8.7 / 25

CommunityFork signal

2.8 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

67%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

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 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about MikroMCP

MikroMCP 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 MikroMCP publish package provenance?

Yes. MikroMCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does MikroMCP have an OpenSSF Scorecard?

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

Maintained. Last push was 20 days ago.

What license does MikroMCP use?

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

Are MikroMCP's commits signed?

67% of the last 100 commits to MikroMCP 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

MikroMCP 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

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 MikroMCP'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 → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

Maintain MikroMCP?

For maintainers

HVTrust scores MikroMCP 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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 723 spots (#980 → #257)

2026-09-23

HVTrust Changed

HVTrust up 47.9pts (25.3 → 73.2)

2026-09-22

Newly Listed

First tracked at rank #980

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank dropped 13 spots (#218 → #231)

2026-09-15

Rank Moved

Rank dropped 12 spots (#202 → #214)

2026-09-07

Rank Moved

Rank dropped 11 spots (#158 → #169)

2026-09-06

Rank Moved

Rank dropped 15 spots (#143 → #158)

2026-09-05

Rank Moved

Rank dropped 19 spots (#124 → #143)

2026-08-31

Rank Moved

Rank dropped 15 spots (#98 → #113)

2026-08-27

Scorecard Added

OSSF Scorecard: 4.3/10

2026-08-27

Rank Moved

Rank rose 141 spots (#236 → #95)

2026-08-27

HVTrust Changed

HVTrust up 12.0pts (66.0 → 78.0)

2026-08-26

Rank Moved

Rank dropped 79 spots (#157 → #236)

2026-08-26

HVTrust Changed

HVTrust down 3.2pts (69.2 → 66.0)

2026-08-22

Rank Moved

Rank rose 18 spots (#173 → #155)

2026-08-13

Rank Moved

Rank dropped 12 spots (#164 → #176)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-12

Rank Moved

Rank rose 30 spots (#194 → #164)

2026-08-10

Rank Moved

Rank dropped 22 spots (#172 → #194)

2026-08-08

Newly Listed

First tracked at rank #168

GitHub → npm: mikromcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mikromcp.svg)](https://hvtracker.net/agents/mikromcp)
            
HTML:
            <a href="https://hvtracker.net/agents/mikromcp"><img src="https://hvtracker.net/badge/mikromcp.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