# Paqtra (oci · ghcr.io/zyvorai/paqtra-mcp)

Read-only Cilium and Hubble network observability and flow investigation for Kubernetes.

- Trust score: 35/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-19

## Components

- oci · `ghcr.io/zyvorai/paqtra-mcp`: 35/100 (this document), [markdown](https://verifymcp.io/servers/zyvorai-paqtra/ghcr-io-zyvorai-paqtra-mcp.md), [page](https://verifymcp.io/servers/zyvorai-paqtra/ghcr-io-zyvorai-paqtra-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/zyvorai/paqtra-mcp`
- Version: `2.2.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-19.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 23/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1284 tokens (~32/item across 39 items; 39 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 97% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 39 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 40 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Paqtra MCP server?

Paqtra runs locally as a container image, launched with docker run --rm -i -e PAQTRA_URL -e PAQTRA_TOKEN -e PAQTRA_USERNAME -e PAQTRA_PASSWORD ghcr.io/zyvorai/paqtra-mcp:2.2.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add zyvorai-paqtra -- docker run --rm -i -e PAQTRA_URL -e PAQTRA_TOKEN -e PAQTRA_USERNAME -e PAQTRA_PASSWORD ghcr.io/zyvorai/paqtra-mcp:2.2.3
```

This image reads PAQTRA_URL, PAQTRA_TOKEN, PAQTRA_USERNAME and PAQTRA_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "zyvorai-paqtra": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "PAQTRA_URL",
        "-e",
        "PAQTRA_TOKEN",
        "-e",
        "PAQTRA_USERNAME",
        "-e",
        "PAQTRA_PASSWORD",
        "ghcr.io/zyvorai/paqtra-mcp:2.2.3"
      ]
    }
  }
}
```

This image reads PAQTRA_URL, PAQTRA_TOKEN, PAQTRA_USERNAME and PAQTRA_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "zyvorai-paqtra": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "PAQTRA_URL",
        "-e",
        "PAQTRA_TOKEN",
        "-e",
        "PAQTRA_USERNAME",
        "-e",
        "PAQTRA_PASSWORD",
        "ghcr.io/zyvorai/paqtra-mcp:2.2.3"
      ]
    }
  }
}
```

This image reads PAQTRA_URL, PAQTRA_TOKEN, PAQTRA_USERNAME and PAQTRA_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add zyvorai-paqtra -- docker run --rm -i -e PAQTRA_URL -e PAQTRA_TOKEN -e PAQTRA_USERNAME -e PAQTRA_PASSWORD ghcr.io/zyvorai/paqtra-mcp:2.2.3
```

This image reads PAQTRA_URL, PAQTRA_TOKEN, PAQTRA_USERNAME and PAQTRA_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zyvorai-paqtra": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "PAQTRA_URL",
        "-e",
        "PAQTRA_TOKEN",
        "-e",
        "PAQTRA_USERNAME",
        "-e",
        "PAQTRA_PASSWORD",
        "ghcr.io/zyvorai/paqtra-mcp:2.2.3"
      ],
      "enabled": true
    }
  }
}
```

This image reads PAQTRA_URL, PAQTRA_TOKEN, PAQTRA_USERNAME and PAQTRA_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  zyvorai-paqtra:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "PAQTRA_URL", "-e", "PAQTRA_TOKEN", "-e", "PAQTRA_USERNAME", "-e", "PAQTRA_PASSWORD", "ghcr.io/zyvorai/paqtra-mcp:2.2.3"]
```

This image reads PAQTRA_URL, PAQTRA_TOKEN, PAQTRA_USERNAME and PAQTRA_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "zyvorai-paqtra": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "PAQTRA_URL",
        "-e",
        "PAQTRA_TOKEN",
        "-e",
        "PAQTRA_USERNAME",
        "-e",
        "PAQTRA_PASSWORD",
        "ghcr.io/zyvorai/paqtra-mcp:2.2.3"
      ]
    }
  }
}
```

