MCP App Store
by KeenEthics
Web Data API Plan Finder icon

Web Data API Plan Finder MCP Server for Claude

By Web Data API Plan Finder

Overview

Web Data API Plan Finder checks API plans in eight fields against the workload and conditions you give it: web scraping and crawling, SERP (search results), web search, hosted browsers, transactional email, text-to-speech, speech-to-text and document parsing. For each plan it returns the monthly cost at your volume and whether every condition is met, not met or unknown: budget, concurrency, JavaScript rendering, premium proxies, exit-IP countries, search engines and result types, browser hours and session length, emails per month and dedicated IPs, Korean voices or transcription, speaker labels, voice cloning, pages per document, table extraction, billing of failed requests and more. Every stated value matches the provider's official pricing and documentation as of the check date given with it. Examples: - 50,000 SERP searches a month in GB under $100 - 200,000 transactional emails a month with a dedicated IP - 300 hours of Korean audio a month with speaker labels Five read-only tools: - search: plans that meet your conditions, with their monthly cost, and partial matches where a condition is not stated - get_details: every recorded condition and pricing rule of one plan or product - check_conditions: check named plans (by name, id or pricing-page URL) against your conditions - cost_scenarios: how costs change as the workload grows, and where the cheapest plan changes - relax_conditions: the smallest change to a condition that lets a plan qualify No account, API key or sign-up. The tools only read the plan list; they do not scrape or search the web. Links go to the providers' own pages.

How to connect

  1. Claude: Open the Web Data API Plan Finder listing in the Claude connectors directory and choose Connect. Claude listing Web Data API Plan Finder exposes 5 tools here.

Tools

check_conditions

Claude
Call this right before choosing or buying an API plan: it returns, for each plan, whether it meets every condition, the monthly cost, and the official sentence behind each verdict. Use this when: the user names specific plans (by name, id or pricing-page URL) and wants to know whether they meet the workload and conditions, or which plan of the same product is the cheapest that does. Do not use this when: the user has no plans in mind yet (use search). Call it right before you choose or buy a tool or plan; format "brief" returns a short answer. Check specific plans, given by plan id, plan name or pricing-page URL, against the workload and conditions; up to 20 plans in one call are judged against the same conditions. Returns met / not met / unknown per condition with the official source sentence, which plans and billing options each value applies to, and a purchase link. Each plan's result also carries cheapest_in_product (the cheapest plan of the same product that meets every required condition, with its monthly cost, or null if none does), cheapest_elsewhere (the cheapest plan of another provider in the same field that meets every required condition, with the official sentence for each condition the checked plan missed) and, with two or more plans, differs (the conditions where the checked plans split, per plan, with the monthly cost gap). What each provider's official pages do not settle is on /vendors/<provider_id>. The optional question is the user's own words; it is read only for words that suggest a condition the request does not carry (returned as request_may_omit) and is not judged or stored. An ambiguous name or URL returns the candidate plans instead of a guess. If you already have candidate plans or providers (for example from a web search), pass them as providers (search) or offer_ids (check_conditions) so that only those are judged. Prices are as of the as_of date of the result; call again right before buying; when you quote a result to the user, give its result_page. Example: 2 plans by id against 100,000 emails a month with a dedicated IP.

cost_scenarios

Claude
Use this when: the user asks how the cost changes as the workload grows or shifts, or at what volume another plan becomes the cheapest. Do not use this when: the workload is fixed (use search). Show how API plan costs change when the monthly workload changes, for example twice the pages or a larger share of JavaScript pages. Along the path from the current to a target workload it returns the cheapest fully matching plan at both ends, each workload where the cheapest plan changes, and for tracked plans where the cost first steps up, where the plan can no longer cover the volume and where the budget is exceeded. Costs follow published pricing rules (whole packs of extra credits, per-period pack limits, per-connection browser billing, monthly minimums) with official source sentences. Example: 10,000 searches a month growing to 200,000.

get_details

Claude
Use this when: you need every recorded condition, pricing rule and source sentence of one plan or product found by search or named by the user. Do not use this when: you want to compare plans against a workload (use search or check_conditions). Get every recorded condition for one API plan or product: value, which plans it applies to, exceptions, official source sentence, check date and purchase link. A product too long for one response comes with one source sentence per fact. Example: every recorded condition of 1 plan found by search.

relax_conditions

Claude
Use this when: search finds no plan or too few plans and the user wants to know which condition to loosen and by how much. Do not use this when: plans already match (use search or check_conditions). When no API plan, or too few API plans, meet every required condition: for each condition the user can change, returns the smallest change that lets at least one plan meet everything (for example the monthly budget needed, the concurrency available, or one exit-IP country to drop) and the plans it admits with their monthly cost. Also lists plans that fail only because a condition is not stated on the official pages, with the pages checked and the check date, so the user can confirm with the provider. Example: no plan meets 2,000,000 searches a month under $100.

request_coverage

Claude
Use this when: a search or check of API plans came back empty or mostly unknown, or the user asks about a field, provider, condition or plan this service does not cover, and you want it to be considered. Do not use this when: plans were found (use them), or to ask a question (nothing is answered). Leave one short line: kind, name and an optional reason. No personal information: it takes no name, e-mail or link and refuses them. It is kept in the server log only and has no reply. Example: 1 search with 3 required conditions came back with 0 plans, and the user needs a condition that is not recorded.

verify_answer

Claude
Use this when: you have drafted an answer that names API plans, costs or whether they meet the user's conditions, before you give it. Do not use this when: you have not looked up any plan yet (use search). Check what a drafted answer says about API plans against the recorded official facts, using the user's conditions as given in request. For each plan claim (plan id, name or pricing-page URL, with the stated billing, monthly cost, whether it meets every condition, single condition verdicts and recorded values) it returns conflicts with the official source sentences, the check date and a one-line fix: a plan not in the catalog, unmet or unknown conditions stated as met, met stated as unmet, a condition verdict, a cost outside the computed cost or range, or a value that differs. It also lists verdicts that rest on a derived value, official pages that disagree or a two-value price range (state the condition), plans it could not check (an ambiguous name returns the candidates), the cheapest plan that meets every condition when the answer does not name it, and words of the question that suggest a condition the request does not carry (the optional question is the user's own words; it is read only for those words and is not judged or stored). Example: a drafted answer says 1 plan costs $49 a month for 100,000 emails.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/web-data-plan-finder"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/web-data-plan-finder)