revenue-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| revenue_dashboardB | Get full revenue dashboard — all entries, totals, pipeline status. Honest numbers only. |
| add_revenue_entryC | Track a new revenue opportunity (bounty, grant, product sale, freelance gig) |
| update_revenue_statusB | Update status of a revenue entry (e.g. pending → submitted → paid) |
| scan_bountyA | Anti-scam scanner — checks if a GitHub repo's bounty is legitimate (0-5 score) |
| find_bountiesA | Search GitHub for real, paying bounty opportunities. Filters out known scams. |
| crypto_portfolioC | Get real-time crypto portfolio value from CoinGecko (no fake numbers) |
| check_prsB | Check status of all open PRs across repos — track which ones might earn money |
| agent_messageC | Send/receive messages between AI agents for coordination. Honest communication only. |
| agent_inboxC | Read pending messages for an agent |
| product_catalogB | List all products and their monetization status |
| weekly_reportB | Generate honest weekly revenue report — no inflated numbers, only verified data |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Revenue Dashboard | Current revenue status and pipeline |
| Known Scam Repos | List of verified scam bounty repositories |
TDQS
Scored across 11 tools
Most tools have distinct purposes, but there is some overlap between 'find_bounties' and 'scan_bounty' as both relate to bounty verification, which could cause confusion. Other tools like 'add_revenue_entry' and 'update_revenue_status' are clearly differentiated for tracking revenue lifecycle.
The naming is mixed with some tools using verb_noun patterns like 'add_revenue_entry' and 'update_revenue_status', while others use noun-based names like 'agent_inbox' and 'crypto_portfolio'. This inconsistency reduces predictability but remains readable overall.
With 11 tools, the count is well-scoped for a revenue management server, covering areas like tracking, messaging, bounty handling, and reporting. Each tool appears to serve a specific function without being excessive.
The toolset provides good coverage for revenue tracking, including entry management, status updates, reporting, and bounty verification. Minor gaps might exist, such as lack of tools for deleting revenue entries or handling non-bounty income sources, but core workflows are well-supported.