# NVIDIA NemoClaw CKG (remote · ckg-nvidia-nemoclaw.onrender.com)

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

- Trust score: 59/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `ckg-nvidia-nemoclaw.onrender.com`: 59/100 (this document), [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, [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

- Endpoint: `https://ckg-nvidia-nemoclaw.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.10.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1126 tokens (~140/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http yarmoluk-ckg-nvidia-nemoclaw https://ckg-nvidia-nemoclaw.onrender.com/mcp
```

### Codex

```toml
[mcp_servers.yarmoluk-ckg-nvidia-nemoclaw]
url = "https://ckg-nvidia-nemoclaw.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yarmoluk-ckg-nvidia-nemoclaw": {
      "type": "remote",
      "url": "https://ckg-nvidia-nemoclaw.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yarmoluk-ckg-nvidia-nemoclaw --url https://ckg-nvidia-nemoclaw.onrender.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  yarmoluk-ckg-nvidia-nemoclaw:
    url: "https://ckg-nvidia-nemoclaw.onrender.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "yarmoluk-ckg-nvidia-nemoclaw": {
      "type": "http",
      "url": "https://ckg-nvidia-nemoclaw.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-03 (score 59, −1)

- [functional regression] Schema quality: pass → fail
- [functional] New tool “query_intersect”

### 2026-08-02 (score 60, +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-07-31 (score 59, +3)

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

### 2026-07-30 (score 56, +42)

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

### 2026-07-29 (score 14)

First indexed and scored.

## MCP tools (8)

### `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)

### `query_intersect` (~367 tokens)

Answer a conjunctive query: concepts reachable from EVERY anchor at once (A AND B).

query_ckg walks outward from one concept. This intersects the reachable sets of two or
more, which is the shape of most real questions — "the component that satisfies A AND
applies to B". Neither anchor alone answers it; the answer lives in the overlap.

Every branch is an exact set of declared edges, so the intersection is exact. A concept
appears only if a declared path reaches it from each anchor. A relation missing from the
graph produces an empty result, never a guess.

Args:
    branches: Two or more branches. Either a bare anchor ("TensorRT-LLM"), which takes
        everything within `depth` hops, or an anchor plus an explicit relation path using
        '>' ("TensorRT-LLM > REQUIRES > ENABLES"), where each relation replaces the
        frontier. '*' matches any relation. Mix both forms freely.
    depth: Hops for bare-anchor branches, 1-5 (default 2). Ignored for explicit paths.
    direction: 'out' follows dependencies, 'in' follows them backwards, 'both' (default).
    mode: 'AND' (default) intersects branches; 'OR' unions them.
    limit: Max concepts listed, 1-200 (default 40). The true count is always shown.

Returns:
    Markdown with the query plan and its per-step set sizes, then the answer set with
    taxonomy tags. Reports which branch was empty when the intersection is empty.

Input parameters:

- `branches` (array, required)
- `depth` (integer)
- `direction` (string)
- `limit` (integer)
- `mode` (string)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw-2#diagnostics

## Score history

- 2026-08-03: 59
- 2026-08-02: 60
- 2026-08-01: 59
- 2026-07-31: 59
- 2026-07-30: 56
- 2026-07-29: 14

## Links

- Remote endpoint: https://ckg-nvidia-nemoclaw.onrender.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw-2/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw-2/changelog.json
- HTML version of this page: https://verifymcp.io/servers/yarmoluk-ckg-nvidia-nemoclaw/ckg-nvidia-nemoclaw-2