Network Packet Analyzer

Parse pcap and basic pcapng captures, surface protocol hierarchy and session statistics, and export filtered packet summaries

html· HTML resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Request a presigned URL → returns { uploadUrl, storageKey }
curl -X POST 'https://api.elysiatools.com/api/upload/presign/network-packet-analyzer' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"packetFile.ext","contentType":"application/octet-stream","size":12345}'

# 2) PUT the file bytes directly to the presigned uploadUrl
curl -X PUT '<presigned uploadUrl>' \
  --data-binary @/path/to/file.ext

# 3) Call the tool, passing the returned storageKey for each file field
curl -X POST 'https://api.elysiatools.com/en/api/tools/network-packet-analyzer' \
  -F 'packetFile=uploads/2026/01/01/your-tool-1700000000000-abc123.ext' \
  -F 'protocolFilter=dns' \
  -F 'ipFilter=192.168.1.10' \
  -F 'exportFormat=json'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST https://api.elysiatools.com/en/api/tools/network-packet-analyzer

Parameters

Name	Type	Required	Description
packetFile	fileupload required	Yes	—
protocolFilter	select	No	—
ipFilter	text	No	—
exportFormat	select	No	—

File-type parameters must be uploaded first via POST /upload/network-packet-analyzer, then the returned filePath is passed to the corresponding file field.

Response format

HTML result

JSON

{
  "result": "<div>Processed HTML content</div>",
  "error": "Error message (optional)",
  "message": "Notification message (optional)",
  "metadata": {
    "key": "value"
  }
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "mcpServers": {
    "elysiatools-network-packet-analyzer": {
      "name": "network-packet-analyzer",
      "description": "Parse pcap and basic pcapng captures, surface protocol hierarchy and session statistics, and export filtered packet summaries",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=network-packet-analyzer",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "network-packet-analyzer",
    "arguments": {
  "packetFile": "https://example.com/file.ext",
  "protocolFilter": "dns",
  "ipFilter": "192.168.1.10",
  "exportFormat": "json"
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]