# NVIDIA NemoClaw CKG (pypi · ckg-nvidia-nemoclaw)

NVIDIA NemoClaw knowledge graph — 55 nodes, F1 0.576 (+269% vs RAG), 11x fewer tokens. MCP-native.

- Trust score: 34/100 (low)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `ckg-nvidia-nemoclaw.onrender.com`: 59/100, [markdown](https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw-2.md), [page](https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw-2)
- pypi · `ckg-nvidia-nemoclaw`: 34/100 (this document), [markdown](https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw.md), [page](https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw)

## Channel facts

- Registry: `pypi`
- Package: `ckg-nvidia-nemoclaw`
- Version: `0.10.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-08-03.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 30 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.

**Unverified: 4 categories.** Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### Claude

```bash
claude mcp add yarmoluk-ckg-nvidia-nemoclaw -- uvx ckg-nvidia-nemoclaw
```

### Codex

```bash
codex mcp add yarmoluk-ckg-nvidia-nemoclaw -- uvx ckg-nvidia-nemoclaw
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yarmoluk-ckg-nvidia-nemoclaw": {
      "type": "local",
      "command": [
        "uvx",
        "ckg-nvidia-nemoclaw"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yarmoluk-ckg-nvidia-nemoclaw --command uvx --arg ckg-nvidia-nemoclaw
```

### Hermes

```yaml
mcp_servers:
  yarmoluk-ckg-nvidia-nemoclaw:
    command: "uvx"
    args: ["ckg-nvidia-nemoclaw"]
```

### Other

```json
{
  "mcpServers": {
    "yarmoluk-ckg-nvidia-nemoclaw": {
      "command": "uvx",
      "args": [
        "ckg-nvidia-nemoclaw"
      ]
    }
  }
}
```

## 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-08-02 (score 34, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-01 (score 19, −4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 23, +5)

- [security regression] Provenance: unverified → fail
- [security regression] Malware scan: pass → unverified
- [security improvement] Known CVEs: unverified → pass
- [security improvement] Install scripts: unverified → pass
- [security] The scripts that run when this package is installed changed: build_backend
- [functional improvement] License: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → 0.99
- [functional] Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.
- [functional] Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.
- [functional] Licence: MIT

### 2026-07-30 (score 18, −6)

- [security regression] Source repository: pass → fail
- [functional regression] Security disclosure: fail → unverified
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Package version: 0.5.6 → 0.10.3

### 2026-07-27 (score 24)

First indexed and scored.

## MCP tools (7)

### `ask_nemoclaw` (~108 tokens)

Answer a question about NVIDIA NemoClaw by traversing the knowledge graph.

Covers: agent runtimes (OpenClaw/Hermes/Deep Agents), OpenShell platform,
inference routing, network policy, security layers, deployment paths,
progressive tool disclosure, managed MCP servers, snapshots, shields,
FOX Blueprint, Nemotron 3 Ultra ecosystem, and platform support.

Args:
    question: Your question about NemoClaw concepts or architecture.

Input parameters:

- `question` (string, required)

Output parameters:

- `result` (string)

### `query_ckg` (~78 tokens)

Return the typed subgraph around a NemoClaw concept.

Args:
    concept: Exact or partial concept label (e.g. 'OpenClaw', 'NetworkPolicy', 'L7Proxy').
    depth: Traversal hops (1–5, default 3).

Input parameters:

- `concept` (string, required)
- `depth` (integer)

Output parameters:

- `result` (string)

### `get_prerequisites` (~53 tokens)

Return the full upstream prerequisite chain for a NemoClaw concept.

Useful for understanding what a concept depends on end-to-end.

Args:
    concept: Exact or partial concept label.

Input parameters:

- `concept` (string, required)

Output parameters:

- `result` (string)

### `search_concepts` (~53 tokens)

Fuzzy search for NemoClaw concepts by name or keyword.

Args:
    query: Partial name or keyword (e.g. 'policy', 'inference', 'agent').

Input parameters:

- `query` (string, required)

Output parameters:

- `result` (string)

### `list_domains` (~17 tokens)

List available domains in this CKG server.

Output parameters:

- `result` (string)

### `verify_source` (~179 tokens)

Return the authoritative source URL and content hash for a NemoClaw concept node.

Every node in the CKG was declared from a specific source document. This tool
returns the source URL (where the node came from) and the SHA-256 hash of that
document's bytes at extraction time. A hash mismatch on re-fetch means either
the source has changed (stale edge — re-extract) or the graph was patched without
re-fetching (silent edit — investigate).

Audit chain:
    edge answer → graph commit → source_hash → source_url (fetch hint)

Verification:
    curl -s <source_url> | sha256sum
    # compare output to source_hash

Args:
    concept: Exact or partial concept label (e.g. 'CorporateCA', 'L7Proxy').

Input parameters:

- `concept` (string, required)

Output parameters:

- `result` (string)

### `route_query` (~196 tokens)

Route a NemoClaw question to the optimal model and reasoning approach via graph depth.

The CKG graph IS the router. NemoClaw's dependency chains (e.g. OpenShell → L7Proxy →
CorporateCA → mTLS) are deep and typed — hop depth is a deterministic complexity signal.
No heuristic: the graph decides which model and reasoning approach to use.

Routing table:
  hop_depth 1  → haiku  · direct          (single concept lookup)
  hop_depth 2  → sonnet · generic_cot     (moderate chain)
  hop_depth 3+ → opus   · sparql_cot      (deep chain, structured reasoning required)

Args:
    question: Concept name or natural language question about NemoClaw / OpenShell.

Returns:
    model_tier + reasoning_approach + why + context subgraph to inject before LLM call.

Input parameters:

- `question` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw#diagnostics

## Score history

- 2026-08-03: 34
- 2026-08-02: 34
- 2026-08-01: 19
- 2026-07-31: 23
- 2026-07-30: 18
- 2026-07-28: 24
- 2026-07-27: 24

## Links

- PyPI project: https://pypi.org/project/ckg-nvidia-nemoclaw/
- Socket report: https://socket.dev/pypi/package/ckg-nvidia-nemoclaw
- Changelog RSS feed: https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw/changelog.json
- HTML version of this page: https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw