mcp-nvidia-nim
Related Servers
Alternatives to mcp-nvidia-nim
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI agents to consume 50+ NVIDIA NIM models including LLMs, image generation, and vision through 10 MCP tools with rich metadata and advanced filtering.11358 npm1MIT
- FlicenseNot gradedqualityCmaintenanceProvides a live, audited catalog of AI models from NVIDIA NIM, OpenRouter, Nous Portal, and other providers, enabling search, retrieval, and usage examples via MCP tools and resources.-
- FlicenseAqualityDmaintenanceProvides tools for NVIDIA NIM and Visual GenAI APIs, enabling chat completions, model listing, and image generation via NVIDIA-hosted endpoints.4-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible applications to manage and use local or cloud LLM models through comprehensive SDK tools, including model management, text generation, chat with tool support, embeddings, and web search/fetch.894 npmAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access 140+ NVIDIA NIM models for chat, embeddings, reranking, vision, image generation, OCR, and content safety via stdio.87 npmMIT
- AlicenseAqualityDmaintenanceEnables LLM agents to control NVIDIA Run:AI infrastructure by dynamically searching and executing over 426 Run:AI APIs through MCP tools.49 npmMIT
TDQS
Scored across 11 tools
Half the tool set consists of explicit aliases (Portuguese names) that duplicate the English tools exactly, making it impossible to infer any selection difference. The six unique capabilities are distinct, but the aliases create multiple unclear boundaries and invite misselection.
All names use a consistent nim_ prefix and snake_case, which is readable. However, the set mixes English and Portuguese conventions, and the alias pairs introduce duplicate naming patterns rather than a single predictable scheme.
Eleven tools is a reasonable raw count, but five are redundant aliases, leaving only six unique capabilities. The aliases inflate the surface without adding functionality, making the count feel heavier than necessary.
The unique tools cover the core NIM lifecycle: status/quota inspection, general query, deep reasoning, code review, vision analysis, and document extraction. Minor gaps exist (e.g., no explicit model listing beyond status), but agents can work around them.