Freshness before conclusions
The agent can check provider sync state before treating missing or delayed imports as a revenue change.
Give Codex business context beside the code.
Use one MCP endpoint to inspect project revenue, explain changes, and verify sync health while planning product work or releases.
What Codex can analyze after one connection.
Exact period comparison
It can compare explicit UTC ranges and report gross, fees, net, refunds, disputes, and transaction changes without mixing currencies.
Explain the drivers
It can group revenue by project, provider, product, offer, source label, or event type, then inspect only the time series that matters.
A read-only revenue layer for Codex
Codex connects to https://verifiedmrr.com/mcp through MCP. VerifiedMRR normalizes revenue that is already imported from payment and affiliate providers, so the agent sees one workspace-scoped schema instead of receiving provider credentials.
The connection has no refund, payout, customer, subscription, import-trigger, or credential-management tools. It is designed for analysis, reporting, and monitoring rather than payment operations.
Useful workflows
Check whether a product's revenue trend supports prioritizing a proposed engineering investment.
Review launch impact with exact pre/post date ranges and a project or product breakdown alongside the relevant code changes.
Generate a source-backed operating note without giving the coding agent access to refunds, customers, subscriptions, or provider secrets.
Set it up in Codex
Add the Streamable HTTP endpoint in Codex settings or config.toml, authenticate with OAuth, or point bearer_token_env_var at a protected environment secret.
Follow the complete Codex setup guide for OAuth, headless tokens, verification, and troubleshooting.
Copy this first analysis prompt
Paste this after the connection is authenticated. It verifies freshness and tool access before asking for an explanation.
Use the connected VerifiedMRR MCP server in Codex. Call get_sync_status first, then list_projects. Explain what revenue data is available, identify stale or degraded sources, compare this month with the previous month, and show the largest project or product changes. Keep currencies separate and state every date range.Keep exploring
Finish your Codex revenue setup.
FAQ
Before you connect a provider.
Can Codex change payments through VerifiedMRR?
No. Every VerifiedMRR MCP tool is read-only and there are no money-moving or customer-management operations.
Does the agent receive customer or card data?
No. The MCP returns normalized project, aggregate, event, currency, and sync metadata—not customer profiles, addresses, card data, or provider credentials.
Does MCP combine currencies automatically?
No. MCP preserves source currencies. The web dashboard has a clearly labelled display-only Auto FX option, but agents must keep MCP currencies separate.
Give Codex grounded revenue context.
Connect one read-only endpoint, verify sync health, and replace recurring spreadsheet handoffs with live workspace-scoped analysis.