Stars Cash Flow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STARS_CASH_FLOW_API_KEY | Yes | Your API key from @StarsCashFlowbot (Reseller). Required for all actions except listing services. | |
| STARS_CASH_FLOW_API_BASE | No | Base URL for the Stars Cash Flow API. | https://api-stars.ros.media/api/v2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_servicesA | List the Stars Cash Flow service catalog with live USD rates (per 1000), min/max quantity and whether each service needs a link. No API key required. Use this to discover service IDs and price an order before calling create_order. |
| get_balanceA | Get the remaining USD balance of the configured reseller API key. |
| create_orderA | Place a Stars Cash Flow order. THIS SPENDS the key's USD balance. Two-step by design: call without |
| order_statusA | Get the status of one or more orders. Pass a single |
| cancel_orderA | Cancel one or more orders. The unfulfilled remainder is refunded to the key's USD balance. Pass |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing services, checking balance, placing orders, canceling orders, and checking status. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_order, list_services, get_balance), making them predictable and easy to understand.
With 5 tools, the set is well-scoped for the service's purpose, covering all essential operations without unnecessary bloat. Each tool serves a clear role.
The tool set covers the full lifecycle: discovery (list_services), funding (get_balance), ordering (create_order), cancellation (cancel_order), and tracking (order_status). No obvious gaps for the intended domain.