Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Sogl/mikrotik-rest-mcp

PYPI · MIKROTIK-REST-MCP-SERVER

MikroTik RouterOS 7 REST MCP: filtered reads, guarded writes, timed rollback

+20 this week 89 Trust /100

Last scanned (1 day ago)

Scores higher than 92% of PyPI servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Sogl/mikrotik-rest-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 11 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 8509 tokens (~123/item across 69 items; 63 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 64 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 12 Oct 26 +3

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 33. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 13. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Oct 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 0.1.1 → 0.1.2 functional
  • 2 Oct 26 67

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 16 Oct 2026 · Analysed pypi/mikrotik-rest-mcp-server@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo Sogl/mikrotik-rest-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Sogl/mikrotik-rest-mcp/.github/workflows/publish.yml@refs/tags/v0.1.2
Rekor log index 3077878313
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:ad362eb432e793d95cd0fc7fec22ebb94d27bb1c756b503335efc5115a12eb05

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 63 exposed · ~8,412 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
routeros_watch ~285

Sample a REST path N times with an interval; optionally report per-item deltas of numeric fields (diff=true). Useful for watching counters, traffic, registrations.

NameTypeReqDescription
compactboolean–Emit compact single-line JSON per item instead of pretty-printed output.
containsstring–Case-insensitive substring search across the rendered item.
countinteger––
descendingboolean–Reverse sort order when sort_by is set.
diffboolean–Report field deltas between first and last sample instead of raw samples.
fieldsarray–Client-side field projection applied after any RouterOS .proplist request.
intervalnumber––
limitinteger–Limit returned items after filtering and sorting.
pathstringyes–
proplist––Optional RouterOS .proplist for server-side property selection on POST .../print.
query_wordsarray–Optional RouterOS .query stack for server-side filtering on POST .../print.
sort_bystring–Sort by a field name after filtering.
whereobject–Client-side filters applied after any RouterOS .query/.proplist request. Exact match by field, or use suffixes __contains / __in / __not / __startswith / __endswith / __gt / __gte / __lt / __lte.

No output schema declared.

No examples provided.

routeros_write ~77

Mutate a whitelisted RouterOS REST path using POST, PUT, PATCH or DELETE.

NameTypeReqDescription
confirmboolean–Set true only after the user explicitly approves a destructive/disruptive operation.
dataobject|array|string|number|boolean|null––
methodstringyes–
pathstringyes–

No output schema declared.

No examples provided.

run_fetch ~60

Run a bounded RouterOS fetch diagnostic with as-value output and no file writes.

NameTypeReqDescription
addressstring––
hoststring––
http_methodstring––
outputstring––
urlstringyes–

No output schema declared.

No examples provided.

run_ping ~59

Run a bounded RouterOS ping diagnostic via POST /rest/ping.

NameTypeReqDescription
addressstringyes–
countinteger––
interfacestring––
src_addressstring––
vrfstring––

No output schema declared.

No examples provided.

run_script ~47

Run RouterOS system script by name using /rest/system/script/run.

NameTypeReqDescription
confirmboolean–Set true only after the user explicitly approves running this script.
namestringyes–

No output schema declared.

No examples provided.

run_script_inline ~67

Create a temporary RouterOS script, execute it, and remove it. Requires a policy-capable user (yolo mode); always asks for confirmation in careful mode.

NameTypeReqDescription
confirmboolean–Set true only after the user explicitly approves executing this script.
scriptstringyes–

No output schema declared.

No examples provided.

run_traceroute ~81

Run a bounded RouterOS traceroute diagnostic via POST /rest/tool/traceroute.

NameTypeReqDescription
addressstringyes–
countinteger––
interfacestring––
max_hopsinteger––
src_addressstring––
use_dnsboolean––
vrfstring––

No output schema declared.

No examples provided.

run_wifi_monitor ~38

Run a one-shot RouterOS Wi-Fi monitor for an interface via POST /rest/interface/wifi/monitor.

NameTypeReqDescription
interfacestringyes–

No output schema declared.

No examples provided.

safe_status ~18

List pending apply_safe operations and their rollback state.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

save_backup ~49

Create a RouterOS binary backup file on the router via POST /rest/system/backup/save.

NameTypeReqDescription
dont_encryptboolean––
namestringyes–
passwordstring––

No output schema declared.

No examples provided.

save_export ~60

Create a RouterOS text export file on the router via POST /rest/export.

NameTypeReqDescription
compactboolean––
filestringyes–
show_sensitiveboolean––
terseboolean––
verboseboolean––

No output schema declared.

No examples provided.

update_file ~38

Update contents of a small RouterOS text file via POST /rest/file/set.

NameTypeReqDescription
contentsstringyes–
namestringyes–

No output schema declared.

No examples provided.

upload_file ~42

Upload a small local UTF-8 text file to RouterOS via PUT /rest/file.

NameTypeReqDescription
local_pathstringyes–
remote_namestringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.Sogl/mikrotik-rest-mcp server?

io.github.Sogl/mikrotik-rest-mcp runs locally as a PyPI package, launched with uvx mikrotik-rest-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mikrotik-rest-mcp-server

# add to Claude Code
claude mcp add sogl-mikrotik-rest-mcp -- uvx mikrotik-rest-mcp-server
Common questions

What is the io.github.Sogl/mikrotik-rest-mcp server?

io.github.Sogl/mikrotik-rest-mcp is listed in the public MCP registry as io.github.Sogl/mikrotik-rest-mcp. MikroTik RouterOS 7 REST MCP: filtered reads, guarded writes, timed rollback. This page covers its PyPI package (mikrotik-rest-mcp-server).

Is the io.github.Sogl/mikrotik-rest-mcp server safe to use?

io.github.Sogl/mikrotik-rest-mcp scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Sogl/mikrotik-rest-mcp server expose?

io.github.Sogl/mikrotik-rest-mcp exposes 63 tools: get_containers, get_dhcp_leases, get_dhcp_servers, get_files, get_firewall_connections, and 58 more. Their descriptions and schemas cost roughly 8,412 tokens of context every time the server is loaded.

Is the io.github.Sogl/mikrotik-rest-mcp server still maintained?

io.github.Sogl/mikrotik-rest-mcp is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Sogl/mikrotik-rest-mcp server under?

io.github.Sogl/mikrotik-rest-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.