Is Mikrotik MCP safe to use?

Mikrotik MCP has an HVTrust score of 75.8/100 (Grade B), ranked #257 of 1374 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 75.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 329 GitHub stars and is categorized under MCP Servers.

Mikrotik MCP

Repository

Website by jeff-nasseri

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

Provenance Attested

Signed commits 0%

Last push 5d ago

Advisories None known

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 75.8/100 (Grade B), ranked #257 of 1374 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.5/10; recent commits are unsigned; no published advisory affects its latest release (mcp-server-mikrotik); last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How Mikrotik MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 5.5 to 9.0lowest checks: CII-Best-Practices 0, Dependency-Update-Tool 0, Fuzzing 0 +7.2 → 83.0 A · #54 of 778
Sign every commit0% signed today +5.0 → 80.8 A · #84 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Mikrotik MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Unsigned

github.com/jeff-nasseri/mikrotik-mcp, MIT, last pushed 2026-11-05. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.5/10 (scanned Oct 31, 2026). The checks that decide who can get a change released:
- Code Review2
- Branch Protection4
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 2

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 9
Published packages Partly attested
- PyPI mcp-server-mikrotik Source link points to this repo's current name Build provenance attested
What you install today No known advisories

Latest release checked: mcp-server-mikrotik 0.27.0.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-08-29 OSSF Scorecard: 5.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Mikrotik MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Mikrotik MCP compares in MCP Servers

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

Where the 75.8 comes from

HVTrust dimensions vs the MCP Servers average

75.8 / 100 · 100.0% confidence

Mikrotik MCP MCP Servers average (778 agents)

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

14.4 / 25

3.6 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.2 / 17

0.9 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

18.3 / 20

6.1 above avg 12.2

AdoptionLog-scaled stars · package downloads

9.9 / 20

2.3 above avg 7.6

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-11-01

Rank Moved

Rank rose 10 spots (#257 → #247)

2026-10-31

Rank Moved

Rank dropped 17 spots (#240 → #257)

2026-10-18

Rank Moved

Rank rose 14 spots (#243 → #229)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/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 View MCP Servers Report missing data

69.2

Activity sub-score · out of 100

#148

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-09-29 2026-11-10

Activity & Reach

Stars

329

Forks

Last Push

2026-11-05

5 days ago

Commits (4 wk)

Downloads (7d)

801

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼4

was #253

Analysis

Activity Inputs

69.2 / 100

StarsRepository reach

15.1 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

20.9 / 25

CommunityFork signal

8.8 / 20

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.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 Mikrotik MCP actively maintained?

Actively maintained. The repository was pushed to within the last 5 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?

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

low confidence

Unknown

Package source metadata is missing or inconclusive

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

Rank Moved

Rank rose 10 spots (#257 → #247)

2026-10-31

Rank Moved

Rank dropped 17 spots (#240 → #257)

2026-10-18

Rank Moved

Rank rose 14 spots (#243 → #229)

2026-10-12

Rank Moved

Rank dropped 66 spots (#163 → #229)

2026-10-12

HVTrust Changed

HVTrust down 3.9pts (79.8 → 75.9)

2026-10-11

Grade Changed

Trust grade A → B

2026-10-11

Rank Moved

Rank dropped 17 spots (#146 → #163)

2026-10-04

Grade Changed

Trust grade B → A

2026-10-04

Rank Moved

Rank rose 17 spots (#152 → #135)

2026-10-02

Grade Changed

Trust grade A → B

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)

GitHub → Website → 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.4 · Raw JSON

Mikrotik MCP

How Mikrotik MCP could raise its score

Chain of custody

Source Unsigned

Review and release Mixed

Published packages Partly attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Mikrotik MCP compares in MCP Servers

Where the 75.8 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Mikrotik MCP

AI agent surface

Maintain Mikrotik MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers