NVIDIA NemoClaw CKG
io.github.Yarmoluk/ckg-nvidia-nemoclaw · v0.10.3
NVIDIA NemoClaw knowledge graph — 55 nodes, F1 0.576 (+269% vs RAG), 11x fewer tokens. MCP-native.
MCPremotelocal · pypino credentialsAI & LLM
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 8 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
A 86/100
What it does: 8 tools · 6 read, 0 write · AI & LLM
Test call list_domains: worked (1,036 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +1
- Read/write annotations: 0
- Safe test call: +20
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://ckg-nvidia-nemoclaw.onrender.com/mcpPackage
registry: pypi
identifier: ckg-nvidia-nemoclaw
version: 0.10.3
transport: stdioTools
8 tools listed at last check
ask_nemoclawAnswer 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 Blueprquery_ckgReturn 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).get_prerequisitesReturn 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.search_conceptsFuzzy search for NemoClaw concepts by name or keyword. Args: query: Partial name or keyword (e.g. 'policy', 'inference', 'agent').list_domainsList available domains in this CKG server.verify_sourceReturn 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-froute_queryRoute 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 whichquery_intersectAnswer 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 answer
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.Yarmoluk/ckg-nvidia-nemoclaw)