Awslabs Pcap Analyzer MCP Server
awslabs-pcap-analyzer-mcp-server
PyPI
v1.0.1
Published by aws-samples — 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.
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 − 4 = 96. 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 |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 0
Tools 46
Each tool and what it can reach — statically extracted from the published source.
extract_http_requestsnetwork egressanalyze_application_response_timesno sensitive capabilityanalyze_bandwidth_utilizationno sensitive capabilityanalyze_congestion_indicatorsno sensitive capabilityanalyze_connection_lifecycleno sensitive capabilityanalyze_connection_reuseno sensitive capabilityanalyze_connection_timeoutsno sensitive capabilityanalyze_dns_resolution_issuesno sensitive capabilityanalyze_duplicate_acksno sensitive capabilityanalyze_expert_informationno sensitive capability
Show 36 more tools ↓
analyze_geo_asn_mappingno sensitive capabilityanalyze_icmp_errorsno sensitive capabilityanalyze_mtu_fragmentationno sensitive capabilityanalyze_network_latencyno sensitive capabilityanalyze_network_performanceno sensitive capabilityanalyze_network_quality_metricsno sensitive capabilityanalyze_network_topologyno sensitive capabilityanalyze_out_of_order_packetsno sensitive capabilityanalyze_packet_timing_issuesno sensitive capabilityanalyze_pcap_fileno sensitive capabilityanalyze_protocol_anomaliesno sensitive capabilityanalyze_quic_trafficno sensitive capabilityanalyze_security_threatsno sensitive capabilityanalyze_sni_mismatchesno sensitive capabilityanalyze_tcp_resetsno sensitive capabilityanalyze_tcp_retransmissionsno sensitive capabilityanalyze_tcp_window_scalingno sensitive capabilityanalyze_tcp_zero_windowno sensitive capabilityanalyze_tls_alertsno sensitive capabilityanalyze_tls_handshakesno sensitive capabilitydetect_arp_spoofingno sensitive capabilitydetect_dns_tunnelingno sensitive capabilityextract_certificate_detailsno sensitive capabilityextract_credentialsno sensitive capabilityextract_fieldsno sensitive capabilityextract_tls_cipher_analysisno sensitive capabilityfollow_tcp_streamno sensitive capabilityfollow_udp_streamno sensitive capabilitygenerate_throughput_io_graphno sensitive capabilitygenerate_traffic_timelineno sensitive capabilityget_capture_statusno sensitive capabilitylist_captured_filesno sensitive capabilitylist_network_interfacesno sensitive capabilitysearch_packet_contentno sensitive capabilitystart_packet_captureno sensitive capabilitystop_packet_captureno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (46 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 |
|---|---|---|---|---|
v1.0.1 latest |
A 96/100 | 0 | 1.9.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.
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 awslabs-pcap-analyzer-mcp-server --online --registry pypiMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.