scapy-mcp 0.1.0__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,93 @@
1
+ Metadata-Version: 2.5
2
+ Name: scapy-mcp
3
+ Version: 0.1.0
4
+ Summary: MCP server wrapping Scapy — packet crafting, dissection, and live capture
5
+ Project-URL: Homepage, https://github.com/lesleslie/scapy-mcp
6
+ Project-URL: Repository, https://github.com/lesleslie/scapy-mcp
7
+ Author-email: Les Leslie <les@wedgwoodwebworks.com>
8
+ License-Expression: BSD-3-Clause
9
+ License-File: LICENSE
10
+ Classifier: Development Status :: 3 - Alpha
11
+ Classifier: Intended Audience :: Developers
12
+ Classifier: License :: OSI Approved :: BSD License
13
+ Classifier: Programming Language :: Python :: 3
14
+ Classifier: Programming Language :: Python :: 3.14
15
+ Requires-Python: >=3.14
16
+ Requires-Dist: fastmcp>=2.12.0
17
+ Requires-Dist: httpx2>=0.28.1
18
+ Requires-Dist: mcp-common>=0.18.0
19
+ Requires-Dist: oneiric>=0.16.0
20
+ Requires-Dist: pydantic-settings>=2.1.0
21
+ Requires-Dist: pydantic>=2.5.0
22
+ Requires-Dist: scapy>=2.5.0
23
+ Provides-Extra: dev
24
+ Requires-Dist: bandit>=1.7.9; extra == 'dev'
25
+ Requires-Dist: mypy>=1.9.0; extra == 'dev'
26
+ Requires-Dist: pytest-asyncio>=0.23.0; extra == 'dev'
27
+ Requires-Dist: pytest-cov>=4.1.0; extra == 'dev'
28
+ Requires-Dist: pytest>=8.0.0; extra == 'dev'
29
+ Requires-Dist: ruff>=0.4.8; extra == 'dev'
30
+ Description-Content-Type: text/markdown
31
+
32
+ # scapy-mcp
33
+
34
+ > **Scaffold status: PyPI name reservation.** This package is a placeholder scaffold to claim
35
+ > the `scapy-mcp` name on PyPI. The MCP server is not yet implemented.
36
+
37
+ MCP server wrapping [Scapy](https://scapy.net/) — interactive packet
38
+ manipulation library. Provides access to:
39
+
40
+ - **Packet crafting** — build L2/L3/L4 packets from Pythonic layers
41
+ - **Dissection** — decode captured packet bytes into structured summaries
42
+ - **Live capture** — sniff interfaces with optional BPF filters
43
+ - **PCAP I/O** — read and write `.pcap` / `.pcapng` files
44
+ - **Protocol layers** — TCP, UDP, ICMP, ARP, DNS, TLS, raw
45
+
46
+ ## Reserve the PyPI name
47
+
48
+ ```bash
49
+ cd /Users/les/Projects/scapy-mcp
50
+ uv build
51
+ uv publish # uses UV_PUBLISH_TOKEN from env
52
+ ```
53
+
54
+ The package name `scapy-mcp` is currently free on PyPI (verified 2026-08-31).
55
+ Publishing a placeholder 0.1.0 release locks the name.
56
+
57
+ ## Connection to flowscape
58
+
59
+ The `flowscape` design spec
60
+ (`docs/superpowers/specs/2026-08-31-flowscape-design.md`) explicitly lists
61
+ `scapy-mcp` as a future integration under **Out of scope / future work**:
62
+
63
+ > scapy-mcp / unifi-mcp integration — Enrichment plugins for `heuristics.py`
64
+ > / `graph.py` — v2+
65
+
66
+ This scaffold is the name-reservation placeholder for that v2 integration.
67
+
68
+ ## Architecture (planned)
69
+
70
+ Mirrors the `raindropio-mcp` pattern in this ecosystem:
71
+
72
+ - `scapy` as the core packet manipulation dependency
73
+ - `fastmcp` for the MCP server surface (tools = scapy operations)
74
+ - `oneiric` for layered config (`settings/scapy-mcp.yaml`, `local.yaml`,
75
+ env vars) — configures default interface, capture mode (live vs offline),
76
+ optional `SCAPY_MCP_PRIVILEGED_HELPER` for `/dev/bpf*` ACLs
77
+ - `mcp-common` for bootstrap, health endpoints
78
+ - `pydantic`/`pydantic-settings` for typed config models
79
+ - Live capture requires root or a ChmodBPF-style helper (same constraint
80
+ documented for flowscape)
81
+
82
+ ## Status
83
+
84
+ | Phase | State |
85
+ |---|---|
86
+ | PyPI name reservation | **pending** (run `uv publish`) |
87
+ | Spec / plan | not written |
88
+ | Implementation | not started |
89
+ | Tests | not started |
90
+
91
+ ## License
92
+
93
+ BSD-3-Clause.
@@ -0,0 +1,5 @@
1
+ scapy_mcp-0.1.0.dist-info/METADATA,sha256=a6HFDbpJuCaMAy5Gvk5XwoCP0fDJ68YR-gKGtW9LFzY,3303
2
+ scapy_mcp-0.1.0.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
3
+ scapy_mcp-0.1.0.dist-info/entry_points.txt,sha256=RJ-LZbiRjRXyu1jCmE14qOGjcO39PpK0FLbYEZG8uN8,54
4
+ scapy_mcp-0.1.0.dist-info/licenses/LICENSE,sha256=2OhoMJP-Wr6xT8SUiw2Z_JqNxMPleu4EyzijfBh7AKU,1518
5
+ scapy_mcp-0.1.0.dist-info/RECORD,,
@@ -0,0 +1,4 @@
1
+ Wheel-Version: 1.0
2
+ Generator: hatchling 1.32.0
3
+ Root-Is-Purelib: true
4
+ Tag: py3-none-any
@@ -0,0 +1,2 @@
1
+ [console_scripts]
2
+ scapy-mcp = scapy_mcp.__main__:main
@@ -0,0 +1,29 @@
1
+ BSD 3-Clause License
2
+
3
+ Copyright (c) 2026, Les Leslie. All rights reserved.
4
+
5
+ Redistribution and use in source and binary forms, with or without
6
+ modification, are permitted provided that the following conditions are met:
7
+
8
+ 1. Redistributions of source code must retain the above copyright notice,
9
+ this list of conditions and the following disclaimer.
10
+
11
+ 2. Redistributions in binary form must reproduce the above copyright notice,
12
+ this list of conditions and the following disclaimer in the documentation
13
+ and/or other materials provided with the distribution.
14
+
15
+ 3. Neither the name of the copyright holder nor the names of its
16
+ contributors may be used to endorse or promote products derived from
17
+ this software without specific prior written permission.
18
+
19
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
20
+ AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22
+ ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
23
+ LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
24
+ CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
25
+ SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
26
+ INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
27
+ CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
28
+ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
29
+ POSSIBILITY OF SUCH DAMAGE.