Zeek MCP Server
zeek-mcp
npm
v3.1.2
Source verified
Published by lidless-labs — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for Zeek network analysis framework - query and analyze Zeek logs via AI
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 − 6 = 94. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
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
high Shell/command execution in server code (dist/chunk-3VUI4GIZ.js)MTC-SRC-002
In the server's implementation (`dist/chunk-3VUI4GIZ.js:2744`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rom "path"; import * as child_process from "child_process"; function getPcapConfig() { return { pcapDir: process.e
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/chunk-3VUI4GIZ.js
Tools 39
Each tool and what it can reach — statically extracted from the published source.
zeek_query_httpnetwork egressmisp_add_eventno sensitive capabilitymisp_bulk_lookupno sensitive capabilitymisp_search_iocsno sensitive capabilitynids_sensor_statusno sensitive capabilitypcap_analyzeno sensitive capabilitypcap_listno sensitive capabilitysuricata_alert_summaryno sensitive capabilitysuricata_correlate_zeekno sensitive capabilitysuricata_eve_statsno sensitive capability
Show 29 more tools ↓
suricata_query_alertsno sensitive capabilitythehive_create_alertno sensitive capabilitythehive_create_caseno sensitive capabilitythehive_search_casesno sensitive capabilityzeek_connection_summaryno sensitive capabilityzeek_detect_anomaliesno sensitive capabilityzeek_detect_beaconingno sensitive capabilityzeek_detect_outliersno sensitive capabilityzeek_dhcp_asset_mapno sensitive capabilityzeek_dns_summaryno sensitive capabilityzeek_dns_tunneling_checkno sensitive capabilityzeek_executable_downloadsno sensitive capabilityzeek_expired_certsno sensitive capabilityzeek_investigate_hostno sensitive capabilityzeek_investigate_uidno sensitive capabilityzeek_ja3_fingerprintsno sensitive capabilityzeek_ja3_huntno sensitive capabilityzeek_long_connectionsno sensitive capabilityzeek_network_baselineno sensitive capabilityzeek_query_connectionsno sensitive capabilityzeek_query_dhcpno sensitive capabilityzeek_query_dnsno sensitive capabilityzeek_query_filesno sensitive capabilityzeek_query_noticesno sensitive capabilityzeek_query_sshno sensitive capabilityzeek_query_sslno sensitive capabilityzeek_software_inventoryno sensitive capabilityzeek_ssh_bruteforceno sensitive capabilityzeek_suspicious_httpno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (39 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v3.1.2 latest |
A 94/100 | 1 | 1.13.0 | 2026-09-07 |
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.
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 zeek-mcp --onlineMore in Cloud & DevOps
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.