This image reads PAQTRA_URL, PAQTRA_TOKEN, PAQTRA_USERNAME and PAQTRA_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "zyvorai-paqtra": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "PAQTRA_URL",
        "-e",
        "PAQTRA_TOKEN",
        "-e",
        "PAQTRA_USERNAME",
        "-e",
        "PAQTRA_PASSWORD",
        "ghcr.io/zyvorai/paqtra-mcp:2.2.3"
      ]
    }
  }
}
```

This image reads PAQTRA_URL, PAQTRA_TOKEN, PAQTRA_USERNAME and PAQTRA_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 35, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 34, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-15 (score 33)

First indexed and scored.

## MCP tools (39)

### `paqtra_flows` (~82 tokens)

List recent Hubble flows, optionally filtered by namespace or verdict (FORWARDED, DROPPED).

Input parameters:

- `limit` (integer): Maximum rows to return
- `namespace` (string): Kubernetes namespace to filter on
- `offset` (integer): Rows to skip, for paging
- `verdict` (string): FORWARDED or DROPPED

### `paqtra_flow` (~25 tokens)

Get one flow by id.

Input parameters:

- `id` (string, required): Flow id

### `paqtra_flow_stats` (~25 tokens)

Flow totals: forwarded, dropped, requests per second, average latency.

### `paqtra_flow_history` (~52 tokens)

Query stored flow history.

Input parameters:

- `limit` (integer): Maximum rows to return
- `namespace` (string): Kubernetes namespace to filter on
- `offset` (integer): Rows to skip, for paging

### `paqtra_flow_timeline` (~32 tokens)

Flow counts over time from stored history.

Input parameters:

- `namespace` (string): Kubernetes namespace to filter on

### `paqtra_flow_store` (~22 tokens)

Size, retention and health of the flow history store.

### `paqtra_policies` (~41 tokens)

List network policies (Cilium CNP/CCNP) Paqtra can see.

Input parameters:

- `namespace` (string): Kubernetes namespace to filter on

### `paqtra_policy` (~26 tokens)

Get one network policy by id.

Input parameters:

- `id` (string, required): Policy id

### `paqtra_hubble_nodes` (~18 tokens)

Hubble relay node status.

### `paqtra_hubble_metrics` (~17 tokens)

Hubble metrics summary.

### `paqtra_cilium_metrics` (~18 tokens)

Cilium agent metrics summary.

### `paqtra_cilium_features` (~30 tokens)

Enabled Cilium features (kube-proxy replacement, encryption, Hubble, ...).

### `paqtra_cilium_resources` (~55 tokens)

List Cilium custom resources of a kind (for example ciliumnetworkpolicies, ciliumendpoints).

Input parameters:

- `kind` (string, required): Resource kind
- `namespace` (string): Kubernetes namespace to filter on

### `paqtra_cilium_agent` (~37 tokens)

Read-only Cilium agent query (status, endpoints, identities, ...).

Input parameters:

- `what` (string, required): Agent query name

### `paqtra_investigate_path` (~104 tokens)

Answer why workload A cannot reach B: evidence from flows, drops and policy. Stores an evidence bundle; changes no cluster state.

Input parameters:

- `destination` (object, required): object {namespace, name|pod}
- `port` (integer, required): destination port
- `protocol` (string): TCP (default) or UDP
- `source` (object, required): object {namespace, name|pod}
- `time_window_minutes` (integer): look-back, default 60

### `paqtra_investigate_flow` (~48 tokens)

Explain one flow: which policy or condition allowed or dropped it. Stores an evidence bundle; changes no cluster state.

Input parameters:

- `flow_id` (string, required): Flow id to explain

### `paqtra_investigation` (~29 tokens)

Fetch a stored investigation bundle by id.

Input parameters:

- `id` (string, required): Bundle id

### `paqtra_connectivity_paths` (~19 tokens)

Declared connectivity paths being watched.

### `paqtra_connectivity_path_status` (~30 tokens)

Current status of one declared connectivity path.

Input parameters:

- `id` (string, required): Path id

### `paqtra_connectivity_alerts` (~20 tokens)

Connectivity alerts raised by declared paths.

### `paqtra_anomalies` (~40 tokens)

Detected network anomalies.

Input parameters:

- `limit` (integer): Maximum rows to return
- `namespace` (string): Kubernetes namespace to filter on

### `paqtra_anomaly` (~27 tokens)

Get one anomaly by id.

Input parameters:

- `id` (string, required): Anomaly id

### `paqtra_compliance_frameworks` (~17 tokens)

Supported compliance frameworks.

### `paqtra_compliance_audits` (~18 tokens)

Past compliance audits.

### `paqtra_compliance_audit` (~29 tokens)

Get one compliance audit by id.

Input parameters:

- `id` (string, required): Audit id

### `paqtra_security_posture` (~17 tokens)

Overall security posture summary.

### `paqtra_security_findings` (~30 tokens)

Security findings from the dashboard.

Input parameters:

- `namespace` (string): Kubernetes namespace to filter on

### `paqtra_zero_trust` (~19 tokens)

Zero-trust score per namespace.

### `paqtra_rootcause_drops` (~42 tokens)

Recent packet drops with reasons.

Input parameters:

- `limit` (integer): Maximum rows to return
- `namespace` (string): Kubernetes namespace to filter on

### `paqtra_healer_problems` (~28 tokens)

Problems the healer module has detected (listing only; fixes are not exposed).

### `paqtra_events` (~40 tokens)

Recent Kubernetes and Cilium events.

Input parameters:

- `limit` (integer): Maximum rows to return
- `namespace` (string): Kubernetes namespace to filter on

### `paqtra_endpoints` (~27 tokens)

Cilium endpoints.

Input parameters:

- `namespace` (string): Kubernetes namespace to filter on

### `paqtra_nodes` (~19 tokens)

Cluster nodes and their Cilium agent state.

### `paqtra_dependencies` (~28 tokens)

Observed service dependency graph.

Input parameters:

- `namespace` (string): Kubernetes namespace to filter on

### `paqtra_heatmap` (~28 tokens)

Traffic heatmap data.

Input parameters:

- `namespace` (string): Kubernetes namespace to filter on

### `paqtra_ebpf_attachments` (~32 tokens)

BPF program attachments classified as cil_*, netra_* or other (read-only).

### `paqtra_ebpf_drift` (~24 tokens)

BPF attachment drift against the last known state.

### `paqtra_ebpf_programs` (~24 tokens)

Loaded eBPF programs and their runtime stats.

### `paqtra_health` (~13 tokens)

API health.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/zyvorai-paqtra/ghcr-io-zyvorai-paqtra-mcp#diagnostics

## Score history

- 2026-10-19: 35
- 2026-10-18: 35
- 2026-10-17: 34
- 2026-10-16: 33
- 2026-10-15: 33

## Common questions

### What is the Paqtra MCP server?

Paqtra is an MCP server listed in the public MCP registry as io.github.zyvorai/paqtra. Read-only Cilium and Hubble network observability and flow investigation for Kubernetes. This page covers its container image (ghcr.io/zyvorai/paqtra-mcp).

### Is the Paqtra MCP server safe to use?

Paqtra scores 35 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Paqtra MCP server expose?

Paqtra exposes 39 tools: paqtra_flows, paqtra_flow, paqtra_flow_stats, paqtra_flow_history, paqtra_flow_timeline, and 34 more. Their descriptions and schemas cost roughly 1,232 tokens of context every time the server is loaded.

### Is the Paqtra MCP server still maintained?

Paqtra is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Paqtra MCP server under?

Paqtra declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/zyvorai/paqtra-mcp
- Changelog RSS feed: https://verifymcp.io/servers/zyvorai-paqtra/ghcr-io-zyvorai-paqtra-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/zyvorai-paqtra/ghcr-io-zyvorai-paqtra-mcp.json
- HTML version of this page: https://verifymcp.io/servers/zyvorai-paqtra/ghcr-io-zyvorai-paqtra-mcp