nvidia-MCP
Related Servers
Alternatives to nvidia-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.8MIT
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server to inspect allowlisted Docker containers, systemd services, JSONL logs, and HTTP health endpoints without arbitrary shell access.MIT
- AlicenseNot gradedqualityCmaintenanceIt enables MCP-compatible AI clients to run local device, filesystem, shell, PowerShell, Git, browser, HTTP, clipboard and application actions on a Windows PC and a paired Android phone, with session-based device routing. Sensitive operations are gated behind configurable one-use approvals and recorded in a local SQLite audit.MIT
- AlicenseBqualityBmaintenanceLocal MCP server for observing and controlling an authorized Android device over USB using ADB and scrcpy, providing screen capture, UI automation, app inspection, logcat, and evidence recording.2941 npm3MIT
- AlicenseNot gradedqualityDmaintenanceA locally-run, read-only MCP server that lets an LLM client diagnose a self-hosted *arr media stack by aggregating across Sonarr, Radarr, Prowlarr, qBittorrent, Tdarr, and Profilarr.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA safety-oriented Model Context Protocol (MCP) server for inspecting, controlling, diagnosing, and selectively administering a Home Assistant instance.MIT
TDQS
Scored across 25 tools
Most tools map cleanly to a distinct resource+action, and the settings family (kodi_settings vs kodi_addon_settings vs kodi_set_setting vs kodi_set_addon_setting) is carefully differentiated by object and read/write. A few pairs like kodi_backup_file/kodi_backups and kodi_patch_file/kodi_set_setting require close reading, but boundaries are largely clear.
All names use lowercase snake_case with consistent shield_/kodi_ namespace prefixes, and verbs are predictable (read, patch, restore, set, preview, apply). Some entries are noun-only (kodi_status, kodi_addons, kodi_logs) rather than verb_noun, a minor deviation but still readable and grouped.
25 tools is heavy for what is essentially a Shield/Kodi inspection-and-safe-edit server, and the surface sits right at the borderline where maintenance and selection cost grow. The extensive safety-related variants (backup/patch/restore, manager layout trio) are arguably each justified, but a leaner surface would reduce cognitive load.
The surface covers device lifecycle and diagnostics, logs, file read/backup/patch/restore round-trips, settings and add-on settings, and optional Manager layout staging/apply/rebuild, giving strong lifecycle coverage. Only minor gaps remain, such as no dedicated file-delete or broader addon-management operations, which agents can work around.