SaaS & AI Pricing API MCP Server ★ New (July 14)¶
Free REST API and MCP server providing verified pricing data for 490+ SaaS, AI, and LLM tools. OpenAPI 3.1 format, no API key required. Gives AI agents structured access to the pricing landscape — perfect for competitive research, tool stack evaluation, and market intelligence.
Source: mcp.so (exact repo TBD — GitHub search API rate-limited) Submitted: July 14, 2026
Key Features¶
- 490+ tools covered: SaaS platforms, AI APIs, LLM providers, developer tools
- Verified pricing: Real pricing data, not scraped estimates
- OpenAPI 3.1 format: Standard, machine-readable API spec
- No API key: Free to use, no authentication required
- MCP-native: Connect directly to Claude, Cursor, ChatGPT, and any MCP client
- Structured queries: Ask "compare CRM pricing" or "cheapest LLM API for 1M tokens" and get structured, comparable results
Business Relevance¶
Every operator faces the same question: "Which tools should we use and what will they cost?" This MCP server turns that question into a query your AI agent can answer. Use cases: - Tool stack evaluation: Compare pricing across CRM, analytics, marketing, and DevOps tools - Vendor research: Research alternatives before committing to annual contracts - Cost optimization: Find cheaper alternatives to current tools - Market intelligence: Track pricing trends across the SaaS and AI landscape - Budget planning: Model tool costs for new projects or teams
Essential for operators in procurement, finance, engineering leadership, and anyone evaluating business software.
Integration with CorpusIQ¶
Pair with CorpusIQ's financial connectors (QuickBooks, Stripe) to compare actual spend against market pricing. Ask your AI agent: "We spend $X on these tools — are there cheaper alternatives?" and get data-driven answers spanning both your actual costs and market rates.
Limitations¶
- Exact GitHub repo TBD (GitHub search API rate-limited as of July 14)
- 490 tools is comprehensive but not exhaustive — niche tools may be missing
- Pricing changes frequently — data freshness depends on update frequency