mikrotik-mcp (vesact/mikrotik-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
21 days ago

mikrotik-mcp

MCP server for managing MikroTik RouterOS fleets, exposing 65+ tools for system administration, interfaces, firewall, DHCP/DNS, PPP, diagnostics, and SSH command execution with KeePass-backed credentials.

→ vesact/mikrotik-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

vesact

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: KEEPASS_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configKEEPASS_GROUPmikrotik Vault group to enumerate devices from
🔐 secretKEEPASS_PASSWORDcp .env.example .env # set at minimum
configKEEPASS_PATH"": "/path/to/vault.kdbx",
configMCP_HOST0.0.0.0 HTTP bind address
configMCP_HTTP_PORT3000 (8000 in the Docker image) HTTP listen port
configMCP_TRANSPORTstdio (http in the Docker image) MCP transport
configREAD_ONLYfalse Expose only read-only state-query tools
configROUTEROS_REST_PORT443 REST API port on target devices
configROUTEROS_REST_SCHEMEhttps https or http
configROUTEROS_SETUP_PORT80 (unchanged) Target www port when bootstrapping via setup-new-device
configROUTEROS_TIMEOUT_MS10000 REST request timeout
configSSH_TIMEOUT_MS10000 Per-command SSH timeout (ros-command)
configTEST_REST_PORT
configTEST_REST_SCHEME
// quality suggestions

Tool annotations

1/65 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

64/65 tools missing one or more hints — device-list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); system-ntp-get (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); system-snmp-get (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +61 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

64/65 tool handlers declare input schemas (98%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 1/65 tool handlers wrap calls in try/catch (2%)

Wrap each tool handler body in try/catch and return a structured error response.

Shell command execution

4 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Dependency freshness

1/5 production deps stale: kdbxweb@2022-06-19 (4.1y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/vesact-mikrotik-mcp-1cseqm)](https://m8ven.ai/mcp/vesact-mikrotik-mcp-1cseqm)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a6a1e98344da1c8abe5e9ecda8b7ada9c771d7c2
code hash: 47170045801ed169cd8c6fee54856ba84a09e3be078200e8f4460d0375a8ea00
verified: 8/6/2026, 9:06:42 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client