mcpcap 0.5.8__tar.gz → 0.5.10__tar.gz

mcpcap-0.5.10/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,106 @@
+name: Bug Report
+description: Report a bug or issue with mcpcap
+title: "[Bug] "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report a bug! Please fill out this form as completely as possible.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Bug Description
+      description: A clear and concise description of what the bug is.
+      placeholder: Describe the bug...
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to Reproduce
+      description: Steps to reproduce the behavior
+      placeholder: |
+        1. Run mcpcap with...
+        2. Analyze PCAP file...
+        3. See error...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: A clear and concise description of what you expected to happen.
+      placeholder: What should have happened?
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happened instead?
+      placeholder: What actually happened?
+    validations:
+      required: true
+
+  - type: textarea
+    id: pcap-info
+    attributes:
+      label: PCAP File Information
+      description: Information about the PCAP file that caused the issue (if applicable)
+      placeholder: |
+        - File size: 
+        - Protocols present: 
+        - Capture tool: 
+        - Any sensitive data removed: Yes/No
+    validations:
+      required: false
+
+  - type: dropdown
+    id: modules
+    attributes:
+      label: Affected Modules
+      description: Which mcpcap modules are affected?
+      multiple: true
+      options:
+        - DNS
+        - DHCP
+        - ICMP
+        - All modules
+        - Unknown
+    validations:
+      required: true
+
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: Information about your environment
+      placeholder: |
+        - mcpcap version: 
+        - Python version: 
+        - Operating system: 
+        - Installation method: pip/git/other
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Error Logs
+      description: If applicable, add any error messages or logs
+      render: shell
+    validations:
+      required: false
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Context
+      description: Add any other context about the problem here
+    validations:
+      required: false

mcpcap-0.5.10/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Documentation
+    url: https://docs.mcpcap.ai
+    about: Check the documentation for usage guides and API reference
+  - name: Discussions
+    url: https://github.com/mcpcap/mcpcap/discussions
+    about: Ask questions and discuss ideas with the community

mcpcap-0.5.10/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,104 @@
+name: Feature Request
+description: Suggest a new feature or enhancement for mcpcap
+title: "[Feature] "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for suggesting a new feature! Please describe your idea clearly.
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Feature Summary
+      description: A brief summary of the feature you'd like to see
+      placeholder: What feature would you like to see added?
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem Statement
+      description: What problem does this feature solve?
+      placeholder: |
+        Is your feature request related to a problem? Please describe.
+        A clear and concise description of what the problem is.
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed Solution
+      description: Describe the solution you'd like
+      placeholder: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+
+  - type: dropdown
+    id: category
+    attributes:
+      label: Feature Category
+      description: What type of feature is this?
+      options:
+        - New protocol support
+        - Analysis enhancement
+        - Performance improvement
+        - User interface
+        - Documentation
+        - Testing
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority Level
+      description: How important is this feature to you?
+      options:
+        - Low - Nice to have
+        - Medium - Would be helpful
+        - High - Important for my use case
+        - Critical - Blocking my work
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternative Solutions
+      description: Describe any alternative solutions or features you've considered
+      placeholder: What alternatives have you considered?
+    validations:
+      required: false
+
+  - type: textarea
+    id: use-cases
+    attributes:
+      label: Use Cases
+      description: Describe specific use cases where this feature would be valuable
+      placeholder: |
+        - Use case 1: ...
+        - Use case 2: ...
+    validations:
+      required: false
+
+  - type: textarea
+    id: implementation
+    attributes:
+      label: Implementation Ideas
+      description: If you have ideas about how this could be implemented, share them here
+      placeholder: Any thoughts on how this could be implemented?
+    validations:
+      required: false
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Context
+      description: Add any other context, screenshots, or examples about the feature request
+    validations:
+      required: false

mcpcap-0.5.10/.github/ISSUE_TEMPLATE/module_request.yml

