Skip to main content
Glama

Server Details

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

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
9.2% over 61 days
Last Tested
Transport
Streamable HTTP
URL
Repository
Yarmoluk/ckg-nvidia-ai
GitHub Stars
7

TDQS

A4/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have clearly distinct purposes: listing, searching, traversing, intersecting, routing, and verifying are all separated. The main potential confusion is between get_prerequisites and query_ckg, since both traverse prerequisite relationships, though the former is explicitly ordered and full-chain while the latter is general graph traversal.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: ask, get, list, query, route, search, verify. Even the query_* pair is consistent, and the one brand-tinged name (ask_nvidia) still follows the same verb_noun structure.

Tool Count5/5

Nine tools is a well-scoped set for an NVIDIA knowledge-graph server. There are enough tools to cover discovery, querying, specialized traversal, routing, and verification without feeling bloated or thin.

Completeness4/5

The surface covers domain listing, concept search, graph traversal, prerequisite chains, conjunctive queries, routing, NL question answering, and source verification—strong coverage for a knowledge-graph query server. A minor gap is the lack of a direct get-concept-details tool, though query_ckg and ask_nvidia partially compensate.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Addedquery_intersect
  2. 2 tool updates
    • Changedget_prerequisites1 field changed
      • changedOutput schema / (root)
        Previous value: -{
        -  "properties": {
        -    "result": {
        -      "title": "Result",
        -      "type": "string"
        -    }
        -  },
        -  "required": [
        -    "result"
        -  ],
        -  "title": "get_prerequisitesOutput",
        -  "type": "object"
        -}New value: +null
    • Changedquery_ckg1 field changed
      • changedOutput schema / (root)
        Previous value: -{
        -  "properties": {
        -    "result": {
        -      "title": "Result",
        -      "type": "string"
        -    }
        -  },
        -  "required": [
        -    "result"
        -  ],
        -  "title": "query_ckgOutput",
        -  "type": "object"
        -}New value: +null
  3. 8 tool updates
    • First observedask_nvidia
    • First observedget_prerequisites
    • First observedlist_domains
    • First observedlist_ecosystem
    • First observedquery_ckg
    • First observedroute_query
    • First observedsearch_concepts
    • First observedverify_source

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.