noc-pcap-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_capture_summaryB | Overview of a PCAP file: duration, packet count, protocols seen, top talkers. |
| list_tcp_conversationsA | Enumerate TCP conversations (4-tuple) in a PCAP with packet/byte counts and timing. |
| analyze_tcp_conversationB | RTT, retransmissions, zero-window events and duplicate ACKs for one TCP conversation, citing the frame numbers that evidence each finding. |
| detect_security_anomaliesA | Scan a PCAP for port scans, ARP spoofing, high-entropy DNS queries and cleartext credentials, ranked by severity. |
| extract_json_rpc_exchangeB | Reassemble a TCP conversation's payload, classify JSON-RPC messages and pair requests with responses by id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct layer or task: overall summary, conversation enumeration, per-conversation transport analysis, security scanning, and JSON-RPC payload extraction. Though analyze_tcp_conversation and extract_json_rpc_exchange both work on a conversation, one is transport-focused and the other application-focused, so no reasonable misselection exists.
All tool names follow a clear verb_noun snake_case pattern: get/list/analyze/detect/extract plus a specific object. The singular 'tcp_conversation' after 'analyze_' and the plural in 'list_tcp_conversations' is grammatically consistent, not a style break.
Five tools is a well-scoped set for a PCAP analysis server; each tool provides a distinct capability without redundancy. This is within the ideal range and leaves room for focused use.
The surface covers the core NOC/PCAP workflow: summarize, enumerate conversations, drill into a conversation's health, detect anomalies, and extract application-layer exchanges. A minor gap is the lack of generic packet/filter drill-down or pcap file management, but agents can work around these.