MRR Bench pricing MCP server
An MCP endpoint your AI assistant can call to look up what SaaS tools actually charge — 4,164 tools, 14,490 price tiers, each with the pricing-page text it came from.
What MCP is, in one line
MCP (Model Context Protocol) is how an AI assistant calls an outside tool instead of guessing. Once you add this server, you can ask “what does Jasper charge now, and did it change this year?” and the assistant fetches the numbers from here rather than inventing them.
Connect it
Claude Code, Cursor, or any client that supports remote HTTP servers:
{"mcpServers":{"mrrbench":{"type":"http","url":"https://mrrbench.com/mcp"}}}
Claude Desktop and other clients that only speak stdio can wrap the same endpoint:
npx mcp-remote https://mrrbench.com/mcp
No key, no signup — the endpoint is read-only and open. Discovery card: /mcp.json. Implementation: mrrbench-pricing-mcp.
What you can ask
- “What does Jasper cost per month right now, and what is in each tier?”
- “Which of these five tools raised prices in the last 90 days?”
- “What would this stack cost per month: Descript, Notion, Figma, Jasper?”
- “Find me SEO tools under $50 a month.”
The four tools
search_tools— find tools by name or category across the indexget_pricing— every tier for one tool, with the verbatim pricing-page evidence and the date it was checkedprice_changes— verified list-price moves with dates and percentagesstack_cost— monthly and yearly total for a set of tools
Where the numbers come from
Prices are read from public pricing pages and re-checked on a schedule; the snippet behind each price is returned with it, so an answer can point at the page it came from. The change log only carries list prices — discounts and per-unit metering are excluded, because “the price changed” and “they ran a promo” are different facts.
Try it without a client
curl -s https://mrrbench.com/mcp -H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"get_pricing","arguments":{"domain":"jasper.ai"}}}'