Mikrotik Rest MCP Server

mikrotik-rest-mcp PyPI v0.1.2

Published by alirezadavoodi — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
93/100
Last scanned
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable
inspection depth (source) — how much of the target the scan could see

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: mikrotik_download_file → mikrotik_get_logs → mikrotik_upload_file. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow mikrotik_download_file → mikrotik_get_logs → mikrotik_upload_file

Tools 130

Each tool and what it can reach — statically extracted from the published source.

  • mikrotik_download_fileingests untrusted input
  • mikrotik_get_logsreads sensitive data
  • mikrotik_get_logs_by_severityreads sensitive data
  • mikrotik_get_logs_by_topicreads sensitive data
  • mikrotik_upload_filenetwork egress
  • mikrotik_add_blackhole_routeno sensitive capability
  • mikrotik_add_default_routeno sensitive capability
  • mikrotik_add_routeno sensitive capability
  • mikrotik_check_route_pathno sensitive capability
  • mikrotik_clear_logsno sensitive capability
  • mikrotik_create_backupno sensitive capability
  • mikrotik_create_basic_firewall_setupno sensitive capability
  • mikrotik_create_dhcp_leaseno sensitive capability
  • mikrotik_create_dhcp_poolno sensitive capability
  • mikrotik_create_dhcp_serverno sensitive capability
  • mikrotik_create_dns_staticno sensitive capability
  • mikrotik_create_filter_ruleno sensitive capability
  • mikrotik_create_firewall_address_listno sensitive capability
  • mikrotik_create_ip_addressno sensitive capability
  • mikrotik_create_ip_poolno sensitive capability
  • mikrotik_create_logging_actionno sensitive capability
  • mikrotik_create_logging_ruleno sensitive capability
  • mikrotik_create_nat_ruleno sensitive capability
  • mikrotik_create_userno sensitive capability
  • mikrotik_create_user_groupno sensitive capability
  • mikrotik_create_vlan_interfaceno sensitive capability
  • mikrotik_create_wireguard_interfaceno sensitive capability
  • mikrotik_create_wireguard_peerno sensitive capability
  • mikrotik_create_wireless_interfaceno sensitive capability
  • mikrotik_disable_dns_staticno sensitive capability
  • mikrotik_disable_filter_ruleno sensitive capability
  • mikrotik_disable_ip_addressno sensitive capability
  • mikrotik_disable_logging_ruleno sensitive capability
  • mikrotik_disable_nat_ruleno sensitive capability
  • mikrotik_disable_routeno sensitive capability
  • mikrotik_disable_userno sensitive capability
  • mikrotik_enable_dns_staticno sensitive capability
  • mikrotik_enable_filter_ruleno sensitive capability
  • mikrotik_enable_ip_addressno sensitive capability
  • mikrotik_enable_logging_ruleno sensitive capability
  • mikrotik_enable_nat_ruleno sensitive capability
  • mikrotik_enable_routeno sensitive capability
  • mikrotik_enable_userno sensitive capability
  • mikrotik_expand_ip_poolno sensitive capability
  • mikrotik_flush_dns_cacheno sensitive capability
  • mikrotik_flush_route_cacheno sensitive capability
  • mikrotik_get_active_usersno sensitive capability
  • mikrotik_get_dhcp_leaseno sensitive capability
  • mikrotik_get_dhcp_poolno sensitive capability
  • mikrotik_get_dhcp_serverno sensitive capability
  • mikrotik_get_dns_cacheno sensitive capability
  • mikrotik_get_dns_cache_statisticsno sensitive capability
  • mikrotik_get_dns_settingsno sensitive capability
  • mikrotik_get_dns_staticno sensitive capability
  • mikrotik_get_filter_ruleno sensitive capability
  • mikrotik_get_firewall_address_listno sensitive capability
  • mikrotik_get_ip_addressno sensitive capability
  • mikrotik_get_ip_poolno sensitive capability
  • mikrotik_get_logging_actionno sensitive capability
  • mikrotik_get_logging_ruleno sensitive capability
  • mikrotik_get_nat_ruleno sensitive capability
  • mikrotik_get_routeno sensitive capability
  • mikrotik_get_route_cacheno sensitive capability
  • mikrotik_get_route_statisticsno sensitive capability
  • mikrotik_get_routing_tableno sensitive capability
  • mikrotik_get_userno sensitive capability
  • mikrotik_get_user_groupno sensitive capability
  • mikrotik_get_vlan_interfaceno sensitive capability
  • mikrotik_get_wireguard_interfaceno sensitive capability
  • mikrotik_get_wireguard_peerno sensitive capability
  • mikrotik_get_wireless_interfaceno sensitive capability
  • mikrotik_get_wireless_registration_tableno sensitive capability
  • mikrotik_list_backupsno sensitive capability
  • mikrotik_list_dhcp_leasesno sensitive capability
  • mikrotik_list_dhcp_poolsno sensitive capability
  • mikrotik_list_dhcp_serversno sensitive capability
  • mikrotik_list_dns_staticno sensitive capability
  • mikrotik_list_filter_rulesno sensitive capability
  • mikrotik_list_firewall_address_listno sensitive capability
  • mikrotik_list_ip_addressesno sensitive capability
  • mikrotik_list_ip_pool_usedno sensitive capability
  • mikrotik_list_ip_poolsno sensitive capability
  • mikrotik_list_logging_actionsno sensitive capability
  • mikrotik_list_logging_rulesno sensitive capability
  • mikrotik_list_nat_rulesno sensitive capability
  • mikrotik_list_routesno sensitive capability
  • mikrotik_list_user_groupsno sensitive capability
  • mikrotik_list_usersno sensitive capability
  • mikrotik_list_vlan_interfacesno sensitive capability
  • mikrotik_list_wireguard_interfacesno sensitive capability
  • mikrotik_list_wireguard_peersno sensitive capability
  • mikrotik_list_wireless_interfacesno sensitive capability
  • mikrotik_move_filter_ruleno sensitive capability
  • mikrotik_move_nat_ruleno sensitive capability
  • mikrotik_remove_dhcp_leaseno sensitive capability
  • mikrotik_remove_dhcp_poolno sensitive capability
  • mikrotik_remove_dhcp_serverno sensitive capability
  • mikrotik_remove_dns_staticno sensitive capability
  • mikrotik_remove_filter_ruleno sensitive capability
  • mikrotik_remove_firewall_address_listno sensitive capability
  • mikrotik_remove_ip_addressno sensitive capability
  • mikrotik_remove_ip_poolno sensitive capability
  • mikrotik_remove_logging_actionno sensitive capability
  • mikrotik_remove_logging_ruleno sensitive capability
  • mikrotik_remove_nat_ruleno sensitive capability
  • mikrotik_remove_routeno sensitive capability
  • mikrotik_remove_userno sensitive capability
  • mikrotik_remove_user_groupno sensitive capability
  • mikrotik_remove_vlan_interfaceno sensitive capability
  • mikrotik_remove_wireguard_interfaceno sensitive capability
  • mikrotik_remove_wireguard_peerno sensitive capability
  • mikrotik_remove_wireless_interfaceno sensitive capability
  • mikrotik_restore_backupno sensitive capability
  • mikrotik_scan_wireless_networksno sensitive capability
  • mikrotik_search_logsno sensitive capability
  • mikrotik_set_dns_serversno sensitive capability
  • mikrotik_update_dhcp_poolno sensitive capability
  • mikrotik_update_dns_staticno sensitive capability
  • mikrotik_update_filter_ruleno sensitive capability
  • mikrotik_update_ip_addressno sensitive capability
  • mikrotik_update_ip_poolno sensitive capability
  • mikrotik_update_logging_actionno sensitive capability
  • mikrotik_update_logging_ruleno sensitive capability
  • mikrotik_update_nat_ruleno sensitive capability
  • mikrotik_update_routeno sensitive capability
  • mikrotik_update_userno sensitive capability
  • mikrotik_update_vlan_interfaceno sensitive capability
  • mikrotik_update_wireguard_interfaceno sensitive capability
  • mikrotik_update_wireguard_peerno sensitive capability
  • mikrotik_update_wireless_interfaceno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.2 latest A 93/100 1 1.8.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mikrotik-rest-mcp/badge.svg)](https://mcptrustchecker.com/registry/mikrotik-rest-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/mikrotik-rest-mcp"><img src="https://mcptrustchecker.com/registry/mikrotik-rest-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mikrotik-rest-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mikrotik-rest-mcp --online --registry pypi

Use the free API → How scoring works

More in API Development