MCP serverio.github.scraping-api-plans/web-data-plan-finder
Compare web scraping, crawling and SERP API pricing and limits against your workload and budget
Overview
Score?
UNRATED 0.000
of what a free look can see, on 1 looks
Looks
3
last 17 hr ago
Tools
5
changed 17 hr ago
More info
URL
plans.intoperson.com/mcp
streamable-http
Says it is
web-data-plan-finder 0.1.0
protocol 2025-06-18
In the record since
2 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.000 · highest on record 0.8561
Toolsfrom sha256:4973c3e437…200edc · +0 −0 17 hr ago
| Tool | Schema |
|---|---|
| check_conditions 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 |
input · output |
| cost_scenarios 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 |
input · output |
| get_details 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 co |
input · output |
| relax_conditions 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 |
input · output |
| search Use this when: the user wants to know which web data API plans (web scraping, crawling, SERP search result APIs) fit a monthly workload, budget or required conditions, or what one |
input · output |
Verify it yourself
npx teppi-check https://plans.intoperson.com/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M3XM3ZM3EDAS7671EYGV6G8X