A
licenseNot graded
qualityF
maintenanceEnables Claude Code to execute shell commands, Python code, and file transfers on a Google Colab T4 GPU via an MCP server, bridging the GPU gap for AI coding agents.
6
MIT
prime-intellect-mcp
by kvrancic
Related Servers
Alternatives to prime-intellect-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for renting real GPUs from the terminal. Enables browsing, renting, chatting, managing, and pooling GPU instances with per-second billing, designed for AI agents.46 npm1-
- AlicenseAqualityFmaintenanceA server that allows LLMs to run Claude Code with all permissions bypassed automatically, enabling code execution and file editing without permission interruptions.1372 npm1,315MIT
- AlicenseAqualityDmaintenanceThis MCP server enables remote control and management of Claude Code agents, allowing you to execute missions, configure agent personalities, and integrate with other MCP tools.715 npm1MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets any MCP-capable agent spawn and drive Claude Code sessions — effectively turning Claude Code into an orchestratable sub-agent fleet.59 npmMIT
- AlicenseNot gradedqualityAmaintenanceThis server enables users to operate Claude Code functionalities 24/7 directly within Telegram. It provides advanced features including voice interaction, session memory persistence, and real-time Agentic Mode monitoring.MIT
TDQS
A4.4/5.0
Scored across 9 tools
Disambiguation5/5
Each tool has a unique and clearly distinct purpose, from wallet balance and GPU availability listing to pod creation, quoting, and termination. There is no overlap that could cause an agent to select the wrong tool.
Naming Consistency5/5
Tool names follow a consistent pattern: utility functions use verb_noun (e.g., get_wallet_balance, list_availability) and pod operations all start with pod_ (e.g., pod_create, pod_terminate). The naming is predictable and easily understood.
Tool Count5/5
With 9 tools covering wallet, GPU types, availability, pod lifecycle (create, list, status, quote, terminate), and runaway monitoring, the count is well-scoped for the server's purpose. Each tool earns its place with no redundancy.
Completeness5/5
The tool surface covers the full lifecycle of GPU pod management: discovering availability, quoting, creating, monitoring status, listing, terminating, and checking for runaway pods. The inclusion of wallet balance and wait-for-SSH functionality addresses common operational needs.
Maintenance
ActivityInactive
ResponsivenessNo issues