Netra
OCI · GHCR.IO/ZYVORAI/NETRA-MCP
eBPF network observability and safe emergency control for Linux and Kubernetes.
Available components
Last scanned (10 hours ago)
Scores higher than 49% of OCI servers
Category Monitoring and Observability
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 9769 tokens (~66/item across 147 items; 138 tools + 9 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "netra_ebpf_drops" implies "drop" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 139 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Oct 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.10 → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.31.0 → 0.32.0 functional
- 17 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.30.1 → 0.31.0 functional
- 15 Oct 26 35
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 19 Oct 2026 · Analysed oci/ghcr.io/zyvorai/netra-mcp@0.32.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
netra_intel_feed_get ~35
Return the active threat-intel feed status and entries. Loading a feed (PUT) is a separate mutate tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_intel_history ~26
Read retained threat-feed revisions, expiry and status. No rollback or mutation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_intel_hits ~26
Match the active threat-intel feed against live agent metadata. Observe-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_intel_preview ~83
Parse a threat-intel or deny list (JSON entries, CSV type,value,direction, or bare IPs/CIDRs/DNS names) into the shape POST /api/v1/ebpf/deny/import accepts. Applies nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Feed body: JSON, CSV, or newline-separated IPs/CIDRs/names. |
No output schema declared.
No examples provided.
netra_investigate_connection ~140
Compose DNS, flow, netlink, policy explain, path/drop evidence and a confidence scorecard into one failed-connection timeline. Observe-only; never mutates.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Workload namespace. |
| node | string | – | Optional node filter. |
| peer | string | – | Peer IP or hostname. |
| pod | string | – | Pod name. |
| port | integer | – | Destination port. |
| since | string | – | Duration or RFC3339 start. |
| until | string | – | RFC3339 end. |
| window | string | – | Lookback duration, e.g. 15m. Default 15m. |
No output schema declared.
No examples provided.
netra_lease ~27
Enforce-mode lease clock: remaining seconds, expired, or none. Observe-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_listen_queues ~43
Per-node TCP listen queue depth (inet_diag). Observe-only; never changes backlog tunables.
| Name | Type | Req | Description |
|---|---|---|---|
| node | string | – | Limit to one node name. |
No output schema declared.
No examples provided.
netra_metrics_alerts ~38
Active metric health alerts (warning/critical), recent transitions, rules and silences from the declarative metric alert engine. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_metrics_anomalies ~139
Machine-learning anomaly summary: anomaly rate per node and the most anomalous metrics in a window. With highlight_after/highlight_before it also ranks metrics whose distribution changed versus the preceding baseline (metric correlations). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | Window start. Default -900. |
| before | integer | – | Window end. Default now. |
| highlight_after | integer | – | Highlighted range start for correlation ranking. |
| highlight_before | integer | – | Highlighted range end for correlation ranking. |
| nodes | string | – | Comma list of node globs. |
| top | integer | – | Ranked rows to return, default 30. |
No output schema declared.
No examples provided.
netra_metrics_contexts ~91
List per-second metric contexts (for example system.cpu, net.net, disk.space, cgroup.cpu, app.cpu_utilization) with chart instances, dimensions, units and labels per node. Read-only. See docs/metrics.md.
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | – | Family glob, for example net or disk. |
| nodes | string | – | Comma list of node globs. Default all nodes. |
No output schema declared.
No examples provided.
netra_metrics_evidence ~169
Evidence behind a metric over a window: top flow-history peers (ranked by blocked packets for drop metrics, retransmissions for TCP metrics, bytes otherwise), current kernel drop reasons, overlapping capture sessions, other anomalous metrics, and links to drop explain, TCP events, DNS findings and flow history. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | Window start (unix seconds, or negative relative). Default -900. |
| before | integer | – | Window end. Default now. |
| context | string | yes | Metric context, e.g. ebpf.kernel_drops, net.net, workload.red_errors. |
| labels | string | – | Chart labels to narrow flows, e.g. namespace:shop,workload:cart. |
| node | string | – | Node name; empty for all nodes. |
No output schema declared.
No examples provided.
netra_metrics_fleet ~68
Fleet metrics roll-up: this cluster plus every NETRA_FLEET_PEERS peer — nodes, series, anomaly rate over the last 15 minutes, raised metric alerts by severity, top alerts and anomalous dimensions per cluster. Peers are read best-effort. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_metrics_query ~247
Query one metric context as evenly spaced points with a per-point anomaly rate. after/before are unix seconds or negative seconds relative to now (after=-600 is the last ten minutes). The tier (1s, 1m, 1h) is picked from the time range. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | Start, unix seconds or negative relative seconds. Default -600. |
| aggregate | string | – | How series in one group combine. |
| before | integer | – | End, unix seconds or 0 for now. |
| charts | string | – | Comma list of chart globs. |
| context | string | – | Metric context, for example system.cpu. Required. |
| dimensions | string | – | Comma list of dimension globs. |
| group | string | – | Reduction inside a time bucket. |
| group_by | string | – | dimension (default), chart, node, instance, all or label:<key>. |
| labels | string | – | Comma list of key:value label filters; values may use *. |
| nodes | string | – | Comma list of node globs. |
| points | integer | – | Number of points, max 3000. |
No output schema declared.
No examples provided.
netra_namespace_heat ~44
Packets/bytes/blocked rolled up by Kubernetes namespace from agent destination stats.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows, 1-200. Default 30. |
No output schema declared.
No examples provided.
netra_netlink ~122
Read-only RTNL change recorder: link, address, route, neighbor events and optional per-node state snapshots. Never mutates routes, links, addresses, neighbors, or rules. view=events|state|all.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Event kind filter. |
| limit | integer | – | Max events, 1-5000. |
| node | string | – | Limit to one node name. |
| since | string | – | Duration (e.g. 30m) or RFC3339 lower bound. |
| view | string | – | Response shape. |
No output schema declared.
No examples provided.
netra_netlink_findings ~76
Level-triggered netlink findings (default-route loss, uplink down, failed neighbors, recorder overruns). Observe-only; never mutates the stack.
| Name | Type | Req | Description |
|---|---|---|---|
| node | string | – | Limit to one node name. |
| window | string | – | Lookback window, e.g. 1h. Default server window. |
No output schema declared.
No examples provided.
netra_node_resources ~78
Per-node CPU/memory/load-average snapshot plus per-workload cgroup v2 CPU/memory usage, top-N by CPU. A "top"-like view attributed to Kubernetes workloads rather than raw host PIDs. Observe-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max top-CPU workload rows, 1-200. Default 20. |
No output schema declared.
No examples provided.
netra_playbooks ~53
Review-only operator playbook derived from the current report snapshot. AutoApply is always false; steps suggest netractl/API actions a human still has to run.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Playbook encoding. |
No output schema declared.
No examples provided.
netra_pods ~39
List pods known to the cluster, with lockdown status.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Restrict to this namespace. Omit for all namespaces. |
No output schema declared.
No examples provided.
netra_policies_history ~78
List recorded policy revisions (checkpoints, applies, rollbacks, deletes) Netra has captured, optionally filtered by namespace/name.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max revisions to return, 1-200. Default 50. |
| name | string | – | Filter by policy name. |
| namespace | string | – | Filter by namespace. |
No output schema declared.
No examples provided.
netra_policies_history_export ~35
Export the full policy revision archive as JSON (for backup or transfer to another controller via netra_policy_history_import).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_policies_list ~50
List CiliumNetworkPolicies in a namespace, raw from the cluster. Requires Cilium integration to be enabled on the controller.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Namespace to list. Default "default". |
No output schema declared.
No examples provided.
netra_policy_build ~181
Generate a CiliumNetworkPolicy manifest from a simple description, without applying it. Pass the result to netra_policy_plan then netra_policy_apply to actually apply it.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDns | boolean | – | Also allow DNS (UDP/53) egress. |
| kind | string | – | Workload kind the selector targets, e.g. "pod". |
| name | string | yes | Policy name. |
| namespace | string | yes | Namespace the policy applies to. |
| port | integer | – | Allowed destination port. Omit to allow all ports. |
| protocol | string | – | Allowed protocol, e.g. TCP or UDP. Omit for any. |
| selector | object | – | Pod label selector, e.g. {"app":"checkout"}. |
| to | array | – | Allowed egress destinations (CIDRs, FQDNs, or entities). |
No output schema declared.
No examples provided.
netra_policy_gitops_status ~78
GitOps reconciler status: every manifest under NETRA_GITOPS_DIR, its computed change plan, whether it applied, and whether it's drifted (live policy differs from the last GitOps-applied revision — never auto-applied over). 409 if GitOps is not enabled (NETRA_GITOPS_DIR unset).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_policy_lockdown ~125
Generate a deny-all CiliumNetworkPolicy manifest for one workload, without applying it. This only produces the manifest — pass it to netra_policy_plan/netra_policy_apply to actually lock the workload down, and use netra_policy_unlock to remove an already-applied lockdown.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Workload kind. Default "pod". |
| name | string | yes | Workload name. |
| namespace | string | – | Namespace of the workload. Default "default". |
| selector | object | – | Pod label selector. Auto-detected from the live workload if omitted. |
No output schema declared.
No examples provided.
netra_policy_simulate ~116
Evaluate a candidate CiliumNetworkPolicy manifest's egress rules against the observed dependency graph and live workload labels — read-only, applies nothing. toCIDR/toCIDRSet/toEntities/toServices/toEndpoints destinations are precisely computed; toFQDNs destinations are always "unverified" (never a false "denied"), since there is no DNS/SNI→IP correlation to confirm or rule out a match.
| Name | Type | Req | Description |
|---|---|---|---|
| manifest | string | yes | Full CiliumNetworkPolicy manifest (YAML or JSON) to simulate. |
No output schema declared.
No examples provided.
netra_ports ~38
Top destination ports by packet count (protocol/port).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows, 1-200. Default 30. |
No output schema declared.
No examples provided.
netra_protocols ~25
L4 protocol mix (TCP/UDP/…) across current destination stats.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_report ~56
Point-in-time operator briefing (health, drift, exposure, incidents, recent audit). format=markdown (default) or json. Observe-only; never applies policy or extends a lease.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Briefing encoding. |
No output schema declared.
No examples provided.
netra_report_prevention ~43
Threat-prevention-style coverage snapshot: intel hits, lease state, detector findings, AI/DoH/DoT/JA3. Not IPS efficacy %.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_scorecard ~31
Single 0-100 board from health, stale agents, detached programs, missing maps, blocked events.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_security_incidents ~42
Correlate recent DNS, scan and IP/CIDR intel evidence by exact node/namespace/pod. No attack or causal verdict and no enforcement.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_security_optimizer ~31
Read-only review of flat deny predicates. Sampled matches are not rule-hit counters; never applies changes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_status ~42
Overall Netra controller status: fast-path config, agent counts/staleness, baseline and rate-baseline capture state, Hubble status, HA/Cilium flags.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_talkers ~41
Top destination IPs by packet count across current agent reports.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows, 1-200. Default 20. |
No output schema declared.
No examples provided.
netra_vms ~57
List KubeVirt VMs known to the cluster, with lockdown status. `available` in the result indicates whether KubeVirt is installed.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Restrict to this namespace. Omit for all namespaces. |
No output schema declared.
No examples provided.
netra_watchlist_match ~38
Match an intel-grammar list against current flows/events/DNS/SNI. Applies nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Feed body. |
No output schema declared.
No examples provided.
netra_workload_detail ~66
Detailed info for one workload: phase, node, IP, labels, recommended NetworkPolicy selector, matching policies, and lockdown status.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Workload kind. |
| name | string | yes | Workload name. |
| namespace | string | yes | Kubernetes namespace. |
No output schema declared.
No examples provided.
How do I install the Netra MCP server?
Netra runs locally as a container image, launched with docker run --rm -i -e NETRA_URL -e NETRA_API_KEY -e NETRA_MCP_ALLOW_MUTATIONS -e NETRA_MCP_ACTOR ghcr.io/zyvorai/netra-mcp:0.32.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/zyvorai/netra-mcp
claude mcp add zyvorai-netra -- docker run --rm -i -e NETRA_URL -e NETRA_API_KEY -e NETRA_MCP_ALLOW_MUTATIONS -e NETRA_MCP_ACTOR ghcr.io/zyvorai/netra-mcp:0.32.0
This image reads NETRA_URL, NETRA_API_KEY, NETRA_MCP_ALLOW_MUTATIONS and NETRA_MCP_ACTOR. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Netra MCP server?
Netra is an MCP server listed in the public MCP registry as io.github.zyvorai/netra. eBPF network observability and safe emergency control for Linux and Kubernetes. This page covers its container image (ghcr.io/zyvorai/netra-mcp).
Is the Netra MCP server safe to use?
Netra scores 37 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 Netra MCP server expose?
Netra exposes 138 tools: netra_agents, netra_ai_agent, netra_ai_ask, netra_ai_brief, netra_ai_digest, and 133 more. Their descriptions and schemas cost roughly 9,562 tokens of context every time the server is loaded.
Is the Netra MCP server still maintained?
Netra 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 Netra MCP server under?
Netra declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.