Private workspace scope
Every OAuth grant or personal token is bound to one VerifiedMRR user and workspace. The agent can only read data that account can access.
The VerifiedMRR MCP server gives compatible AI clients a read-only view of your normalized revenue: portfolio totals, project performance, trends, recent events, and sync health. Choose your client below and connect at https://verifiedmrr.com/mcp.
Every OAuth grant or personal token is bound to one VerifiedMRR user and workspace. The agent can only read data that account can access.
The tools query VerifiedMRR's normalized revenue model, so an agent can compare connected projects without learning a different schema for every payment provider.
There are no refund, payout, subscription, customer, or credential-management actions. Every exposed MCP tool is annotated read-only.
OAuth is the best default for interactive clients. Add the endpoint, sign in to VerifiedMRR when your client opens the browser, approve the revenue:read scope, and return to the agent.
For headless agents and CI, open VerifiedMRR Settings → Agent access and create a personal MCP token. The full token is shown once. Store it in a secret manager and send it as an Authorization: Bearer header.
Agents can retrieve a workspace overview, list projects, inspect one project's revenue, request a daily or monthly time series, review recent normalized revenue events, and check provider sync status.
Useful prompts include: Compare every project by net revenue this month; explain the change from last month; flag stale syncs before writing a report; or draft a board update with the source period and currency stated explicitly.
Use the dedicated guides for ChatGPT, Claude and Claude Code, Hermes Agent, OpenClaw, or Codex. Any MCP client that supports Streamable HTTP plus OAuth 2.1 or bearer-token headers can connect to the same endpoint.
Use https://verifiedmrr.com/mcp. It is a remote Streamable HTTP MCP endpoint and supports OAuth 2.1 or a VerifiedMRR personal MCP token.
No. The MCP server is read-only and exposes no money-moving, customer, subscription, payout, or credential-management tools.
No. The MCP tools return workspace, project, aggregate revenue, normalized event, currency, and sync metadata—not customer profiles or card data.
The MCP layer reads revenue already imported into your VerifiedMRR workspace. It is provider-neutral, so connected providers use the same agent-facing tools and response shape.
Open Settings → Agent access to approve OAuth clients, create a headless token, and manage every connection.