Freshness before conclusions
The agent can check provider sync state before treating missing or delayed imports as a revenue change.
Add normalized revenue context to Hermes reasoning through OAuth or a revocable token, with no refunds, customers, or credentials exposed.
The agent can check provider sync state before treating missing or delayed imports as a revenue change.
It can compare explicit UTC ranges and report gross, fees, net, refunds, disputes, and transaction changes without mixing currencies.
It can group revenue by project, provider, product, offer, source label, or event type, then inspect only the time series that matters.
Hermes Agent 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.
Include a currency-safe revenue pulse in a normal Hermes operating loop without uploading a new CSV each run.
Compare equal periods, rank project movement, and explain whether refunds, fees, or lower gross revenue caused the change.
Use parallel read-only calls for independent project checks while keeping every result bound to one authorized workspace.
Add the remote server to Hermes config, complete the OAuth login in a fresh terminal, and reload MCP tools before starting the first analysis.
Follow the complete Hermes Agent setup guide for OAuth, headless tokens, verification, and troubleshooting.
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 Hermes Agent. 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.No. Every VerifiedMRR MCP tool is read-only and there are no money-moving or customer-management operations.
No. The MCP returns normalized project, aggregate, event, currency, and sync metadata—not customer profiles, addresses, card data, or provider credentials.
No. MCP preserves source currencies. The web dashboard has a clearly labelled display-only Auto FX option, but agents must keep MCP currencies separate.
Connect one read-only endpoint, verify sync health, and replace recurring spreadsheet handoffs with live workspace-scoped analysis.