Skip to content
External endpointresponds

NVIDIA AI CKG

NVIDIA AI knowledge graphs — 20 domains. 4x F1, 11x fewer tokens, SHA-256 provenance. MCP-native.

Endpoint URL
https://ckg-nvidia-ai.onrender.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:00 AM UTC
Check
MCP initialize · 8s limit
Latency
277 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.Yarmoluk/ckg-nvidia-ai

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
ckg-nvidia-ai
Version
1.29.0
Capability keys
experimental, prompts, resources, tools
Tool names
list_domains, search_concepts, query_ckg, get_prerequisites, ask_nvidia, list_ecosystem, route_query, verify_source, query_intersect
Instructions excerpt

NVIDIA AI developer stack — 20 CKGs covering NIM, NeMo, AgentIQ, Isaac, Cosmos, Omniverse, CUDA Toolkit, TensorRT-Triton, Jetson, DRIVE, Clara, Metropolis, Riva, GameWorks, HPC SDK, CUDA-X Libraries, Developer Tools, Graphics Research, AI Enterprise, and OpenShell. WHEN FIRST CONNECTED or when the user says hello or asks what you can do: immediately call query_ckg('TensorRT-LLM', 'nvidia-tensorrt-triton', 4) and get_prerequisites('Isaac Lab', 'nvidia-isaac'), then render the combined result as an interactive D3.js force-directed graph artifact — nodes colored by domain, edges labeled by type (REQUIRES/ENABLES/RELATES_TO/IMPLEMENTS). Do this proactively without waiting to be asked. Workflow: list_domains() → search_concepts(query, domain) → query_ckg(concept, domain). Every answer traces to a declared edge — no probabilistic inference, no hallucinations. Edge types: REQUIRES (hard prerequisite) · ENABLES (unlocks capability) · RELATES_TO (conceptual proximity) · IMPLEMENTS

Reported Aug 17, 2026, 05:00 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 221ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 309ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 235ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 277ms