Skip to main content
Glama
Sign In
revenue-mcp

revenue-mcp

by ElromEvedElElyon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Revenue Command Center MCP

Honest, transparent revenue intelligence for AI agents. No fake numbers, no inflated metrics, no scams.

Features

  • 11 Tools for revenue tracking, bounty scanning, crypto portfolio, agent coordination

  • Anti-Scam Scanner — scores GitHub bounty repos 0-5 with red/green flags

  • Agent Messaging — AI agents can coordinate via messages

  • Product Catalog — track all products and monetization status

  • Weekly Reports — honest numbers only, paid vs pending

Tools

Tool

Description

revenue_dashboard

Full revenue pipeline status

add_revenue_entry

Track a new opportunity

update_revenue_status

Update entry status

scan_bounty

Anti-scam repo scanner (0-5)

find_bounties

Search for legit bounties

crypto_portfolio

Real-time prices from CoinGecko

check_prs

All open PRs across repos

agent_message

Send inter-agent messages

agent_inbox

Read agent messages

product_catalog

All products & monetization

weekly_report

Honest weekly summary

Install

npm install github:ElromEvedElElyon/revenue-mcp

Usage with Claude Code

Add to your MCP config:

{
  "mcpServers": {
    "revenue-mcp": {
      "command": "node",
      "args": ["/home/administrador/revenue-mcp/dist/index.js"]
    }
  }
}

Philosophy

  • Only count PAID as revenue (not pending, not projected)

  • Scam detection before bounty work

  • Transparent tracking — every entry has a source and status

  • Agent coordination via honest messaging

Built by ElromEvedElElyon. Em nome do Senhor Jesus Cristo.

Available Tools

11 tools
add_revenue_entryC

Track a new revenue opportunity (bounty, grant, product sale, freelance gig)

Inputs: source (required), description (required), amount_usd (required), status, +3 more.

agent_inboxC

Read pending messages for an agent

Inputs: agent (required).

agent_messageC

Send/receive messages between AI agents for coordination. Honest communication only.

Inputs: from (required), to (required), type (required), content (required), +1 more.

check_prsB

Check status of all open PRs across repos — track which ones might earn money

Inputs: no named parameters.

crypto_portfolioC

Get real-time crypto portfolio value from CoinGecko (no fake numbers)

Inputs: coins.

find_bountiesA

Search GitHub for real, paying bounty opportunities. Filters out known scams.

Inputs: query, min_stars.

product_catalogB

List all products and their monetization status

Inputs: no named parameters.

revenue_dashboardB

Get full revenue dashboard — all entries, totals, pipeline status. Honest numbers only.

Inputs: no named parameters.

scan_bountyA

Anti-scam scanner — checks if a GitHub repo's bounty is legitimate (0-5 score)

Inputs: repo (required).

update_revenue_statusB

Update status of a revenue entry (e.g. pending → submitted → paid)

Inputs: id (required), status (required), notes.

weekly_reportB

Generate honest weekly revenue report — no inflated numbers, only verified data

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 11 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Resources

    Related MCP Connectors

    Appeared in Searches