MCP servers › io.github.wiresage › mikrotik-mcp
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
io.github.wiresage/mikrotik-mcp
MCP server for MikroTik routers: firewall, NAT, routing, DHCP, DNS, WireGuard and more via SSH. — the publisher's description
Summary
io.github.wiresage/mikrotik-mcp is a local MCP server listed in the official MCP registry at version 0.25.1.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 212 tools, 0 resources and 0 prompts.
Record checks
8 of 8 record checks met · 1 does not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #213 of 15,112 packages by monthly downloads
- #418 of 22,952 repositories by GitHub stars, tied with 1 other
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- local package
- Transport
- standard input/output
- Package
- PyPI · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Tools
- 212
- Described as changing data
- 116 of 212 toolsAI-classified
- Mainly works on
- files and code on the machine it runs onAI-classified
- Topic
- cloud-and-devopsAI-classified
- Last tested
- 2026-10-23
Worth knowing before you connect it
- 116 tools are described as changing something (create_backup, create_export, upload_file, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 0.25.1.0, published 2026-10-20 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-11 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 7 versions listed, 2026-10-11 to 2026-10-20; 7 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 7 versions
0.25.1.0· 2026-10-200.25.0.0· 2026-10-190.24.5.0· 2026-10-180.24.4.0· 2026-10-180.24.3.0· 2026-10-180.24.2.0· 2026-10-110.24.1.0· 2026-10-11
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.25.1.0 (published 2026-10-20).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventoryWhat it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.
116 of 212 tools are described as changing something (creating, editing, deleting, sending or running). For 12 the reading was uncertain, so no mark is shown.
“Creates a system backup on the MikroTik device.”
Publisher declares: destructive no · open-world no
5 inputs
namestring or nulldont_encryptbooleaninclude_passwordbooleancommentstring or nulldevicestring or null
“Lists backup files on the MikroTik device.”
Publisher declares: read-only yes · idempotent yes · open-world no
3 inputs
name_filterstring or nullinclude_exportsbooleandevicestring or null
“Creates a configuration export file (rsc/json/xml) on the MikroTik device.”
Publisher declares: destructive no · open-world no
8 inputs
namestring or nullfile_formatstringexport_typestringhide_sensitivebooleanverbosebooleancompactbooleancommentstring or nulldevicestring or null
“Returns a RouterOS configuration section as an export script.”
Publisher declares: read-only yes · idempotent yes · open-world no
4 inputs, 1 required
sectionstringrequiredhide_sensitivebooleancompactbooleandevicestring or null
“Downloads a backup or export file from the MikroTik device as base64-encoded content.”
Publisher declares: read-only yes · idempotent yes · open-world no
3 inputs, 1 required
filenamestringrequiredfile_typestringdevicestring or null
“Uploads a base64-encoded file to the MikroTik device (for restore operations).”
Publisher declares: destructive no · open-world no
3 inputs, 2 required
filenamestringrequiredcontent_base64stringrequireddevicestring or null
“Restores a system backup on the MikroTik device; triggers a reboot.”
Publisher declares: destructive yes · open-world no
3 inputs, 1 required
filenamestringrequiredpasswordstring or nulldevicestring or null
“Imports and executes a RouterOS configuration script (.rsc file) on the device.”
Publisher declares: destructive yes · open-world no
4 inputs, 1 required
filenamestringrequiredrun_after_resetbooleanverbosebooleandevicestring or null
“Removes a file from the MikroTik device filesystem.”
Publisher declares: destructive yes · open-world no
2 inputs, 1 required
filenamestringrequireddevicestring or null
“Gets detailed information about a backup file on the MikroTik device.”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
filenamestringrequireddevicestring or null
“Creates a DHCP server bound to the specified interface on the MikroTik device.”
Publisher declares: destructive no · open-world no
9 inputs, 2 required
namestringrequiredinterfacestringrequiredlease_timestringaddress_poolstring or nulldisabledbooleanauthoritativestringdelay_thresholdstring or nullcommentstring or nulldevicestring or null
“Lists DHCP servers on the MikroTik device.”
Publisher declares: read-only yes · idempotent yes · open-world no
5 inputs
name_filterstring or nullinterface_filterstring or nulldisabled_onlybooleaninvalid_onlybooleandevicestring or null
Show 88 more tools
“Lists detailed IPv4 DHCP leases, optionally filtering active lease fields.”
Publisher declares: read-only yes · idempotent yes · open-world no
10 inputs
address_filterstring or nullmac_filterstring or nullclient_id_filterstring or nullserver_filterstring or nullstatus_filterstring or nulllease_time_filterstring or nulllast_seen_withinstring or nullhostname_filterstring or nullclass_id_filterstring or nulldevicestring or null
“Lists detailed DHCPv6 bindings.”
Publisher declares: read-only yes · idempotent yes · open-world no
8 inputs
address_filterstring or nullduid_filterstring or nulliaid_filterstring or nullserver_filterstring or nullstatus_filterstring or nulllease_time_filterstring or nulllast_seen_withinstring or nulldevicestring or null
“Gets detailed information about a specific DHCP server.”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
namestringrequireddevicestring or null
“Creates a DHCP network configuration (gateway, DNS, domain, etc.) on the MikroTik device.”
Publisher declares: destructive no · open-world no
10 inputs, 2 required
networkstringrequiredgatewaystringrequirednetmaskstring or nulldns_serversarray or nulldomainstring or nullwins_serversarray or nullntp_serversarray or nulldhcp_optionarray or nullcommentstring or nulldevicestring or null
“Updates fields on an existing DHCP network entry on the MikroTik device.”
Publisher declares: destructive no · idempotent yes · open-world no
10 inputs, 1 required
networkstringrequiredgatewaystring or nullnetmaskstring or nulldns_serversarray or nulldomainstring or nullwins_serversarray or nullntp_serversarray or nulldhcp_optionarray or nullcommentstring or nulldevicestring or null
“Removes a DHCP network configuration from the MikroTik device.”
Publisher declares: destructive yes · idempotent yes · open-world no
2 inputs, 1 required
networkstringrequireddevicestring or null
“Creates a DHCP address pool with the given IP ranges on the MikroTik device.”
Publisher declares: destructive no · open-world no
5 inputs, 2 required
namestringrequiredrangesstringrequirednext_poolstring or nullcommentstring or nulldevicestring or null
“Removes a DHCP server from the MikroTik device.”
Publisher declares: destructive yes · idempotent yes · open-world no
2 inputs, 1 required
namestringrequireddevicestring or null
“Sets DNS server configuration.”
Publisher declares: destructive no · open-world no
10 inputs, 1 required
serversarrayrequiredallow_remote_requestsbooleanmax_udp_packet_sizeinteger or nullmax_concurrent_queriesinteger or nullcache_sizeinteger or nullcache_max_ttlstring or nulluse_dohbooleandoh_serverstring or nullverify_doh_certbooleandevicestring or null
“Gets current DNS configuration.”
Publisher declares: read-only yes · idempotent yes · open-world no
1 input
devicestring or null
“Adds a static DNS entry.”
Publisher declares: destructive no · open-world no
15 inputs, 1 required
namestringrequiredaddressstring or nullcnamestring or nullmx_preferenceinteger or nullmx_exchangestring or nulltextstring or nullsrv_priorityinteger or nullsrv_weightinteger or nullsrv_portinteger or nullsrv_targetstring or nullttlstring or nullcommentstring or nulldisabledbooleanregexpstring or nulldevicestring or null
“Lists static DNS entries.”
Publisher declares: read-only yes · idempotent yes · open-world no
6 inputs
name_filterstring or nulladdress_filterstring or nulltype_filterstring or nulldisabled_onlybooleanregexp_onlybooleandevicestring or null
“Gets details of a specific static DNS entry.”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
entry_idstringrequireddevicestring or null
“Updates a static DNS entry.”
Publisher declares: destructive no · idempotent yes · open-world no
16 inputs, 1 required
entry_idstringrequirednamestring or nulladdressstring or nullcnamestring or nullmx_preferenceinteger or nullmx_exchangestring or nulltextstring or nullsrv_priorityinteger or nullsrv_weightinteger or nullsrv_portinteger or nullsrv_targetstring or nullttlstring or nullcommentstring or nulldisabledboolean or nullregexpstring or nulldevicestring or null
“Removes a static DNS entry.”
Publisher declares: destructive yes · idempotent yes · open-world no
2 inputs, 1 required
entry_idstringrequireddevicestring or null
“Enables a static DNS entry.”
Publisher declares: destructive no · idempotent yes · open-world no
2 inputs, 1 required
entry_idstringrequireddevicestring or null
“Disables a static DNS entry.”
Publisher declares: destructive no · idempotent yes · open-world no
2 inputs, 1 required
entry_idstringrequireddevicestring or null
“Gets the current DNS cache.”
Publisher declares: read-only yes · idempotent yes · open-world no
1 input
devicestring or null
“Flushes the DNS cache.”
Publisher declares: destructive yes · idempotent yes · open-world no
1 input
devicestring or null
“Gets DNS cache statistics.”
Publisher declares: read-only yes · idempotent yes · open-world no
1 input
devicestring or null
“Adds a DNS regexp entry.”
Publisher declares: destructive no · open-world no
6 inputs, 2 required
regexpstringrequiredaddressstringrequiredttlstringcommentstring or nulldisabledbooleandevicestring or null
“Tests a DNS query.”
Publisher declares: read-only yes · idempotent yes · open-world no
4 inputs, 1 required
namestringrequiredserverstring or nulltypestringdevicestring or null
“Exports DNS configuration to a file.”
Publisher declares: destructive no · open-world no
2 inputs
filenamestring or nulldevicestring or null
“Adds an entry to an IPv4 or IPv6 firewall address list.”
Publisher declares: destructive no · open-world no
7 inputs, 3 required
familystringrequiredlist_namestringrequiredaddressstringrequiredcommentstring or nulltimeoutstring or nulldisabledbooleandevicestring or null
“Lists IPv4 or IPv6 firewall address list entries.”
Publisher declares: read-only yes · idempotent yes · open-world no
8 inputs, 1 required
familystringrequiredlist_filterstring or nulladdress_filterstring or nullcomment_filterstring or nulldisabled_onlybooleandynamic_onlybooleanstatic_onlybooleandevicestring or null
“Gets one address list entry by list name and address.”
Publisher declares: read-only yes · idempotent yes · open-world no
4 inputs, 3 required
familystringrequiredlist_namestringrequiredaddressstringrequireddevicestring or null
“Updates an address list entry, located by its current list name and address.”
Publisher declares: destructive no · idempotent yes · open-world no
8 inputs, 3 required
familystringrequiredlist_namestringrequiredaddressstringrequirednew_list_namestring or nullcommentstring or nulltimeoutstring or nulldisabledboolean or nulldevicestring or null
“Removes an address list entry by list name and address.”
Publisher declares: destructive yes · idempotent yes · open-world no
4 inputs, 3 required
familystringrequiredlist_namestringrequiredaddressstringrequireddevicestring or null
“Enables an address list entry.”
Publisher declares: destructive no · idempotent yes · open-world no
4 inputs, 3 required
familystringrequiredlist_namestringrequiredaddressstringrequireddevicestring or null
“Disables an address list entry.”
Publisher declares: destructive no · idempotent yes · open-world no
4 inputs, 3 required
familystringrequiredlist_namestringrequiredaddressstringrequireddevicestring or null
“Creates a firewall filter rule in the specified chain on the MikroTik device.”
Publisher declares: destructive no · open-world no
23 inputs, 2 required
chainstringrequiredactionstringrequiredsrc_addressstring or nulldst_addressstring or nullsrc_portstring or nulldst_portstring or nullprotocolstring or nullin_interfacestring or nullout_interfacestring or nullin_interface_liststring or nullout_interface_liststring or nullconnection_statestring or nullconnection_nat_statestring or nullsrc_address_liststring or nulldst_address_liststring or nulllimitstring or nulltcp_flagsstring or nullcommentstring or nulldisabledbooleanlogbooleanlog_prefixstring or nullplace_beforestring or nulldevicestring or null
“Lists firewall filter rules on the MikroTik device.”
Publisher declares: read-only yes · idempotent yes · open-world no
10 inputs
chain_filterstring or nullaction_filterstring or nullsrc_address_filterstring or nulldst_address_filterstring or nullprotocol_filterstring or nullinterface_filterstring or nulldisabled_onlybooleaninvalid_onlybooleandynamic_onlybooleandevicestring or null
“Gets detailed information about a specific firewall filter rule.”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Updates an existing firewall filter rule on the MikroTik device.”
Publisher declares: destructive no · idempotent yes · open-world no
23 inputs, 1 required
rule_idstringrequiredchainstring or nullactionstring or nullsrc_addressstring or nulldst_addressstring or nullsrc_portstring or nulldst_portstring or nullprotocolstring or nullin_interfacestring or nullout_interfacestring or nullin_interface_liststring or nullout_interface_liststring or nullconnection_statestring or nullconnection_nat_statestring or nullsrc_address_liststring or nulldst_address_liststring or nulllimitstring or nulltcp_flagsstring or nullcommentstring or nulldisabledboolean or nulllogboolean or nulllog_prefixstring or nulldevicestring or null
“Removes a firewall filter rule from the MikroTik device.”
Publisher declares: destructive yes · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Moves a firewall filter rule to a different position in the chain.”
Publisher declares: destructive no · idempotent yes · open-world no
3 inputs, 2 required
rule_idstringrequireddestinationintegerrequireddevicestring or null
“Enables a firewall filter rule.”
Publisher declares: destructive no · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Disables a firewall filter rule.”
Publisher declares: destructive no · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Creates a basic firewall setup with common security rules on the MikroTik device.”
Publisher declares: destructive yes · open-world no
1 input
devicestring or null
“Creates a NAT rule (srcnat or dstnat) on the MikroTik device.”
Publisher declares: destructive no · open-world no
17 inputs, 2 required
chainstringrequiredactionstringrequiredsrc_addressstring or nulldst_addressstring or nullsrc_portstring or nulldst_portstring or nullprotocolstring or nullin_interfacestring or nullout_interfacestring or nullto_addressesstring or nullto_portsstring or nullcommentstring or nulldisabledbooleanlogbooleanlog_prefixstring or nullplace_beforestring or nulldevicestring or null
“Lists NAT rules on the MikroTik device.”
Publisher declares: read-only yes · idempotent yes · open-world no
9 inputs
chain_filterstring or nullaction_filterstring or nullsrc_address_filterstring or nulldst_address_filterstring or nullprotocol_filterstring or nullinterface_filterstring or nulldisabled_onlybooleaninvalid_onlybooleandevicestring or null
“Gets detailed information about a specific NAT rule.”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Updates an existing NAT rule on the MikroTik device.”
Publisher declares: destructive no · idempotent yes · open-world no
17 inputs, 1 required
rule_idstringrequiredchainstring or nullactionstring or nullsrc_addressstring or nulldst_addressstring or nullsrc_portstring or nulldst_portstring or nullprotocolstring or nullin_interfacestring or nullout_interfacestring or nullto_addressesstring or nullto_portsstring or nullcommentstring or nulldisabledboolean or nulllogboolean or nulllog_prefixstring or nulldevicestring or null
“Removes a NAT rule from the MikroTik device.”
Publisher declares: destructive yes · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Moves a NAT rule to a different position in the chain.”
Publisher declares: destructive no · idempotent yes · open-world no
3 inputs, 2 required
rule_idstringrequireddestinationintegerrequireddevicestring or null
“Enables a NAT rule.”
Publisher declares: destructive no · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Disables a NAT rule.”
Publisher declares: destructive no · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Lists all interfaces on the MikroTik device (ethernet, bridge, WireGuard, PPPoE, VLAN, WiFi, SFP, LTE, loopback, and any other type).”
Publisher declares: read-only yes · idempotent yes · open-world no
5 inputs
type_filterstring or nullname_filterstring or nullrunning_onlybooleandisabled_onlybooleandevicestring or null
“Gets detailed information about a specific interface by name.”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
namestringrequireddevicestring or null
“Enables an interface on the MikroTik device.”
Publisher declares: destructive no · idempotent yes · open-world no
2 inputs, 1 required
namestringrequireddevicestring or null
“Disables an interface on the MikroTik device.”
Publisher declares: destructive no · idempotent yes · open-world no
2 inputs, 1 required
namestringrequireddevicestring or null
“Lists the MikroTik devices this server manages.”
Publisher declares: read-only yes · idempotent yes · open-world no
Takes no inputs.
“Adds an IP address to an interface on the MikroTik device.”
Publisher declares: destructive no · open-world no
7 inputs, 2 required
addressstringrequiredinterfacestringrequirednetworkstring or nullbroadcaststring or nullcommentstring or nulldisabledbooleandevicestring or null
“Lists IP addresses on the MikroTik device.”
Publisher declares: read-only yes · idempotent yes · open-world no
6 inputs
interface_filterstring or nulladdress_filterstring or nullnetwork_filterstring or nulldisabled_onlybooleandynamic_onlybooleandevicestring or null
“Gets detailed information about a specific IP address by ID or address value.”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
address_idstringrequireddevicestring or null
“Removes an IP address from the MikroTik device by ID or address value.”
Publisher declares: destructive yes · idempotent yes · open-world no
2 inputs, 1 required
address_idstringrequireddevicestring or null
“Adds an IPv6 address to an interface on the MikroTik device.”
Publisher declares: destructive no · open-world no
9 inputs, 2 required
addressstringrequiredinterfacestringrequiredadvertiseboolean or nulleui_64boolean or nullfrom_poolstring or nullno_dadboolean or nullcommentstring or nulldisabledbooleandevicestring or null
“Lists IPv6 addresses on the MikroTik device.”
Publisher declares: read-only yes · idempotent yes · open-world no
7 inputs
interface_filterstring or nulladdress_filterstring or nulldisabled_onlybooleandynamic_onlybooleanglobal_onlybooleanlink_local_onlybooleandevicestring or null
“Gets detailed information about a specific IPv6 address by ID or address value.”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
address_idstringrequireddevicestring or null
“Removes an IPv6 address from the MikroTik device by ID or address value.”
Publisher declares: destructive yes · idempotent yes · open-world no
2 inputs, 1 required
address_idstringrequireddevicestring or null
“Creates an IPv6 firewall filter rule on the MikroTik device.”
Publisher declares: destructive no · open-world no
26 inputs, 2 required
chainstringrequiredactionstringrequiredjump_targetstring or nullsrc_addressstring or nulldst_addressstring or nullsrc_portstring or nulldst_portstring or nullprotocolstring or nullin_interfacestring or nullout_interfacestring or nullconnection_statestring or nullsrc_address_liststring or nulldst_address_liststring or nullsrc_address_typestring or nulldst_address_typestring or nullicmp_optionsstring or nullhop_limitstring or nullheadersstring or nulllimitstring or nulltcp_flagsstring or nullcommentstring or nulldisabledbooleanlogbooleanlog_prefixstring or nullplace_beforestring or null
and 1 more not listed here.
“Lists IPv6 firewall filter rules on the MikroTik device.”
Publisher declares: read-only yes · idempotent yes · open-world no
10 inputs
chain_filterstring or nullaction_filterstring or nullsrc_address_filterstring or nulldst_address_filterstring or nullprotocol_filterstring or nullinterface_filterstring or nulldisabled_onlybooleaninvalid_onlybooleandynamic_onlybooleandevicestring or null
“Gets detailed information about a specific IPv6 firewall filter rule.”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Updates an existing IPv6 firewall filter rule on the MikroTik device.”
Publisher declares: destructive no · idempotent yes · open-world no
26 inputs, 1 required
rule_idstringrequiredchainstring or nullactionstring or nulljump_targetstring or nullsrc_addressstring or nulldst_addressstring or nullsrc_portstring or nulldst_portstring or nullprotocolstring or nullin_interfacestring or nullout_interfacestring or nullconnection_statestring or nullsrc_address_liststring or nulldst_address_liststring or nullsrc_address_typestring or nulldst_address_typestring or nullicmp_optionsstring or nullhop_limitstring or nullheadersstring or nulllimitstring or nulltcp_flagsstring or nullcommentstring or nulldisabledboolean or nulllogboolean or nulllog_prefixstring or null
and 1 more not listed here.
“Removes an IPv6 firewall filter rule from the MikroTik device.”
Publisher declares: destructive yes · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Moves an IPv6 firewall filter rule to a different position in the chain.”
Publisher declares: destructive no · idempotent yes · open-world no
3 inputs, 2 required
rule_idstringrequireddestinationintegerrequireddevicestring or null
“Enables an IPv6 firewall filter rule.”
Publisher declares: destructive no · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Disables an IPv6 firewall filter rule.”
Publisher declares: destructive no · idempotent yes · open-world no
2 inputs, 1 required
rule_idstringrequireddevicestring or null
“Creates an IP pool with the given address ranges on the MikroTik device.”
Publisher declares: destructive no · open-world no
5 inputs, 2 required
namestringrequiredrangesstringrequirednext_poolstring or nullcommentstring or nulldevicestring or null
“Lists IP pools on the MikroTik device.”
Publisher declares: read-only yes · idempotent yes · open-world no
4 inputs
name_filterstring or nullranges_filterstring or nullinclude_usedbooleandevicestring or null
“Gets detailed information about a specific IP pool including used address count.”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
namestringrequireddevicestring or null
“Updates an existing IP pool's name, ranges, or next-pool reference.”
Publisher declares: destructive no · idempotent yes · open-world no
6 inputs, 1 required
namestringrequirednew_namestring or nullrangesstring or nullnext_poolstring or nullcommentstring or nulldevicestring or null
“Removes an IP pool from the MikroTik device (fails if pool is in use).”
Publisher declares: destructive yes · idempotent yes · open-world no
2 inputs, 1 required
namestringrequireddevicestring or null
“Lists currently used (allocated) addresses from IP pools.”
Publisher declares: read-only yes · idempotent yes · open-world no
5 inputs
pool_namestring or nulladdress_filterstring or nullmac_filterstring or nullinfo_filterstring or nulldevicestring or null
“Expands an existing IP pool by appending additional address ranges.”
Publisher declares: destructive no · idempotent yes · open-world no
3 inputs, 2 required
namestringrequiredadditional_rangesstringrequireddevicestring or null
“Gets logs from the MikroTik device with optional topic, time, and message filters.”
Publisher declares: read-only yes · idempotent yes · open-world no
7 inputs
topicsstring or nulltime_filterstring or nullmessage_filterstring or nullprefix_filterstring or nulllimitinteger or nullprint_asstringdevicestring or null
“Gets logs filtered by severity level (debug/info/warning/error/critical).”
Publisher declares: read-only yes · idempotent yes · open-world no
4 inputs, 1 required
severitystringrequiredtime_filterstring or nulllimitinteger or nulldevicestring or null
“Gets logs for a specific topic/facility (system, dhcp, interface, firewall, etc.).”
Publisher declares: read-only yes · idempotent yes · open-world no
4 inputs, 1 required
topicstringrequiredtime_filterstring or nulllimitinteger or nulldevicestring or null
“Searches log messages for a literal term.”
Publisher declares: read-only yes · idempotent yes · open-world no
5 inputs, 1 required
search_termstringrequiredtime_filterstring or nullcase_sensitivebooleanlimitinteger or nulldevicestring or null
“Gets system-related log events (login, reboot, config-change, etc.).”
Publisher declares: read-only yes · idempotent yes · open-world no
4 inputs
event_typestring or nulltime_filterstring or nulllimitinteger or nulldevicestring or null
“Gets security-related log entries (logins, failures, blocked connections, etc.).”
Publisher declares: read-only yes · idempotent yes · open-world no
3 inputs
time_filterstring or nulllimitinteger or nulldevicestring or null
“Explains why MikroTik's in-memory log cannot be cleared on demand.”
Publisher declares: read-only yes · idempotent yes · open-world no
1 input
devicestring or null
“Gets log entry counts by topic and severity from the MikroTik device.”
Publisher declares: read-only yes · idempotent yes · open-world no
1 input
devicestring or null
“Exports logs to a .txt file on the MikroTik device with optional topic and time filters.”
Publisher declares: destructive no · open-world no
4 inputs
filenamestring or nulltopicsstring or nulltime_filterstring or nulldevicestring or null
“Watches for new log entries for a limited duration (max 60s) and returns them.”
Publisher declares: read-only yes · idempotent yes · open-world no
3 inputs
topicsstring or nulldurationintegerdevicestring or null
“Lists detailed IPv4 ARP entries.”
Publisher declares: read-only yes · idempotent yes · open-world no
5 inputs
address_filterstring or nullmac_filterstring or nullinterface_filterstring or nullstatus_filterstring or nulldevicestring or null
“Lists detailed IPv6 neighbor-discovery entries.”
Publisher declares: read-only yes · idempotent yes · open-world no
5 inputs
address_filterstring or nullmac_filterstring or nullinterface_filterstring or nullstatus_filterstring or nulldevicestring or null
“Reads real-time Power-over-Ethernet (PoE) monitor data for one or more ethernet interfaces — PoE-out status, voltage, current, and power.”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
interfacesstringrequireddevicestring or null
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. The first 100 of 212 tools are listed. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 200 tools
- Says what it returns
- 19% of 164 tools
- States limits, defaults or errors
- 6% of 196 tools
- Says when to use it
- 0% of 200 tools
- Items covered per tool
- 1.3 of 4 on average
Counted from the listing
- Parameters with a description
- 0% of 978
- Tools with a description
- 100% of 212
- Typical description length
- 131 characters
The tool set
Counted from the listing
- Tools
- 212
- Size of the list
- about 50,797 tokens for an agent to load (characters ÷ 4)
- Naming
- 212 of 212 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 200 of 212 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the PyPI package mcp-server-mikrotik
Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"mikrotik-mcp": {
"command": "uvx",
"args": [
"mcp-server-mikrotik==0.25.1.0"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mikrotik-mcp": {
"command": "uvx",
"args": [
"mcp-server-mikrotik==0.25.1.0"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"mikrotik-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-server-mikrotik==0.25.1.0"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"mikrotik-mcp","type":"stdio","command":"uvx","args":["mcp-server-mikrotik==0.25.1.0"]}'Claude Code
claude mcp add --transport stdio mikrotik-mcp -- uvx mcp-server-mikrotik==0.25.1.0
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- uvx mcp-server-mikrotik==0.25.1.0
- Optional settings the entry also lists (left out above): MIKROTIK_HOST, MIKROTIK_USERNAME, MIKROTIK_PASSWORD, MIKROTIK_PORT, MIKROTIK_KEY_FILENAME, MIKROTIK_READ_ONLY, MIKROTIK_SENSITIVE_HIDING, MIKROTIK_INVENTORY_FILE, MIKROTIK_INVENTORY.
- This runs the publisher's code on your machine (uvx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.25.1.0
- Latest stable
- 0.25.1.0
- Status
- current
- Withdrawn
- no
Source: pypi.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-10-23 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha256-92b2b2c24ea925a97…
- License
- MIT
Source: the package registry · 2026-10-23.
Usage
- Downloads
- 10,831 in the last month
Source: pypistats.org · 2026-10-23.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Published package can be started | Started and answered | matches | our test · 2026-10-23 |
| Version 0.25.1.0 on PyPI | Exists and can be installed | matches | PyPI · 2026-10-23 |
| Repository github.com/wiresage/mikrotik-mcp | Opens publicly | matches | api.github.com · 2026-10-23 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.wiresage
- GitHub owner
- an organization (wiresage)
- Repository
- github.com/wiresage/mikrotik-mcp
- Stars
- 303
- Repository age
- over a year
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating8 of 8 record checks met · 1 does not apply
- #213 of 15,112 packages by monthly downloads
- #418 of 22,952 repositories by GitHub stars, tied with 1 other
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about io.github.wiresage/mikrotik-mcp
Answered from the data aboveIs io.github.wiresage/mikrotik-mcp safe to install?
We do not rate servers as safe or unsafe. 8 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 116 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.wiresage/mikrotik-mcp been security tested?
Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.
What can io.github.wiresage/mikrotik-mcp do?
It lists 212 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, run code or commands and generate content. We did not call any tool, so this describes the text, not the behaviour.
Can io.github.wiresage/mikrotik-mcp change or delete data?
116 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Does io.github.wiresage/mikrotik-mcp publish a security policy?
Yes: its repository has a public security policy (github.com/wiresage/mikrotik-mcp/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Is the listed version current?
Yes. The registry lists 0.25.1.0, the latest stable release on PyPI.
Where is the source code of io.github.wiresage/mikrotik-mcp?
In github.com/wiresage/mikrotik-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- com.mcparmory/datadogalso has tools that creates or changes data, deletes, runs code or commands, generates content, reads or searchescompare with this one
- com.mcparmory/grafanaalso has tools that creates or changes data, deletes, runs code or commands, generates content, reads or searchescompare with this one
- io.github.emog33k/winrdp-mcpalso has tools that creates or changes data, deletes, runs code or commands, generates content, reads or searchescompare with this one
- io.github.smurfy92/openclaw-control-mcpalso has tools that creates or changes data, deletes, runs code or commands, generates content, reads or searchescompare with this one
- com.osir/domain-registrarOSIR Domain Registraralso has tools that creates or changes data, deletes, runs code or commands, generates content, reads or searchescompare with this one
- com.argosvix/serveralso has tools that creates or changes data, deletes, runs code or commands, generates content, reads or searchescompare with this one
Active servers whose topic is also “cloud-and-devops” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (read-only run)
We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not applicable
- Consent handling: not applicable
- Sign-in metadata: not applicable
2 exercised10 not run (reason given)6 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted the published package in an isolated sandbox (read-only mode)
- 3,412 msConnected after 0 redirects.
- Read the inventory: 212 tools, 0 resources, 0 prompts.
- 4,087 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.wiresage/mikrotik-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.wiresage/mikrotik-mcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.wiresage/mikrotik-mcp)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology