updated 2026-09-04 23:32 UTC

MikroMCP

AliKarami/MikroMCP

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

MCP Servers TypeScript Grade B Listed MIT
77.6/100
Rank #124 of 1320
Compare MikroMCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-23 · 12d ago
Recent change
Rank

Is MikroMCP safe? MikroMCP scores 77.6/100 (Grade B), ranked #124 of 1320 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; 63% of recent commits are signed; last pushed 2026-08-23. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#55 Reversecore MCP — 77.8 (B) → #56 Anytype MCP — 77.6 (B) → #58 Aiven MCP — 77.5 (B) → #59 Zigbee2MQTT MCP — 77.5 (B) →

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
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)
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
56.6
Activity sub-score · out of 100
#57
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 →

Signals refreshed 2026-09-04 23:32 UTC · Repo last pushed 12 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
62
Forks
3
Last Push
2026-08-23
12 days ago
Commits (4 wk)
37
Downloads (7d)
528
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼4
was #120

Analysis

HVTrust Dimensions vs MCP Servers

77.6 / 100 · 100.0% confidence

MikroMCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.0 / 25
6.4 above avg 9.6
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 11.8
Maintenance60% last-push freshness · 40% commit activity
17.5 / 20
5.3 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.9 / 20
1.6 above avg 6.3

Activity Inputs

56.6 / 100
StarsRepository reach
10.8 / 30
FreshnessLast push recency
23.3 / 25
ActivityRecent commits
19.7 / 25
CommunityFork signal
2.8 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
4.3 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
63%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
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

Is MikroMCP safe?

Public supply-chain signals for MikroMCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but MikroMCP carries less obvious unverified-evidence risk than projects with thin signals.
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 12 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?
63% 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-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
Rank 7HVTrust 2Listed 1Surface 1Scorecard 1
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
HVTrust 77.6 Grade B
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