Netra
OCI · GHCR.IO/ZYVORAI/NETRA-MCP
eBPF network observability and safe emergency control for Linux and Kubernetes.
Available components
Last scanned (9 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_ebpf_sysctl_audit ~159
Network-hardening/tuning sysctl inventory across agents: per-interface security posture (rp_filter, redirects, source-route, martians, proxy_arp), IPv6 posture, TCP tuning/lifecycle, conntrack timeouts, and ARP/neighbor/bridge settings, flagged against an established hardening baseline where one exists. Context-dependent settings (ip_forward, disable_ipv6, tcp_congestion_control, conntrack timeout durations, etc.) are reported informationally, without a pass/fail verdict. Distinct from netra_ebpf_drops/kernel-network, which are evidence-correlated congestion diagnostics.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max findings/outlier rows per node, 1-500. Default 50. |
No output schema declared.
No examples provided.
netra_ebpf_tls_fingerprint_risk ~42
Rare JA3 / missing-SNI / ECH-extension risk board from capture fingerprints.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items. |
No output schema declared.
No examples provided.
netra_ebpf_tls_fingerprints ~36
JA3/JA4 fingerprints observed from capture-stream ClientHello frames (single-skb). Observe-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_ebpf_topology ~46
A derived service/workload topology view built from current agent reports.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max topology items, 1-1000. Default 100. |
No output schema declared.
No examples provided.
netra_ebpf_workloads ~51
List workload identities (pod/cgroup/container attribution) known to the cluster, optionally for one node.
| Name | Type | Req | Description |
|---|---|---|---|
| node | string | – | Restrict to this node. Omit for all nodes. |
No output schema declared.
No examples provided.
netra_export_audit ~85
Export recent audit events for a SIEM or log pipeline. Formats: json (default), jsonl, cef, syslog (RFC5424), otlp (OTLP/HTTP JSON Logs). Observe-only; no payloads.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Export encoding. |
| limit | integer | – | Max events, 1-500. Default 100. |
No output schema declared.
No examples provided.
netra_export_blocks ~88
Export current blocked/dropped FastPathEvents (5-tuple + reason + process identity) in the SIEM encodings, including otlp-trace — each blocked event becomes one OTLP span for a trace-based backend. No payloads.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Export encoding. |
| limit | integer | – | Max blocked events, 1-2000. Default 200. |
No output schema declared.
No examples provided.
netra_export_events ~100
Export current health anomalies and incident clusters (optionally audit) in the same SIEM encodings as netra_export_audit. include is a comma list of anomaly,incident,audit.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Export encoding. |
| include | string | – | Comma list of anomaly, incident, audit. Default anomaly,incident. |
| limit | integer | – | Audit cap when include lists audit, 1-500. Default 100. |
No output schema declared.
No examples provided.
netra_export_flows ~70
Export current non-stale destination-flow counters (5-tuple + packets/bytes/blocked) in the SIEM encodings. No payloads.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Export encoding. |
| limit | integer | – | Max flow rows, 1-2000. Default 200. |
No output schema declared.
No examples provided.
netra_export_status ~30
Whether optional syslog push is configured, plus the pull-export endpoints and encodings this controller supports.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_fleet ~19
Compact per-node agent inventory. Observe-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_fleet_clusters ~40
Multi-cluster read-only aggregator: local fleet plus optional NETRA_FLEET_PEERS remotes (name|url|key|tenant).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_fleet_tenants ~28
Partner/MSSP tenant rollup from fleet cluster tenant labels. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_flow_history ~165
Queryable flow history (pod, peer, port, protocol, bytes, drops, comm). 7-day sidecar, no payloads.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Well-known-port hint: mysql, postgres, redis, kafka, grpc, http, https. |
| limit | integer | – | Max records, 1-2000. Default 200. |
| namespace | string | – | Filter by namespace. |
| node | string | – | Filter by node. |
| peer | string | – | Filter by peer IP. |
| pod | string | – | Filter by pod name. |
| protocol | string | – | Filter by protocol, for example tcp. |
| since | string | – | Duration (1h) or RFC3339. Default 1h. Max 168h. |
No output schema declared.
No examples provided.
netra_flow_summary ~155
A bounded, point-in-time summary of recent Hubble flows (top talkers/destinations), optionally filtered. This is the request/response equivalent of the flows/stream SSE endpoint, which this MCP server does not expose.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | Filter by destination IP address or CIDR. |
| direction | string | – | Filter by direction. |
| namespace | string | – | Filter by namespace. |
| number | integer | – | Max underlying flows to sample, 1-5000. Default 500. |
| pod | string | – | Filter by pod name. |
| protocol | string | – | Filter by L4 protocol, e.g. TCP or UDP. |
| verdict | string | – | Filter by Hubble verdict. |
No output schema declared.
No examples provided.
netra_handoff ~37
On-call pack: report + playbook + coverage + fleet + audit + drop reasons.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Pack encoding. |
No output schema declared.
No examples provided.
netra_incidents ~148
Cross-signal incident clusters: health anomalies, behavior/rate drift, exposure, drop-detective findings, and audit events joined by a shared canonical source (workload/pod/cgroup/node), only surfaced once at least two different signal kinds agree on the same source. Drop-detective and audit-event joins are best-effort (joinConfidence="probable") since neither carries direct namespace/pod attribution; joinConfidence="" means the finding is real but couldn't be attributed to a specific workload at all (grouped under sourceKey="control-plane" instead of being dropped).
| Name | Type | Req | Description |
|---|---|---|---|
| auditLimit | integer | – | Max audit events considered, 1-1000. Default 200. |
No output schema declared.
No examples provided.
netra_incidents_timeline ~128
Chronological, human-readable timeline merging the audit log with cluster-health-signature (AI digest fingerprint) transitions. Each entry is a plain sentence, never raw counters. An optional LLM prose rewrite (engine="llm") is attempted only when NETRA_AI_API_KEY is set; the deterministic bullet-point entries are always present and complete on their own.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | RFC3339 timestamp; only entries at or after this time are returned. Omit for everything retained (audit: up to 1000 events; health samples: up to 2h). |
No output schema declared.
No examples provided.
netra_insights_baseline_get ~34
The currently captured behavior baseline, if any (see netra_insights_baseline_capture to create one).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_insights_blast_radius ~140
Multi-hop reachability from one dependency-graph node, breadth-first over observed traffic edges. This is OBSERVED TRAFFIC REACHABILITY, not a policy allow/deny determination — a node with no edges here may still be permitted to reach further destinations that simply weren't observed in this window. Edges may be stale relative to the currently applied policy.
| Name | Type | Req | Description |
|---|---|---|---|
| hops | integer | – | Max hops to traverse, 1-6. Default 3. |
| root | string | yes | Dependency-graph node ID to start from (see netra_insights_dependencies for IDs, e.g. "workload:prod:deployment:api"). |
No output schema declared.
No examples provided.
netra_insights_category_deny ~50
Review-only leased SNI deny drafts for selected app categories (default social,finance).
| Name | Type | Req | Description |
|---|---|---|---|
| categories | string | – | Comma-separated categories. |
| limit | integer | – | Max drafts. |
No output schema declared.
No examples provided.
netra_insights_dependencies ~45
The inferred service dependency graph (who talks to whom, including external destinations).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max edges, 1-5000. Default 500. |
No output schema declared.
No examples provided.
netra_insights_destination_risk ~47
Combined destination risk from intel hits, categories, AI/MCP, DoH/DoT, and volume. Observe-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max destinations. |
No output schema declared.
No examples provided.
netra_insights_drift ~25
Behavior drift findings: how current traffic differs from the captured baseline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_insights_ech_blind ~38
ECH / missing-SNI blindness board. Observe-only; no decrypt.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max findings. |
No output schema declared.
No examples provided.
netra_insights_exfil ~39
Exfil heuristics: destination fan-out, volume, rare hosts. Not DLP.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max findings. |
No output schema declared.
No examples provided.
netra_insights_experience ~44
Workload digital-experience scorecard from connect latency, TCP retrans/RTO, DNS failures. No endpoint agent.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max workloads. |
No output schema declared.
No examples provided.
netra_insights_exposure ~58
Exposure findings combining the dependency graph with behavior and rate drift (e.g. workloads newly reachable from outside the cluster).
| Name | Type | Req | Description |
|---|---|---|---|
| window | string | – | Rate-drift window, e.g. "5m". Default 5m. |
No output schema declared.
No examples provided.
netra_insights_health_trend ~117
Linear time-to-breach projection from recent cluster health-score history. A heuristic trend over a coarse, step-function score, never a statistical guarantee — confidence is always "low" or "medium", never "high". Returns no projection (with an explanatory note) when there's too little history, the trend is flat/improving, the fit is too noisy, or the breach would be beyond a 24h horizon.
| Name | Type | Req | Description |
|---|---|---|---|
| threshold | integer | – | Health-score breach threshold, 0-99. Default 50. |
No output schema declared.
No examples provided.
netra_insights_identity_drafts ~40
ServiceAccount + label identity drafts with review-only CNP sketches. Never auto-applied.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max drafts. |
No output schema declared.
No examples provided.
netra_insights_kernel_notes ~38
Scrubbed kernel log lines about netdev, TCP, UDP, conntrack, and OOM. Not the application journal.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_insights_lateral ~37
Lateral-movement playbooks from scan findings with review-only lease drafts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max playbooks. |
No output schema declared.
No examples provided.
netra_insights_microseg ~51
East-west microsegmentation guidance: prefer PacketWolf on Cilium; Netra lease drafts only when Cilium is absent.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max Netra lease drafts when applicable. |
No output schema declared.
No examples provided.
netra_insights_new_since_start ~151
Behavior-drift findings (new destinations since the captured baseline) whose owning pod/workload started after that baseline — a plausible "first egress after start" correlation, not a precise timing claim (no conversion exists between kernel-boot-monotonic packet timestamps and Kubernetes wall-clock pod start times). Stateless and on-demand: may repeat the same finding across a pod's crash loop, unlike the alert-poller's equivalent which suppresses that for one cycle. Requires a captured behavior baseline (see netra_insights_baseline_capture).
| Name | Type | Req | Description |
|---|---|---|---|
| maxRestarts | integer | – | Exclude pods/workloads with more cumulative container restarts than this. 0 disables the filter. Default 5. |
No output schema declared.
No examples provided.
netra_insights_policy_packs ~50
Review-only sanctioned-egress CiliumNetworkPolicy packs from NETRA_SANCTIONED_HOSTS + observed traffic. Prefer PacketWolf to apply.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max packs. |
No output schema declared.
No examples provided.
netra_insights_policy_review ~125
Full review for one policy recommendation (from netra_insights_recommendations): which live CiliumNetworkPolicy actually governs the workload (best-effort label match, may be ambiguous), a semantic diff against it, a traffic-aware blast-radius check for each destination the diff would remove (CIDR destinations checked against live traffic; FQDN/entity destinations honestly marked "could not correlate", never a false negative), and recent policy revision history. Read-only — never applies anything.
| Name | Type | Req | Description |
|---|---|---|---|
| recommendationId | string | yes | Recommendation ID from netra_insights_recommendations. |
No output schema declared.
No examples provided.
netra_insights_profiles ~41
Bounded kernel stacks for the hottest host comms, plus the kernel wait channel (wchan). Not a user-space flame graph. No argv.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_insights_protocol_downgrades ~138
Workload/host pairs with TLS handshake history at baseline capture time that now also show cleartext HTTP to the same host. Coexistence-tolerant correlation, never a verdict — do not describe a finding as a "downgrade attack", "MITM", or "stripped" TLS. Check l7Degraded/l7DegradedNodes before reading an empty result as "no downgrades": when true, the L7 (TLS SNI / HTTP Host) BPF programs failed to load on those nodes, so visibility there is genuinely incomplete, not clean. Requires a captured behavior baseline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_insights_rate_baseline_get ~37
The currently captured traffic-rate baseline, if any (see netra_insights_rate_baseline_capture to create one).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_insights_rate_drift ~54
How current traffic rates differ from the captured rate baseline.
| Name | Type | Req | Description |
|---|---|---|---|
| window | string | – | Duration string, e.g. "5m", between 30s and 2h. Default 5m. |
No output schema declared.
No examples provided.
netra_insights_rates ~56
Current traffic-rate window (packets/bytes per second) across agents.
| Name | Type | Req | Description |
|---|---|---|---|
| window | string | – | Duration string, e.g. "5m", between 30s and 2h. Default 5m. |
No output schema declared.
No examples provided.
netra_insights_recommendations ~82
Suggested NetworkPolicy changes derived from the dependency graph and observed behavior. Always requires human review before applying (applyRequiresReview is always true in the result).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max recommendations, 1-200. Default 50. |
| namespace | string | – | Filter by namespace. |
| workload | string | – | Filter by workload name. |
No output schema declared.
No examples provided.
netra_insights_red ~57
Per-workload rate, errors, and TCP SRTT over a window. Errors are drops and retransmits, not HTTP status.
| Name | Type | Req | Description |
|---|---|---|---|
| window | string | – | Duration, for example 5m. Max 168h. |
No output schema declared.
No examples provided.
netra_insights_remediations ~85
Proposed remediations combining exposure and drift findings. Always requires human review before applying (reviewRequired is always true, autoApply always false in the result).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max proposals, 1-200. Default 50. |
| window | string | – | Rate-drift window, e.g. "5m". Default 5m. |
No output schema declared.
No examples provided.
netra_insights_shadow_saas ~53
Shadow SaaS / unsanctioned destinations from SNI/Host/DNS vs NETRA_SANCTIONED_HOSTS. Observe-only CASB-lite.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max findings. |
No output schema declared.
No examples provided.
netra_insights_summary ~30
Rollup counts across dependency graph, behavior drift, rate drift, exposure, and remediation insights.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
netra_insights_traces ~70
Inferred service-path spans from flow edges and pod IPs. Not propagated trace context.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Filter by namespace. |
| pod | string | – | Filter by pod name. |
| since | string | – | Duration, for example 15m. Max 168h. |
No output schema declared.
No examples provided.
netra_insights_workload_events ~60
Kubernetes Warning events for pods (OOMKilled, probe failures, BackOff). Not journal or dmesg.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Restrict to this namespace. |
| pod | string | – | Restrict to this pod name. |
No output schema declared.
No examples provided.
netra_insights_zero_trust ~61
Identity-aware Zero Trust allow/deny drafts from live workload traffic. Review-only; never applies. Durable NetPol remains PacketWolf/Cilium when present.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max drafts, 1-200. Default 50. |
No output schema declared.
No examples provided.
netra_intel_dns_hits ~38
DNS/C2-style domain board: intel suffix match + NX/DGA heuristics.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max hits. |
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.