OpenCROW Network Toolbox
Use this skill for network artifact work that spans both Python packet tooling and native capture or triage tools: scapy, tshark, tcpdump, nmap, nc, and socat.
Quick Start
Start the MCP server from the installed CLI:
opencrow-network-mcp
Run inline Python in ctf:
python ~/.codex/skills/opencrow-network-toolbox/scripts/run_network_python.py --code 'from scapy.all import IP, TCP; print((IP(dst=\"127.0.0.1\")/TCP(dport=31337)).summary())'
Run a packet helper:
python ~/.codex/skills/opencrow-network-toolbox/scripts/run_network_python.py --file /absolute/path/to/packets.py
Verify the mapped stack:
python ~/.codex/skills/opencrow-network-toolbox/scripts/verify_toolkit.py
Workflow
- Start with the MCP server and call
toolbox_info, toolbox_verify, and toolbox_capabilities.
- Use
network_pcap_inspect first when you already have a capture or need a quick filtered look at traffic.
- Use
network_scan to map reachable services before deeper protocol work.
- Use
network_socket_probe for one-shot TCP or UDP validation without opening a persistent async session.
- Use
network_python for Scapy-driven packet generation, decoding, or challenge-specific protocol logic.
- Use
netcat-async or ssh-async separately when you need a long-lived interactive session rather than packet tooling.
- Read references/tooling.md for quick guidance.
Tool Selection
- Use
scapy for packet crafting, sniffing, protocol parsing, PCAP analysis, and challenge-specific dissectors.
- Use
opencrow-network-mcp first for typed MCP access to capture inspection, scanning, probing, and Scapy execution.
- Use
tshark for quick PCAP summaries, display filters, and protocol-aware decoding.
- Use
tcpdump for capture creation and fast packet inspection from the shell.
- Use
nmap for host, port, and service discovery before deeper protocol analysis.
- Use
nc or socat for quick socket experiments, port relays, or test servers.
- Use plain Python socket code only when the task is simpler than full packet work.
- Use
netcat-async when the service is an interactive TCP stream and session persistence matters more than packet structure.
Resources
opencrow-network-mcp: stdio MCP server for typed PCAP inspection, scanning, socket probing, and Scapy execution.
scripts/run_network_python.py: execute inline code or a .py file inside the ctf environment.
scripts/verify_toolkit.py: confirm that scapy is available.
references/tooling.md: quick selection notes for network workflows.
1---2name: opencrow-network-toolbox3description: Use the Anaconda `ctf` environment and installed network tooling for packet- and protocol-level CTF tasks. Use when Codex needs `scapy`, `tshark`, `tcpdump`, `nmap`, `nc`, or `socat` for packet work, capture analysis, or service triage.4---5
6# OpenCROW Network Toolbox
7
8Use this skill for network artifact work that spans both Python packet tooling and native capture or triage tools: `scapy`, `tshark`, `tcpdump`, `nmap`, `nc`, and `socat`.
9
10## Quick Start
11
12Start the MCP server from the installed CLI:
13
14```bash
15opencrow-network-mcp
16```
17
18Run inline Python in `ctf`:
19
20```bash
21python ~/.codex/skills/opencrow-network-toolbox/scripts/run_network_python.py --code 'from scapy.all import IP, TCP; print((IP(dst=\"127.0.0.1\")/TCP(dport=31337)).summary())'
22```
23
24Run a packet helper:
25
26```bash
27python ~/.codex/skills/opencrow-network-toolbox/scripts/run_network_python.py --file /absolute/path/to/packets.py
28```
29
30Verify the mapped stack:
31
32```bash
33python ~/.codex/skills/opencrow-network-toolbox/scripts/verify_toolkit.py
34```
35
36## Workflow
37
381. Start with the MCP server and call `toolbox_info`, `toolbox_verify`, and `toolbox_capabilities`.
392. Use `network_pcap_inspect` first when you already have a capture or need a quick filtered look at traffic.
403. Use `network_scan` to map reachable services before deeper protocol work.
414. Use `network_socket_probe` for one-shot TCP or UDP validation without opening a persistent async session.
425. Use `network_python` for Scapy-driven packet generation, decoding, or challenge-specific protocol logic.
436. Use `netcat-async` or `ssh-async` separately when you need a long-lived interactive session rather than packet tooling.
447. Read [references/tooling.md](references/tooling.md) for quick guidance.
45
46## Tool Selection
47
48- Use `scapy` for packet crafting, sniffing, protocol parsing, PCAP analysis, and challenge-specific dissectors.
49- Use `opencrow-network-mcp` first for typed MCP access to capture inspection, scanning, probing, and Scapy execution.
50- Use `tshark` for quick PCAP summaries, display filters, and protocol-aware decoding.
51- Use `tcpdump` for capture creation and fast packet inspection from the shell.
52- Use `nmap` for host, port, and service discovery before deeper protocol analysis.
53- Use `nc` or `socat` for quick socket experiments, port relays, or test servers.
54- Use plain Python socket code only when the task is simpler than full packet work.
55- Use `netcat-async` when the service is an interactive TCP stream and session persistence matters more than packet structure.
56
57## Resources
58
59- `opencrow-network-mcp`: stdio MCP server for typed PCAP inspection, scanning, socket probing, and Scapy execution.
60- `scripts/run_network_python.py`: execute inline code or a `.py` file inside the `ctf` environment.
61- `scripts/verify_toolkit.py`: confirm that `scapy` is available.
62- `references/tooling.md`: quick selection notes for network workflows.