scraper-finder
Registry code: 7ee65556e5e2b112
Scraper Finder answers 'how do I get data from website X?' for about 170 major websites: the official API route (public, limited, partner-only or none, with price and limits notes and the docs link) next to ranked Apify tools (score from one published formula: core-field coverage, price per 1,000 results, reliability, freshness). Start with which_tool(website). Use find_by_field when the user needs specific output fields (e.g. 'email', 'salary'). list_websites shows coverage and filters by official API status. Nothing here runs a scraper. Public data is not permission: point users to the…
- endpoint
- https://scraperfinder.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is scraper-finder live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is scraper-finder free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does scraper-finder have?
- 3 tools: find_by_field, which_tool, list_websites.
- Is scraper-finder safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_websites open 1h ago
The websites Scraper Finder maps, with their official API status and number of ranked tools. Filter by name, domain or category text, or by API status (public, limited, partner, none, retired).
{ "type": "object", "properties": { "limit": { "type": "integer", "default": 60, "maximum": 200, "minimum": 1 }, "query": { "type": "string", "maxLength": 80, "description": "Part of a name, domain or category, e.g. 'jobs'." }, "api_status": { "enum": [ "public", "limited", "partner", "none", "retired" ], "type": "string" }, "with_tools_only": { "type": "boolean", "default": false } }, "additionalProperties": false }arguments 31 linesfind_by_field unknown 1h ago
Catalogue tools whose published output schema includes the fields you need (e.g. ['email', 'phone'] or ['salary']), optionally for one website, cheapest first among equal matches.
{ "type": "object", "required": [ "fields" ], "properties": { "limit": { "type": "integer", "default": 10, "maximum": 25, "minimum": 1 }, "fields": { "type": "array", "items": { "type": "string" }, "maxItems": 10, "minItems": 1, "description": "Field names, e.g. ['email', 'rating']." }, "website": { "type": "string", "maxLength": 200, "description": "Optional website name or domain." } }, "additionalProperties": false }arguments 29 lineswhich_tool unknown 1h ago
How to get data from one website: its official API (status, name, price and limits notes, docs, check date) beside the ranked catalogue tools (score, price per 1,000 results, core-field coverage, distinctive fields, page and Store link), plus robots.txt and terms facts. Optionally rank by the output fields you need.
{ "type": "object", "required": [ "website" ], "properties": { "limit": { "type": "integer", "default": 5, "maximum": 20, "minimum": 1 }, "fields": { "type": "array", "items": { "type": "string" }, "maxItems": 10, "description": "Optional output fields you need, e.g. ['price', 'bedrooms']." }, "website": { "type": "string", "maxLength": 200, "description": "Website name, domain or URL, e.g. 'Zillow', 'indeed.com'." } }, "additionalProperties": false }arguments 28 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id7ee65556e5e2b112.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/7ee65556e5e2b112/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/7ee65556e5e2b112?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.