Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-geiserx-cashpilot-mcp": {
"args": [
"-y",
"cashpilot-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Everything is exposed over a single JSON-RPC endpoint (/mcp). LLMs / Agents can: initialize -> readResource -> listTools -> callTool ... and so on.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'cashpilot-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked cashpilot-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
A Model Context Protocol (MCP) server that provides AI assistants with direct access to the Spreedly payments API. Enables LLMs to manage gateways, process transactions, tokenize payment methods, and more, through structured, validated tool calls.
MCP server for InsightSentry financial data API - market data, options, screeners, and more
AI agents get on-chain identity, credentials, reputation, escrow, and persistent memory on XRPL.
MCP Security Weekly
Get CVE alerts and security updates for io.github.GeiserX/cashpilot-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A tiny bridge that exposes any CashPilot instance as an MCP server, enabling LLMs to monitor passive income earnings, manage services, and control fleet workers.
| Type | What for | MCP URI / Tool id |
|---|---|---|
| Resources | Browse earnings, services, fleet status, and health scores read-only | cashpilot://earnings/summarycashpilot://earnings/breakdowncashpilot://services/deployedcashpilot://services/catalogcashpilot://fleet/summarycashpilot://workerscashpilot://health/scorescashpilot://collector-alerts |
| Tools | Query earnings, manage services, and trigger collection | get_earnings_dailyget_earnings_historyget_service_logsrestart_servicestop_servicestart_servicedeploy_serviceremove_servicetrigger_collectionget_compose |
Everything is exposed over a single JSON-RPC endpoint (/mcp).
LLMs / Agents can: initialize -> readResource -> listTools -> callTool ... and so on.
services:
cashpilot-mcp:
image: drumsergio/cashpilot-mcp:latest
ports:
- "127.0.0.1:8081:8081"
environment:
- CASHPILOT_URL=http://cashpilot:8080
- CASHPILOT_API_KEY=<your-CASHPILOT_ADMIN_API_KEY>
Security note: The HTTP transport listens on
127.0.0.1:8081by default. If you need to expose it on a network, place it behind a reverse proxy with authentication.
npx cashpilot-mcp