cashpilot-mcp
Related Servers
Alternatives to cashpilot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server exposing 72 tools across 26 homelab services, enabling LLMs to monitor and manage infrastructure, media, storage, and networking with a single endpoint.16MIT
- AlicenseAqualityDmaintenanceA generic MCP server that dynamically exposes any OpenAPI-documented REST API to LLMs by auto-discovering endpoints. It provides tools for exploring API capabilities and making authenticated requests directly through natural language interfaces.25 npmMIT

expenselm-mcp-serverofficial
FlicenseAqualityDmaintenanceMCP server for ExpenseLM, a GenAI powered expense management application. Enables AI agents to access expense data for recording, insights, and advice.1034 PyPI1-- AlicenseNot gradedqualityDmaintenanceMCP server that exposes Fund402 protocol tools to Casper testnet, allowing LLMs to execute real on-chain actions like wallet creation, token management, and borrowing via natural language.Apache 2.0
- AlicenseAqualityAmaintenanceMCP server that exposes any Pumperly instance to LLMs, enabling real-time fuel price queries, station search, route planning, and geocoding.547 npm3GPL 3.0
- AlicenseBqualityCmaintenanceAn MCP server that provides LLMs access to other LLMs444 npm81MIT
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action: service lifecycle, worker listing, catalog lookup, earnings reads, logs, health, and fleet state are clearly separated. The four earnings tools could look similar at a glance, but their descriptions explicitly cross-reference when to use each one.
All tool names follow a consistent snake_case verb_noun pattern: list_*, get_*, deploy_service, restart_service, stop_service, start_service, remove_service, trigger_collection. There are no mixed conventions or vague standalone verbs.
Eighteen tools is slightly above the ideal compact range, but the domain is broad: service lifecycle, workers, catalog, earnings analytics, logs, health, and alerts. Every tool appears to earn its place, though a few earnings-read variants could potentially be consolidated.
The surface covers the full deployed-service lifecycle (list, deploy, start, stop, restart, remove, logs), worker and fleet visibility, catalog/compose generation, earnings summaries and history, collection triggering, alerts, and health scores. No obvious operational dead ends remain for the stated CashPilot domain.