mcpbeat

NVIDIA CUDA Docs MCP Server

by nvidia-ngc-nsight-copilot-api
answering

NVIDIA CUDA Docs is answering right now. Last checked 6 min ago.

Search NVIDIA CUDA documentation and code samples from AI coding agents.

Uptime history 57 hours of history
57 hours agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
1633 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add cuda-docs --transport http https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cuda-docs": {
      "url": "https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs"
    }
  }
}
~/.codex/config.toml
[mcp_servers.cuda-docs]
url = "https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs"
.cursor/mcp.json
{
  "mcpServers": {
    "cuda-docs": {
      "url": "https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "cuda-docs": {
      "url": "https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs streamable-http needs key 1895 ms 6 min ago

Alternatives to NVIDIA CUDA Docs

same job, measured the same way
Codealive MCP
by codealive-ai

Semantic code search and analysis from CodeAlive for AI assistants and agents.

local only
Code Context
by infino-ai

Local code search for AI coding agents: hybrid search and SQL aggregation over an in-repo index.

49 installs/wk local only
Docfork MCP
by smithery

@latest documentation and code examples to 9000+ libraries for LLMs and AI code editors in a singl…

answering
Docuwriter
by docuwriter

Generate, search, and manage codebase documentation on DocuWriter.ai. 72 tools incl. Autopilot.

answering
Docdex
by bekirdag

Fast per-repo documentation indexer and full-text search MCP server for codebases.

2 307 installs/wk local only
GitHits
by githits

Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.

696 installs/wk answering
Radzen Blazor MCP
by radzen-www

AI coding assistant for Radzen Blazor — docs, APIs, code samples, and templates for 100+ components.

answering
ivygrep
by bvolpato

Local code search and task context packs for coding agents

local only

NVIDIA CUDA Docs — questions

Answers built from our own checks of this server.

Why is there no tool list for NVIDIA CUDA Docs?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is NVIDIA CUDA Docs working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 1633 ms. The bar chart above shows every period we have measured.
How do I connect NVIDIA CUDA Docs?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does NVIDIA CUDA Docs need an API key?
Yes. Every time we knock, NVIDIA CUDA Docs answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is NVIDIA CUDA Docs?
It answers our handshake in 1633 ms on average, which is faster than 2% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.