@@ -0,0 +1,123 @@
+name: Protocol Module Request
+description: Request support for a new network protocol analysis module
+title: "[Module] Add support for [PROTOCOL_NAME]"
+labels: ["enhancement", "module", "protocol"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for requesting a new protocol module! This helps us prioritize which protocols to support next.
+
+  - type: input
+    id: protocol-name
+    attributes:
+      label: Protocol Name
+      description: What protocol would you like mcpcap to support?
+      placeholder: e.g., HTTP, FTP, SSH, etc.
+    validations:
+      required: true
+
+  - type: textarea
+    id: protocol-description
+    attributes:
+      label: Protocol Description
+      description: Brief description of the protocol and its purpose
+      placeholder: What does this protocol do? What is it used for?
+    validations:
+      required: true
+
+  - type: dropdown
+    id: protocol-layer
+    attributes:
+      label: OSI Layer
+      description: Which OSI layer does this protocol primarily operate at?
+      options:
+        - Layer 2 - Data Link
+        - Layer 3 - Network  
+        - Layer 4 - Transport
+        - Layer 5 - Session
+        - Layer 6 - Presentation
+        - Layer 7 - Application
+        - Multiple layers
+        - Unknown/Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: use-cases
+    attributes:
+      label: Use Cases
+      description: What specific analysis would you want to perform on this protocol?
+      placeholder: |
+        - Security analysis: ...
+        - Performance monitoring: ...
+        - Troubleshooting: ...
+        - Compliance: ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: analysis-goals
+    attributes:
+      label: Analysis Goals
+      description: What specific information should the module extract or analyze?
+      placeholder: |
+        - Packet counts and sizes
+        - Connection patterns
+        - Error rates
+        - Specific protocol fields
+        - Security indicators
+    validations:
+      required: true
+
+  - type: input
+    id: rfc-standards
+    attributes:
+      label: RFC or Standards
+      description: Are there RFC documents or standards that define this protocol?
+      placeholder: e.g., RFC 793, IEEE 802.11, etc.
+    validations:
+      required: false
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority Level
+      description: How important is this protocol support to your work?
+      options:
+        - Low - Nice to have
+        - Medium - Would be helpful
+        - High - Important for my use case
+        - Critical - Blocking my work
+    validations:
+      required: true
+
+  - type: textarea
+    id: sample-data
+    attributes:
+      label: Sample Data Availability
+      description: Do you have sample PCAP files with this protocol that could help with development?
+      placeholder: |
+        - Yes, I can provide sanitized samples
+        - Yes, but they contain sensitive data
+        - No, but I can generate some
+        - No sample data available
+    validations:
+      required: false
+
+  - type: textarea
+    id: existing-tools
+    attributes:
+      label: Existing Analysis Tools
+      description: Are there existing tools that analyze this protocol? How would mcpcap be different/better?
+      placeholder: What tools currently exist for analyzing this protocol?
+    validations:
+      required: false
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Context
+      description: Any other information that would help with implementing this module
+    validations:
+      required: false

{mcpcap-0.5.8 → mcpcap-0.5.10}/.github/workflows/release.yml

@@ -23,10 +23,21 @@ jobs:
       with:
         python-version: "3.11"
 
+    - name: Install uv
+      uses: astral-sh/setup-uv@v4
+
+    - name: Cache uv dependencies
+      uses: actions/cache@v4
+      with:
+        path: ~/.cache/uv
+        key: ${{ runner.os }}-uv-release-${{ hashFiles('pyproject.toml') }}
+        restore-keys: |
+          ${{ runner.os }}-uv-release-
+          ${{ runner.os }}-uv-
+
     - name: Install build dependencies
       run: |
-        python -m pip install --upgrade pip
-        pip install build setuptools-scm[toml]
+        uv pip install --system build setuptools-scm[toml]
 
     - name: Verify version matches tag
       run: |
@@ -53,7 +64,7 @@ jobs:
 
     - name: Verify package contents
       run: |
-        pip install twine
+        uv pip install --system twine
         twine check dist/*
 
     - name: Create GitHub Release
@@ -107,26 +118,14 @@ jobs:
           echo "server.json not found at repo root; skipping version update"
         fi
 
-    # -------- MCP Registry: install publisher (build from source) --------------
-    - name: Set up Go (for building mcp-publisher)
-      if: steps.pypi_publish.outcome == 'success'
-      uses: actions/setup-go@v5
-      with:
-        go-version: '1.24.x'
-
+    # -------- MCP Registry: install publisher (pre-built binary) ---------------
     - name: Install MCP Publisher
       if: steps.pypi_publish.outcome == 'success'
       run: |
         set -euo pipefail
-        git clone https://github.com/modelcontextprotocol/registry publisher-repo
-        cd publisher-repo
-        make publisher
-        # Verify expected output location and copy to repo root
-        test -f bin/mcp-publisher || { echo "mcp-publisher binary not found at bin/mcp-publisher"; ls -R; exit 1; }
-        cp bin/mcp-publisher ../mcp-publisher
-        cd ..
-        chmod +x mcp-publisher
-        ./mcp-publisher --version || true
+        curl -L "https://github.com/modelcontextprotocol/registry/releases/download/v1.0.0/mcp-publisher_1.0.0_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
+        sudo mv mcp-publisher /usr/local/bin/
+        mcp-publisher --version
 
     # -------- MCP Registry: login with DNS (mcpcap.ai) ------------------------
     # Secret MCP_PRIVATE_KEY must be a 64-character hex Ed25519 private key
@@ -141,12 +140,12 @@ jobs:
 
     - name: Login to MCP Registry (DNS)
       if: steps.pypi_publish.outcome == 'success'
-      run: ./mcp-publisher login dns --domain mcpcap.ai --private-key "${{ secrets.MCP_PRIVATE_KEY }}"
+      run: mcp-publisher login dns --domain mcpcap.ai --private-key "${{ secrets.MCP_PRIVATE_KEY }}"
 
     # -------- MCP Registry: publish -------------------------------------------
     - name: Publish to MCP Registry
       if: steps.pypi_publish.outcome == 'success'
-      run: ./mcp-publisher publish
+      run: mcp-publisher publish
 
     - name: Upload build artifacts
       uses: actions/upload-artifact@v4

{mcpcap-0.5.8 → mcpcap-0.5.10}/.github/workflows/test.yml

@@ -24,10 +24,21 @@ jobs:
       with:
         python-version: ${{ matrix.python-version }}
 
+    - name: Install uv
+      uses: astral-sh/setup-uv@v4
+
+    - name: Cache uv dependencies
+      uses: actions/cache@v4
+      with:
+        path: ~/.cache/uv
+        key: ${{ runner.os }}-uv-${{ matrix.python-version }}-${{ hashFiles('pyproject.toml') }}
+        restore-keys: |
+          ${{ runner.os }}-uv-${{ matrix.python-version }}-
+          ${{ runner.os }}-uv-
+
     - name: Install dependencies
       run: |
-        python -m pip install --upgrade pip
-        pip install -e .[test]
+        uv pip install --system -e .[test]
         
     - name: Check version detection
       run: |
@@ -35,7 +46,7 @@ jobs:
         
     - name: Run linting with ruff
       run: |
-        pip install ruff
+        uv pip install --system ruff
         ruff check .
         ruff format --check .
         
@@ -54,11 +65,22 @@ jobs:
       uses: actions/setup-python@v5
       with:
         python-version: "3.11"
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@v4
+
+    - name: Cache uv dependencies
+      uses: actions/cache@v4
+      with:
+        path: ~/.cache/uv
+        key: ${{ runner.os }}-uv-check-version-${{ hashFiles('pyproject.toml') }}
+        restore-keys: |
+          ${{ runner.os }}-uv-check-version-
+          ${{ runner.os }}-uv-
         
     - name: Install setuptools-scm
       run: |
-        python -m pip install --upgrade pip
-        pip install setuptools-scm[toml]
+        uv pip install --system setuptools-scm[toml]
         
     - name: Verify version can be determined
       run: |

{mcpcap-0.5.8 → mcpcap-0.5.10}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mcpcap
-Version: 0.5.8
+Version: 0.5.10
 Summary: A modular Python MCP Server for analyzing PCAP files
 Author: mcpcap contributors
 License: MIT License

{mcpcap-0.5.8 → mcpcap-0.5.10}/src/mcpcap/_version.py

@@ -28,7 +28,7 @@ version_tuple: VERSION_TUPLE
 commit_id: COMMIT_ID
 __commit_id__: COMMIT_ID
 
-__version__ = version = '0.5.8'
-__version_tuple__ = version_tuple = (0, 5, 8)
+__version__ = version = '0.5.10'
+__version_tuple__ = version_tuple = (0, 5, 10)
 
-__commit_id__ = commit_id = 'gc6e7a1cea'
+__commit_id__ = commit_id = 'g6be924820'

{mcpcap-0.5.8 → mcpcap-0.5.10}/src/mcpcap.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mcpcap
-Version: 0.5.8
+Version: 0.5.10
 Summary: A modular Python MCP Server for analyzing PCAP files
 Author: mcpcap contributors
 License: MIT License

{mcpcap-0.5.8 → mcpcap-0.5.10}/src/mcpcap.egg-info/SOURCES.txt

@@ -6,6 +6,10 @@ README.md
 pyproject.toml
 server.json
 .github/FUNDING.yml
+.github/ISSUE_TEMPLATE/bug_report.yml
+.github/ISSUE_TEMPLATE/config.yml
+.github/ISSUE_TEMPLATE/feature_request.yml
+.github/ISSUE_TEMPLATE/module_request.yml
 .github/workflows/release.yml
 .github/workflows/test.yml
 docs/Makefile