Koskamo

NVIDIA AI CKG MCP

An MCP server providing access to NVIDIA AI Knowledge Graphs across 21 domains, offering structured retrieval with SHA-256 provenance and reduced token usage compared to standard RAG. It supports integration with Claude Desktop, Cursor, Windsurf, and Python LangChain environments.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

NVIDIA AI CKG MCP logo, by Graphify.mdCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by Graphify.md
You need:10 calls/hour, no key required
MCP endpoint (Streamable HTTP)
https://ckg-nvidia-ai.onrender.com/mcp
Vendor documentation

What its tools do

9 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

9 of 9 have a description · 0 of 9 declare behavior hints · 0 of 7 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Integrate knowledge graph retrieval into Claude Desktop via MCP configuration
  • Connect Cursor or Windsurf to NVIDIA AI knowledge domains
  • Use Python LangChain CKGRetriever for domain-specific queries

Source and maintenance

Community listingRegistry 0.16.4
Maintenance checked

Protocol and capabilities

Server
ckg-nvidia-ai 1.30.0
MCP protocol negotiated in check
2025-11-25
Tools
9 advertised
Resources
1 advertised
Resource templates
1 advertised
Prompts
3 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  },
  "experimental": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

NVIDIA AI developer stack — 21 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, OpenShell, and Auto-Ontology. 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 (concrete instantiation).

Tools

9 advertised

list_domains
Advertised by the server during the last successful anonymous check.

List all 21 NVIDIA AI domains available in this knowledge graph.

list_domains input schema
{
  "type": "object",
  "title": "list_domainsArguments",
  "properties": {}
}
list_domains output schema
{
  "type": "object",
  "title": "list_domainsOutput",
  "required": [
    "result"
  ],
  "properties": {
    "result": {
      "type": "string",
      "title": "Result"
    }
  }
}
search_concepts
Advertised by the server during the last successful anonymous check.

Find concepts in a NVIDIA AI domain by keyword. Args: query: Search term — e.g. 'inference', 'sandbox', 'quantization', 'guardrails'. domain: Domain name from list_domains() — e.g. 'nvidia-nim', 'nvidia-openshell'.

search_concepts input schema
{
  "type": "object",
  "title": "search_conceptsArguments",
  "required": [
    "query",
    "domain"
  ],
  "properties": {
    "query": {
      "type": "string",
      "title": "Query"
    },
    "domain": {
      "type": "string",
      "title": "Domain"
    }
  }
}
search_concepts output schema
{
  "type": "object",
  "title": "search_conceptsOutput",
  "required": [
    "result"
  ],
  "properties": {
    "result": {
      "type": "string",
      "title": "Result"
    }
  }
}
query_ckg
Advertised by the server during the last successful anonymous check.

Traverse the NVIDIA knowledge graph from a concept — prerequisites and dependents. Args: concept: Concept name (partial match supported) — e.g. 'TensorRT', 'NIM', 'Isaac Lab'. domain: Domain name from list_domains() — e.g. 'nvidia-tensorrt-triton', 'nvidia-isaac'. depth: Traversal depth 1–5 (default 3).

query_ckg input schema
{
  "type": "object",
  "title": "query_ckgArguments",
  "required": [
    "concept",
    "domain"
  ],
  "properties": {
    "depth": {
      "type": "integer",
      "title": "Depth",
      "default": 3
    },
    "domain": {
      "type": "string",
      "title": "Domain"
    },
    "concept": {
      "type": "string",
      "title": "Concept"
    }
  }
}
get_prerequisites
Advertised by the server during the last successful anonymous check.

Return the full ordered prerequisite chain for a concept — everything to learn first. Args: concept: Target concept — e.g. 'Speculative Decoding', 'Isaac Lab', 'NeMo Guardrails'. domain: Domain name from list_domains().

get_prerequisites input schema
{
  "type": "object",
  "title": "get_prerequisitesArguments",
  "required": [
    "concept",
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "title": "Domain"
    },
    "concept": {
      "type": "string",
      "title": "Concept"
    }
  }
}
ask_nvidia
Advertised by the server during the last successful anonymous check.

Ask a natural-language question answered by Qwen grounded on the NVIDIA CKG. Requires Ollama running locally with a Qwen model pulled: ollama pull qwen2.5:14b Override model: NVIDIA_CKG_MODEL env var (default: qwen2.5:14b) Override host: NVIDIA_CKG_OLLAMA env var (default: http://localhost:11434) Args: question: Natural-language question about the NVIDIA AI stack. domain: Domain from list_domains() — auto-detected from question if omitted.

ask_nvidia input schema
{
  "type": "object",
  "title": "ask_nvidiaArguments",
  "required": [
    "question"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "title": "Domain",
      "default": ""
    },
    "question": {
      "type": "string",
      "title": "Question"
    }
  }
}
ask_nvidia output schema
{
  "type": "object",
  "title": "ask_nvidiaOutput",
  "required": [
    "result"
  ],
  "properties": {
    "result": {
      "type": "string",
      "title": "Result"
    }
  }
}
list_ecosystem
Advertised by the server during the last successful anonymous check.

Discover other CKG packages for adjacent domains — finance, healthcare, legal, and more.

