io.github.Ken-Mutisya/scrapemint-lead-data
Scrapemint Lead Data
Is the Scrapemint Lead Data MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.
Company enrichment, email finding, tech stack, new store leads, press requests and bid notices
needs auth probed 2026-11-15 · unchanged since 2026-11-11 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Missing or invalid access token. Pass an Apify API token in the - Endpoint
- https://mcp.apify.com?tools=scrapemint/company-enrichment,scrapemint/company-email-finder,scrapemint/domain-authority-checker,scrapemint/website-tech-stack-detector,scrapemint/new-shopify-store-leads,scrapemint/journalist-request-finder,scrapemint/uk-companies-house-scraper,scrapemint/sam-gov-contract-opportunities (streamable-http)
- Host
- mcp.apify.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.apify.com?tools=scrapemint/company-enrichment,scrapemint/company-email-finder,scrapemint/domain-authority-checker,scrapemint/website-tech-stack-detector,scrapemint/new-shopify-store-leads,scrapemint/journalist-request-finder,scrapemint/uk-companies-house-scraper,scrapemint/sam-gov-contract-opportunities registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server console-backend.apify.com, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes full_api_access.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/Ken-Mutisya/scrapemint
- Website
- https://apify.com/scrapemint
- Registry
- active, updated 2026-11-09 · registry entry
Compare this server with others.
More servers
Other registry entries on mcp.apify.com, the ones next to this name; all of them.
- Career Site Job Feed io.github.HwangByeongSeon/career-site-job-feed · needs auth
- TX ESBD Procurement io.github.J0401/tx-esbd · needs auth
- Agent Verification Tools (Apify) io.github.JackPT79/agent-verification-tools · needs auth
- io.github.JdPG23/market-data-toolkit-mcp · needs auth
- Scrapemint Market Data io.github.Ken-Mutisya/scrapemint-market-data · not probed
- App Reviews Intelligence io.github.Kupilux/app-reviews-intelligence · needs auth
- Meta Ad Library, Google Ads Transparency & Video Ad Analyzer io.github.LMSlay/tubetext-ad-intelligence · needs auth
- China Data: Taobao, Bilibili, WeChat, Trending io.github.LMSlay/tubetext-china-data · needs auth
Servers that mention lead.
- Getlead ad.getle/leads · alive
- b/cited ai.bcited/bcited · alive
- Contractors Near Me ai.contractorsnearme/contractors-near-me · needs auth
- D50 AI — Sales, Marketing & Hiring Automation ai.d50/d50-platform · needs auth
- Fantopy ai.fantopy/fantopy · needs auth
- LinkDeal ai.linkdeal.www/mcp · needs auth
- Onsa ai.onsa/onsa · alive
- Pro Reach LinkedIn Outreach ai.proreach/outreach · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.