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 (7 hours ago)
Scores higher than 67% 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
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 | allowlisted | 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 →
enable_dns_static ~28
Enables a static DNS entry.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| entry_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_filter_rule ~28
Enables a firewall filter rule.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| rule_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_interface ~54
Enables an interface on the MikroTik device. Notes: name: exact interface name e.g. "ether1", "bridge", "pppoe-out1"
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_ipv6_filter_rule ~32
Enables an IPv6 firewall filter rule.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| rule_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_nat_rule ~27
Enables a NAT rule.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| rule_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_queue_tree ~26
Enables a queue tree.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_route ~47
Enables a route. Notes: route_id: "*N" or "N" from list output e.g. "*3"
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| route_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_safe_mode ~35
Activates MikroTik Safe Mode; changes are held in memory and auto-reverted on disconnect until committed.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_simple_queue ~26
Enables a simple queue.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_user ~24
Enables a user.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_wireguard_interface ~28
Enables a WireGuard interface.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_wireguard_peer ~51
Enables a WireGuard peer. Notes: peer_id: "*N" or "N" from list output e.g. "*2"
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| peer_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
enable_wireless_interface ~27
Enables a wireless interface.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
expand_ip_pool ~113
Expands an existing IP pool by appending additional address ranges. Notes: additional_ranges: hyphen-separated range(s) e.g. "192.168.1.101-192.168.1.150" Multiple ranges comma-separated: "10.0.0.51-10.0.0.60,10.0.0.70-10.0.0.80"
| Name | Type | Req | Description |
|---|---|---|---|
| additional_ranges | string | yes | – |
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
export_dns_config ~27
Exports DNS configuration to a file.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| filename | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
export_logs ~49
Exports logs to a .txt file on the MikroTik device with optional topic and time filters.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| filename | – | – | – |
| time_filter | – | – | – |
| topics | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
export_section ~100
Returns a RouterOS configuration section as an export script. Notes: section: RouterOS path without leading slash e.g. "ip address", "interface vlan", "ip firewall filter", "ip firewall nat", "queue simple" hide_sensitive: keep secrets out of the output (False appends show-sensitive)
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | – |
| device | – | – | – |
| hide_sensitive | boolean | – | – |
| section | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
export_user_config ~27
Exports user configuration to a file.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| filename | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
flush_dns_cache ~20
Flushes the DNS cache.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
flush_route_cache ~20
Flushes the route cache.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_wireguard_client_config ~103
Generates a wg0.conf client config string from the given keys and server endpoint. Does not communicate with the router.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_ips | string | – | – |
| client_address | string | yes | – |
| client_private_key | string | yes | – |
| device | – | – | – |
| dns | – | – | – |
| persistent_keepalive | integer | – | – |
| server_endpoint | string | yes | – |
| server_port | integer | – | – |
| server_public_key | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_active_users ~22
Gets currently active/logged-in users.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_address_list_entry ~48
Gets one address list entry by list name and address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| device | – | – | – |
| family | string | yes | – |
| list_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_dhcp_server ~31
Gets detailed information about a specific DHCP server.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_dns_cache ~20
Gets the current DNS cache.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_dns_cache_statistics ~20
Gets DNS cache statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_dns_settings ~19
Gets current DNS configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_dns_static ~31
Gets details of a specific static DNS entry.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| entry_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_filter_rule ~61
Gets detailed information about a specific firewall filter rule. Notes: rule_id: positional number from list output (e.g. "12") or internal ID (e.g. "*1A")
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| rule_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_interface ~59
Gets detailed information about a specific interface by name. Notes: name: exact interface name e.g. "ether1", "bridge", "pppoe-out1", "wg0"
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ip_address ~36
Gets detailed information about a specific IP address by ID or address value.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | string | yes | – |
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ip_pool ~34
Gets detailed information about a specific IP pool including used address count.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ipsec_active_peers ~116
Lists the IPsec peers with a live IKE session, with uptime and counters. Shows the parent (phase 1) side: `state`, `uptime`, `last-seen` and the byte counters. A peer can sit here `established` while its child SAs carry nothing — use `get_ipsec_installed_sa` to tell the difference. Notes: Both filters are exact matches.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| remote_address_filter | – | – | – |
| state_filter | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ipsec_installed_sa ~423
Lists the installed IPsec security associations (child/phase 2 SAs). The Flags legend is the point of this view. On RouterOS 7 it reads: S - SEEN-TRAFFIC the SA has carried packets H - HW-AEAD the cipher is running in hardware E - ESP `S` is the only field that separates an SA carrying traffic from one that is merely installed. A remote end reporting the connection as up, or its own byte counters growing, does not contradict a missing `S`: those count what the far side sent, not what arrived. Two things this does NOT tell you, both easy to get wrong: - **A missing `S` can mean idle, not broken.** An SA nothing has used looks exactly like one that is failing, and RouterOS withholds `addtime` and `expires-in` until traffic appears, which makes it look half installed. Put traffic over the selector before concluding anything. - **Per-SA counters do not map onto policies once a peer has several child SAs.** Traffic picks among them, so one SA can carry the outbound side of two policies while another sits frozen at the counter it had minutes after install. Pairing SAs by hand — by install time, by address, by lifetime — invents a structure that is not there. Watch which counters move under traffic you control instead. Notes: Address filters are substring matches on the SA endpoints, which are the tunnel endpoints (public addresses), not the encapsulated subnets. Behind NAT-T the endpoints carry the port (`198.51.100.2:4500`), which is why this is not an exact match: filtering on the bare address would find nothing there and report no SAs while some exist.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| dst_address_filter | – | – | – |
| src_address_filter | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ipv6_address ~77
Gets detailed information about a specific IPv6 address by ID or address value. Notes: address_id: a RouterOS internal id (e.g. "*1") or the address value (e.g. "2001:db8::1/64").
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | string | yes | – |
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ipv6_filter_rule ~58
Gets detailed information about a specific IPv6 firewall filter rule. Notes: rule_id: a RouterOS internal id ("*1") or a print position ("0").
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| rule_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_log_statistics ~28
Gets log entry counts by topic and severity from the MikroTik device.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_logs ~139
Gets logs from the MikroTik device with optional topic, time, and message filters. Notes: topics: comma-separated, entry matches any of them e.g. "system,dhcp" time_filter: RouterOS duration e.g. "30s", "5m", "1h", "2d" message_filter: RouterOS regex matched against the message (case-sensitive) limit: keep only the newest N entries
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| limit | – | – | – |
| message_filter | – | – | – |
| prefix_filter | – | – | – |
| print_as | string | – | – |
| time_filter | – | – | – |
| topics | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_logs_by_severity ~49
Gets logs filtered by severity level (debug/info/warning/error/critical).
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| limit | – | – | – |
| severity | string | yes | – |
| time_filter | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_logs_by_topic ~54
Gets logs for a specific topic/facility (system, dhcp, interface, firewall, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| limit | – | – | – |
| time_filter | – | – | – |
| topic | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_nat_rule ~53
Gets detailed information about a specific NAT rule. Notes: rule_id: use the ID from list output e.g. "*1" or "0"
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| rule_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_poe_monitor ~107
Reads real-time Power-over-Ethernet (PoE) monitor data for one or more ethernet interfaces — PoE-out status, voltage, current, and power. Runs ``/interface ethernet poe monitor <interfaces> once``. Notes: interfaces: comma-separated ethernet interface name(s), e.g. "ether1" or "ether9-ap,ether10-ap,ether11-ap,ether12-ap"
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| interfaces | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_poe_settings ~82
Gets the detailed PoE-out settings of a specific ethernet interface (PoE-out mode, priority, voltage, low/high thresholds, …). Runs ``/interface ethernet poe print detail where name=<name>``. Notes: name: exact ethernet interface name, e.g. "ether1"
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_queue_tree ~30
Gets detailed information about a specific queue tree.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_queue_type ~30
Gets detailed information about a specific queue type.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_route ~51
Gets detailed information about a specific route. Notes: route_id: "*N" or "N" from list output e.g. "*3"
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| route_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_route_cache ~19
Gets the route cache.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_route_statistics ~19
Gets routing table statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_routing_table ~41
Gets a specific routing table.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | – |
| device | – | – | – |
| protocol_filter | – | – | – |
| table_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_security_logs ~41
Gets security-related log entries (logins, failures, blocked connections, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| device | – | – | – |
| limit | – | – | – |
| time_filter | – | – | – |
| 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.