Web Data API Plan Finder

Name: Web Data API Plan Finder
Author: scraping-api-plans

MCP serverMCP

Compare web scraping, crawling and SERP API pricing and limits against your workload and budget

by scraping-api-planshomepage ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"web-data-api-plan-finder","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability32/32 checks ok

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	836 ms	server web-data-plan-finder 0.1.0 · protocol 2025-06-18 · 5 tools
12 h ago	mcp initialize	ok	200	831 ms	server web-data-plan-finder 0.1.0 · protocol 2025-06-18 · 5 tools
18 h ago	mcp initialize	ok	200	864 ms	server web-data-plan-finder 0.1.0 · protocol 2025-06-18 · 5 tools
25 h ago	mcp initialize	ok	200	730 ms	server web-data-plan-finder 0.1.0 · protocol 2025-06-18 · 5 tools
32 h ago	mcp initialize	ok	200	798 ms	server web-data-plan-finder 0.1.0 · protocol 2025-06-18 · 5 tools
2 d ago	mcp initialize	ok	200	784 ms	server web-data-plan-finder 0.1.0 · protocol 2025-06-18 · 5 tools
2 d ago	mcp initialize	ok	200	838 ms	server web-data-plan-finder 0.1.0 · protocol 2025-06-18 · 5 tools
2 d ago	mcp initialize	ok	200	813 ms	server web-data-plan-finder 0.1.0 · protocol 2025-06-18 · 5 tools
2 d ago	mcp initialize	ok	200	819 ms	server web-data-plan-finder 0.1.0 · protocol 2025-06-18 · 5 tools
3 d ago	mcp initialize	ok	200	650 ms	server web-data-plan-finder 0.1.0 · protocol 2025-06-18 · 5 tools

Tools observed via MCP handshake

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 cond
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
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
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: th
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 m

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.scraping-api-plans/web-data-plan-finder

first seen 9 d ago · fetched 3 d agoopen ↗

Field history (6 recent events)

9 d ago · declared · summary → "Compare web scraping, crawling and SERP API pricing and limits against your workload and budget"
9 d ago · declared · description → "Compare web scraping, crawling and SERP API pricing and limits against your workload and budget"
9 d ago · declared · publisherName → "scraping-api-plans"
9 d ago · declared · homepageUrl → "https://plans.intoperson.com/guide"
9 d ago · declared · version → "0.1.0"
9 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from