Reliquary MCP
OfficialRelated Servers
Alternatives to Reliquary MCP
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables discovery of public AI models with pricing, documentation context, and OpenAI-compatible integration examples. Supports both read-only queries and paid async media generation tasks.-
- AlicenseNot gradedqualityCmaintenanceAutonomous Cloud GPU Spot Bursts (rent_gpu_burst_arbitrage): Scans wholesale spot orderbooks (RTX 3090, RTX 4090, A100, H100) and provisions on-demand 3-minute compute bursts ($0.0500 USDC) with an automated 180-second idle deadman destruction switch and warm-pool multi-agent reuse.MIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to check live GPU prices, get a cost quote, rent a per-minute GPU instance, upload code and data, run jobs in the background, tail logs, download results and destroy the instance to stop billing. Includes guardrail limits on spend, hours and idle time, safe file transfer, and access to an OpenAI-compatible model API for inference without renting a GPU.3,581 npm1MIT
- AlicenseNot gradedqualityDmaintenanceDiscovers LLM models in real time from cloud providers and local Ollama instances, returning compatibility profiles and live pricing so AI agents can route tasks to the cheapest viable model without breaking tool calls or context clipping.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to query real-time GPU rental prices across 26 platforms, including current lowest quotes, 30-day price history, market movers, platform reliability, and task/budget recommendations. Access is read-only and metered per call via x402 with USDC on Base, requiring no signup or API key.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access decentralized GPU compute over stdio/JSON-RPC, query network status and pricing, estimate job costs, and run verified distributed matrix multiplication, similarity search, and PCA/SVD.414 PyPIApache 2.0
TDQS
Scored across 18 tools
Most tools are clearly scoped by resource (run, catalog, health, monitoring, batch review/plan). The main ambiguity is the cluster of catalog and health/readiness endpoints, where generic reliquary_catalog and several *_catalog tools, plus reliquary_health vs reliquary_monitoring_health, require careful description reading.
All 18 tools use the same reliquary_ prefix and lower snake_case naming, with no camelCase or mixed verb styles. The set is noun/phrase based rather than verb_noun, but it is internally consistent throughout.
18 tools is on the heavy side for a mostly read-only discovery and monitoring server. Several catalog and monitoring endpoints could potentially be consolidated, though most serve distinct subdomains.
The surface covers connection, catalogs, inventory, health/readiness, run listing and snapshots, monitoring, skills, and Affine batch review/planning. As a read-only evidence server it is broadly complete; quote/request and actual validation/execution actions are absent, but those appear explicitly out of scope.