list_ecosystem input schema
{
  "type": "object",
  "title": "list_ecosystemArguments",
  "properties": {}
}
list_ecosystem output schema
{
  "type": "object",
  "title": "list_ecosystemOutput",
  "required": [
    "result"
  ],
  "properties": {
    "result": {
      "type": "string",
      "title": "Result"
    }
  }
}
route_query
Advertised by the server during the last successful anonymous check.

Route an NVIDIA AI question to the optimal model and reasoning approach via graph depth. The CKG graph IS the router — hop depth is a deterministic complexity metric. Deeper NVIDIA prerequisite chains (CUDA → TensorRT → TensorRT-LLM → NIM) require more capable models. No heuristic: the graph decides. Routing table: hop_depth 1 → haiku · direct (simple lookup) hop_depth 2 → sonnet · generic_cot (moderate chain) hop_depth 3+ → opus · sparql_cot (deep dependency, structured reasoning) Args: question: Concept name or natural language question about NVIDIA AI. domain: Domain from list_domains() — e.g. "nvidia-tensorrt-triton", "nvidia-nim". Returns: model_tier + reasoning_approach + why + context subgraph to inject before LLM call.

route_query input schema
{
  "type": "object",
  "title": "route_queryArguments",
  "required": [
    "question"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "title": "Domain",
      "default": ""
    },
    "question": {
      "type": "string",
      "title": "Question"
    }
  }
}
route_query output schema
{
  "type": "object",
  "title": "route_queryOutput",
  "required": [
    "result"
  ],
  "properties": {
    "result": {
      "type": "string",
      "title": "Result"
    }
  }
}
verify_source
Advertised by the server during the last successful anonymous check.

Return the source URL and SHA-256 content hash for any NVIDIA AI concept node. Audit chain: edge answer → graph commit → source_content_hash → source_url (fetch hint). Verification: curl -s <source_url> | sha256sum # compare to source_hash Args: concept: Concept label (partial match supported). domain: Domain from list_domains() — e.g. 'nvidia-nim', 'nvidia-tensorrt-triton'.

verify_source input schema
{
  "type": "object",
  "title": "verify_sourceArguments",
  "required": [
    "concept",
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "title": "Domain"
    },
    "concept": {
      "type": "string",
      "title": "Concept"
    }
  }
}
verify_source output schema
{
  "type": "object",
  "title": "verify_sourceOutput",
  "required": [
    "result"
  ],
  "properties": {
    "result": {
      "type": "string",
      "title": "Result"
    }
  }
}
query_intersect
Advertised by the server during the last successful anonymous check.

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. domain: Domain name from list_domains(). 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.

query_intersect input schema
{
  "type": "object",
  "title": "query_intersectArguments",
  "required": [
    "branches",
    "domain"
  ],
  "properties": {
    "mode": {
      "type": "string",
      "title": "Mode",
      "default": "AND"
    },
    "depth": {
      "type": "integer",
      "title": "Depth",
      "default": 2
    },
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 40
    },
    "domain": {
      "type": "string",
      "title": "Domain"
    },
    "branches": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "title": "Branches"
    },
    "direction": {
      "type": "string",
      "title": "Direction",
      "default": "both"
    }
  }
}

Prompts

3 advertised

explore_nvidia_stack

Advertised by the server during the last successful anonymous check.

Build an interactive graph of the NVIDIA AI inference and robotics stack

No arguments advertised.

map_deployment_chain

Advertised by the server during the last successful anonymous check.

Map the full dependency chain for a production NVIDIA AI deployment

No arguments advertised.

find_what_i_need

Advertised by the server during the last successful anonymous check.

Tell me what I need to get started with a specific NVIDIA technology

No arguments advertised.

Resources

1 advertised

resource_domains

Advertised by the server during the last successful anonymous check.

All 21 NVIDIA AI domains — browsable index

resource_domains URI
ckg://domains

MIME type: text/plain

resource_domain

Advertised by the server during the last successful anonymous check.

Full CKG for a single NVIDIA AI domain — nodes, edges, metadata

resource_domain URI template
ckg://nvidia/{domain}

MIME type: text/plain

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-06: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
895 ms
95th percentile latency
895 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 895 ms · metadata changed · 9 tool(s), 1 resource(s), 1 resource template(s), 3 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http nvidia-ai-ckg-mcp https://ckg-nvidia-ai.onrender.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add nvidia-ai-ckg-mcp --url https://ckg-nvidia-ai.onrender.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable nvidia-ai-ckg-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "nvidia-ai-ckg-mcp": {
      "url": "https://ckg-nvidia-ai.onrender.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "nvidia-ai-ckg-mcp": {
      "type": "streamableHttp",
      "url": "https://ckg-nvidia-ai.onrender.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start nvidia-ai-ckg-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "nvidia-ai-ckg-mcp": {
      "type": "http",
      "url": "https://ckg-nvidia-ai.onrender.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http nvidia-ai-ckg-mcp https://ckg-nvidia-ai.onrender.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://ckg-nvidia-ai.onrender.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "nvidia-ai-ckg-mcp": {
      "serverUrl": "https://ckg-nvidia-ai.onrender.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like NVIDIA AI CKG MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.