Every revenue tool, without the guesswork.

Shared response and currency rules

Every tool is workspace-scoped, read-only, idempotent, and closed-world. Money responses include the lowercase ISO currency plus minor, decimal, and formatted values. MCP results preserve source currencies and never apply the dashboard's Auto FX conversion.

Dates use UTC. Date inputs use YYYY-MM-DD. Time-series, comparison, and breakdown ranges are limited to 366 inclusive days. Invalid tokens return HTTP 401; invalid tool inputs return a schema or bounded-range error.

get_sync_status

No inputs. Returns each connected account's project, provider, status, last successful sync, last redacted error, and the time checked. Call this before interpreting a decline or producing a scheduled report.

Call: get_sync_status({})
Returns: { accounts: [{ projectId, projectName, provider, status, lastSyncAt, lastErrorAt, lastErrorMessage }], checkedAt }

get_revenue_overview

Summarizes a portfolio period. period is today, week, month, quarter, year, or all. periodKey selects an exact historical period; currency optionally narrows the result.

get_revenue_overview({ "period": "month", "periodKey": "2026-07", "currency": "usd" })
Returns: { period, periodKey, currencies: [{ currency, gross, fees, net, refunds, disputes, transactionCount }], projectCounts, generatedAt }

list_projects

Lists active projects for a selected period with provider, normalized revenue, previous net, trend percentage, health signal, and last positive revenue date.

list_projects({ "period": "month" })
Returns: { period, periodKey, projects: [{ id, name, provider, revenue, previousNetMinor, trendPercent, health, lastPositiveRevenueAt }] }

get_project_revenue

Returns one authorized project's revenue for a period. Obtain projectId from list_projects. Unknown or cross-workspace IDs return Project not found in this workspace.

get_project_revenue({ "projectId": "prj_...", "period": "quarter", "periodKey": "2026-Q2" })
Returns: { project: { id, name, provider }, period, periodKey, currencies: [...] }

get_revenue_timeseries

Returns daily or monthly points over an inclusive range of at most 366 days. Filter by projectId and currency when needed.

get_revenue_timeseries({ "from": "2026-07-01", "to": "2026-07-31", "granularity": "day", "projectId": "prj_...", "currency": "usd" })
Returns: { from, to, granularity, projectId, points: [{ bucket, currency, gross, fees, net, refunds, disputes, transactionCount }] }

compare_revenue_periods

Compares two explicit ranges using the same project and currency filters. Percentage change is null when the comparison value is zero and the current value is non-zero.

compare_revenue_periods({ "from": "2026-07-01", "to": "2026-07-31", "compareFrom": "2026-06-01", "compareTo": "2026-06-30", "currency": "usd" })
Returns: { current, comparison, projectId, currencies: [{ currency, current, comparison, changePercent }] }

get_revenue_breakdown

Groups a range by project, provider, product, offer, source, or event_type. limit accepts 1 to 100 and defaults to 25. Unlabelled provider metadata is grouped explicitly instead of discarded.

get_revenue_breakdown({ "from": "2026-07-01", "to": "2026-07-31", "dimension": "product", "currency": "usd", "limit": 20 })
Returns: { from, to, dimension, projectId, groups: [{ key, currency, gross, fees, net, refunds, disputes, transactionCount }] }

list_recent_revenue_events

Returns up to 100 normalized events with project and amount metadata, but no customer, card, address, or provider credential data. Optional project and date filters keep investigations narrow.

list_recent_revenue_events({ "limit": 25, "projectId": "prj_...", "from": "2026-07-01", "to": "2026-07-31" })
Returns: { events: [{ id, projectId, projectName, provider, eventType, occurredAt, productName, offerName, sourceLabel, amount }], limit }

Recommended analysis sequence

Check freshness, discover project IDs, compare exact periods, inspect the largest breakdown groups, then request a time series or recent events only where the aggregate changed. This produces a traceable answer with fewer calls.

Use the connected VerifiedMRR MCP server. First call get_sync_status, then inspect the available tools and explain:
1. What revenue questions you can answer
2. Which projects and providers are available
3. What date ranges and currencies the data covers
4. What you cannot access or change
5. Five useful analyses you can run for me

Do not combine currencies. Clearly distinguish gross, fees, net, refunds, and disputes. Do not make performance claims when a source is stale or still importing.