io.github.wiresage/mikrotik-mcp
PYPI · MCP-SERVER-MIKROTIK
MCP server for MikroTik routers: firewall, NAT, routing, DHCP, DNS, WireGuard and more via SSH.
Available components
Last scanned (15 hours ago)
Scores higher than 68% of PyPI servers
Category Cloud Infrastructure
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 Security50
- Malware scan not yet available for this package.Unverified
- 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
- 1 of 38 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to wiresage/mikrotik-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 15428 tokens (~72/item across 212 items; 212 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 24 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 213 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 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.
- 26 Oct 26 +1
- Package version: 0.26.1.0 → 0.26.2.0 functional
- 24 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.25.1.0 → 0.26.1.0 functional
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 5 Nov 2026 · Analysed pypi/mcp-server-mikrotik@0.26.2.0
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 | wiresage/mikrotik-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/wiresage/mikrotik-mcp/.github/workflows/publish.yml@refs/heads/master |
| Rekor log index | 3494336129 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:52ab730bf6ff17539f0ea46e29a20737f739a7f494dac53296e1be4420564173 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 38 packages
| Packages resolved | 38 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
update_nat_rule ~209
Updates an existing NAT rule on the MikroTik device. Notes: rule_id: use the ID from list output e.g. "*1" or "0" to_addresses: single IP or range e.g. "10.0.0.1" or "10.0.0.1-10.0.0.10" to_ports: single port or range e.g. "8080" or "8080-8090" Pass "" to clear an optional field.
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | – | – |
| chain | – | – | – |
| comment | – | – | – |
| device | – | – | – |
| disabled | – | – | – |
| dst_address | – | – | – |
| dst_port | – | – | – |
| in_interface | – | – | – |
| log | – | – | – |
| log_prefix | – | – | – |
| out_interface | – | – | – |
| protocol | – | – | – |
| rule_id | string | yes | – |
| src_address | – | – | – |
| src_port | – | – | – |
| to_addresses | – | – | – |
| to_ports | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_queue_tree ~164
Updates an existing queue tree entry (bandwidth limits, parent, priority, etc.). Notes: max_limit / limit_at / burst_limit / burst_threshold: bandwidth e.g. "10M", "512k" burst_time: duration e.g. "8s" priority: 1 (highest) – 8 (lowest)
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_size | – | – | – |
| burst_limit | – | – | – |
| burst_threshold | – | – | – |
| burst_time | – | – | – |
| comment | – | – | – |
| device | – | – | – |
| disabled | – | – | – |
| limit_at | – | – | – |
| max_limit | – | – | – |
| name | string | yes | – |
| new_name | – | – | – |
| packet_mark | – | – | – |
| parent | – | – | – |
| priority | – | – | – |
| queue | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_queue_type ~121
Updates an existing queue type's discipline-specific settings.
| Name | Type | Req | Description |
|---|---|---|---|
| cake_ack_filter | – | – | – |
| cake_diffserv | – | – | – |
| cake_flowmode | – | – | – |
| cake_mpu | – | – | – |
| cake_nat | – | – | – |
| cake_overhead | – | – | – |
| cake_overhead_scheme | – | – | – |
| cake_rtt | – | – | – |
| cake_wash | – | – | – |
| device | – | – | – |
| name | string | yes | – |
| new_name | – | – | – |
| pcq_classifier | – | – | – |
| pcq_limit | – | – | – |
| pcq_rate | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_route ~198
Updates a route. Notes: route_id: "*N" or "N" from list output e.g. "*3" dst_address: CIDR e.g. "192.168.1.0/24" check_gateway: "ping" or "arp" distance: 1-255 routing_table: name of a table from /routing table; "" moves the route back to "main", since every RouterOS 7 route belongs to a table. Pass "" to vrf_interface or pref_src to clear them.
| Name | Type | Req | Description |
|---|---|---|---|
| check_gateway | – | – | – |
| comment | – | – | – |
| device | – | – | – |
| disabled | – | – | – |
| distance | – | – | – |
| dst_address | – | – | – |
| gateway | – | – | – |
| pref_src | – | – | – |
| route_id | string | yes | – |
| routing_table | – | – | – |
| scope | – | – | – |
| target_scope | – | – | – |
| vrf_interface | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_simple_queue ~219
Updates an existing simple queue's rate limits, target, or scheduling settings. Notes: target: IP/CIDR or interface e.g. "192.168.1.0/24" or "ether1" max_limit / limit_at / burst_limit / burst_threshold: upload/download bandwidth as "UL/DL" e.g. "10M/10M", or single value e.g. "10M" burst_time: duration e.g. "8s" priority: 1 (highest) – 8 (lowest)
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_size | – | – | – |
| burst_limit | – | – | – |
| burst_threshold | – | – | – |
| burst_time | – | – | – |
| comment | – | – | – |
| device | – | – | – |
| disabled | – | – | – |
| dst | – | – | – |
| limit_at | – | – | – |
| max_limit | – | – | – |
| name | string | yes | – |
| new_name | – | – | – |
| packet_marks | – | – | – |
| parent | – | – | – |
| priority | – | – | – |
| queue | – | – | – |
| target | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_user ~55
Updates a user.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | – |
| comment | – | – | – |
| device | – | – | – |
| disabled | – | – | – |
| group | – | – | – |
| name | string | yes | – |
| new_name | – | – | – |
| password | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_user_group ~47
Updates a user group.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | – | – | – |
| device | – | – | – |
| name | string | yes | – |
| new_name | – | – | – |
| policy | – | – | – |
| skin | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_vlan_interface ~84
Updates an existing VLAN interface's settings on the MikroTik device.
| Name | Type | Req | Description |
|---|---|---|---|
| arp | – | – | – |
| arp_timeout | – | – | – |
| comment | – | – | – |
| device | – | – | – |
| disabled | – | – | – |
| interface | – | – | – |
| mtu | – | – | – |
| name | string | yes | – |
| new_name | – | – | – |
| use_service_tag | – | – | – |
| vlan_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_wireguard_interface ~69
Updates an existing WireGuard interface's settings on the MikroTik device.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | – | – | – |
| device | – | – | – |
| disabled | – | – | – |
| listen_port | – | – | – |
| mtu | – | – | – |
| name | string | yes | – |
| new_name | – | – | – |
| private_key | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_wireguard_peer ~181
Updates an existing WireGuard peer's allowed addresses, endpoint, keepalive, or enabled state. Notes: peer_id: "*N" or "N" from list output e.g. "*2" allowed_address: CIDR, comma-separated e.g. "10.0.0.2/32" or "10.0.0.0/24,192.168.0.0/24" persistent_keepalive: seconds as string e.g. "25" Pass "" for endpoint_address or preshared_key to clear them.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_address | – | – | – |
| comment | – | – | – |
| device | – | – | – |
| disabled | – | – | – |
| endpoint_address | – | – | – |
| endpoint_port | – | – | – |
| peer_id | string | yes | – |
| persistent_keepalive | – | – | – |
| preshared_key | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_wireless_interface ~62
Updates an existing wireless interface's settings (name, SSID, enabled state, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| comment | – | – | – |
| device | – | – | – |
| disabled | – | – | – |
| name | string | yes | – |
| new_name | – | – | – |
| ssid | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
upload_file ~47
Uploads a base64-encoded file to the MikroTik device (for restore operations).
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | yes | – |
| device | – | – | – |
| filename | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.wiresage/mikrotik-mcp server?
io.github.wiresage/mikrotik-mcp runs locally as a PyPI package, launched with uvx mcp-server-mikrotik. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-server-mikrotik
claude mcp add wiresage-mikrotik-mcp -- uvx mcp-server-mikrotik
What is the io.github.wiresage/mikrotik-mcp server?
io.github.wiresage/mikrotik-mcp is listed in the public MCP registry as io.github.wiresage/mikrotik-mcp. MCP server for MikroTik routers: firewall, NAT, routing, DHCP, DNS, WireGuard and more via SSH. This page covers its PyPI package (mcp-server-mikrotik).
Is the io.github.wiresage/mikrotik-mcp server safe to use?
io.github.wiresage/mikrotik-mcp scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.wiresage/mikrotik-mcp server expose?
io.github.wiresage/mikrotik-mcp exposes 212 tools: create_backup, list_backups, create_export, export_section, download_file, and 207 more. Their descriptions and schemas cost roughly 15,351 tokens of context every time the server is loaded.
Is the io.github.wiresage/mikrotik-mcp server still maintained?
io.github.wiresage/mikrotik-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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.wiresage/mikrotik-mcp server under?
io.github.wiresage/mikrotik-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.
What did VerifyMCP test on the io.github.wiresage/mikrotik-mcp server?
VerifyMCP ran 15 checks on io.github.wiresage/mikrotik-mcp, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.wiresage/mikrotik-mcp: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.