Is Mikrotik MCP safe to use?

Mikrotik MCP has an HVTrust score of 80.1/100 (Grade A), ranked #143 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Mikrotik MCP?

Mikrotik MCP scores 80.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 285 GitHub stars and is categorized under MCP Servers.

Mikrotik MCP

jeff-nasseri/mikrotik-mcp

MCP server for Mikrotik

MCP Servers Python Listed MIT

Is Mikrotik MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.7 / 10

Provenance Attested

Signed commits 1%

Last push 2d ago

Compare Mikrotik MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Mikrotik MCP scores 80.1/100 (Grade A), ranked #143 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 5.7/10; 1% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How Mikrotik MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Mikrotik MCP’s 80.1.

Where the 80.1 comes from

HVTrust dimensions vs the MCP Servers average

80.1 / 100 · 100.0% confidence

Mikrotik MCP MCP Servers average (775 agents)

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

14.7 / 25

4.4 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

13.3 / 17

1.1 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.8 / 20

5.7 above avg 12.1

AdoptionLog-scaled stars · package downloads

10.3 / 20

3.1 above avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

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

Maintainer Checklist

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

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 Mikrotik MCP View MCP Servers Report missing data

66.4

Activity sub-score · out of 100

#72

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

285

Forks

Last Push

2026-09-24

2 days ago

Commits (4 wk)

Downloads (7d)

2,177

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #142

Analysis

Activity Inputs

66.4 / 100

StarsRepository reach

14.7 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

18.4 / 25

CommunityFork signal

8.4 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

5.7 / 10

OpenSSF Scorecard · scanned Sep 17, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 7

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 6

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Common questions about Mikrotik MCP

Public supply-chain signals for Mikrotik MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Mikrotik MCP carries less obvious unverified-evidence risk than projects with thin signals.

Does Mikrotik MCP publish package provenance?

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

Does Mikrotik MCP have an OpenSSF Scorecard?

Mikrotik MCP has an OpenSSF Scorecard score of 5.7/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 Mikrotik MCP actively maintained?

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

What license does Mikrotik MCP use?

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

Are Mikrotik MCP's commits signed?

1% of the last 100 commits to Mikrotik 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

Mikrotik MCP 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 Mikrotik MCP'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

Maintain Mikrotik MCP?

For maintainers

HVTrust scores Mikrotik 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.

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

2026-09-23

Rank Moved

Rank rose 564 spots (#702 → #138)

2026-09-23

HVTrust Changed

HVTrust up 49.4pts (30.8 → 80.2)

2026-09-22

Newly Listed

First tracked at rank #702

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-16

Rank Moved

Rank rose 31 spots (#199 → #168)

2026-09-16

Activity Score Changed

Activity score up 6pts (58 → 64)

2026-09-10

Rank Moved

Rank rose 37 spots (#216 → #179)

2026-09-09

Rank Moved

Rank dropped 44 spots (#172 → #216)

2026-09-08

Rank Moved

Rank dropped 27 spots (#145 → #172)

2026-09-08

Activity Score Changed

Activity score down 6pts (65 → 59)

2026-09-07

Rank Moved

Rank dropped 10 spots (#135 → #145)

2026-09-05

Rank Moved

Rank dropped 33 spots (#101 → #134)

2026-09-02

Rank Moved

Rank rose 27 spots (#120 → #93)

2026-08-31

Rank Moved

Rank dropped 19 spots (#105 → #124)

2026-08-29

Scorecard Added

OSSF Scorecard: 5.8/10

2026-08-29

Grade Changed

Trust grade C → B

2026-08-29

Rank Moved

Rank rose 163 spots (#273 → #110)

2026-08-29

HVTrust Changed

HVTrust up 12.0pts (64.5 → 76.5)

2026-08-26

Rank Moved

Rank dropped 22 spots (#241 → #263)

2026-08-24

Rank Moved

Rank dropped 14 spots (#227 → #241)

2026-08-22

Rank Moved

Rank rose 18 spots (#246 → #228)

2026-08-19

Rank Moved

Rank dropped 11 spots (#230 → #241)

2026-08-18

Rank Moved

Rank rose 12 spots (#242 → #230)

2026-08-17

Rank Moved

Rank rose 10 spots (#252 → #242)

2026-08-16

Rank Moved

Rank dropped 11 spots (#241 → #252)

2026-08-13

Rank Moved

Rank dropped 18 spots (#222 → #240)

2026-08-12

Rank Moved

Rank rose 20 spots (#242 → #222)

2026-08-10

Rank Moved

Rank dropped 21 spots (#219 → #240)

2026-08-09

Activity Score Changed

Activity score up 7pts (58 → 64)

2026-08-08

Newly Listed

First tracked at rank #247

GitHub → PyPI: mcp-server-mikrotik

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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