Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.jlucasmcrell/apify-scrapers

PYPI · APIFY-DATA-SCRAPERS

40 Apify public-data tools for leads, news, SEO, jobs, SEC, procurement, and registries.

0 this week 83 Trust /100

Last scanned (8 hours ago)

Scores higher than 85% of PyPI servers

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security94
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Declares code that runs automatically (setup.py, build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 15117 tokens (~359/item across 42 items; 40 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 40 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 42 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 1 Nov 26 +1
    • Stability: 0.97 → pass security
  • 31 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 25 Oct 26 +1
    • Stability: 0.97 → pass security
  • 24 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +1
    • Stability: 0.93 → pass security
  • 16 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 13 Oct 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 12 Oct 26 +1
    • Provenance: unverified → fail ▼ security
    • Security disclosure: fail → unverified ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/apify-data-scrapers@1.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 2 scripts
Hook Tier Command
setup_py unreviewed <setup.py, unreviewed>
build_hook unreviewed legacy backend root module

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 40 exposed · ~14,994 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
wisconsin_business_search ~284

Search the official Wisconsin DFI corporate registry by company name. Returns entity ID, legal name, entity type, registration date, and status, with optional agent, office, annual-report, former-name, and foreign-organization detail. Behavioral Transparency: - Execution: Network call executed synchronously in the cloud via Apify Actor 'captainhandsome/wi-business-entity-search'. - Side Effects: Creates a billed Actor run and dataset on your Apify account; queries the public Wisconsin DFI registry. - Authentication: Requires APIFY_TOKEN. - Latency & Limits: Typical runs take 10-30 seconds without details and longer with detail pages; timeout capped at 120 seconds. Usage Guidelines: - When to use: Use for Wisconsin entity verification, status checks, registered-agent research, former-name discovery, and business lead enrichment. - When NOT to use: Do not use for other states, contractor licences, or a legal good-standing determination. - Named alternatives: Use 'us_business_entity_search' for a multi-state lookup, 'us_contractor_license_search' for licensed contractors.

NameTypeReqDescription
include_detailsboolean–Add registered agent, office addresses, annual-report year, former name, and foreign-entity details.
max_resultsinteger–Maximum records returned and billed.
search_querystringyesFull or partial Wisconsin business name.
NameTypeReqDescription
errorobject––
resultsarrayyes–
runobject––
statusstringyes–

No examples provided.

youtube_video_search ~264

Search public YouTube videos by keyword, returning title, channel, canonical video URL, view count, duration, and publish date - no YouTube Data API quota required. Behavioral Transparency: - Execution: Network call executed synchronously in the cloud via Apify Actor 'captainhandsome/youtube-search-scraper'. - Side Effects: Reads public sources and creates a billed Actor run and dataset on your Apify account. - Authentication: Requires APIFY_TOKEN environment variable. - Latency & Limits: Typical run duration is 10-30 seconds; timeout capped at 120 seconds. Usage Guidelines: - When to use: Use for content research, competitor video monitoring, trend discovery, or building a list of videos on a topic. - When NOT to use: Do not use for retrieving a video's transcript/captions, channel analytics dashboards, or non-YouTube platforms. - Named alternatives: Use 'google_play_reviews_search' for app-store sentiment or 'linkedin_jobs_search' for job-market data; neither covers video content.

NameTypeReqDescription
max_resultsinteger–Maximum number of unique video records to return. Defaults to 25.
search_querystringyesKeyword or phrase to search for on YouTube (e.g. 'small business marketing').
NameTypeReqDescription
errorobject––
resultsarrayyes–
runobject––
statusstringyes–

No examples provided.

Install

How do I install the io.github.jlucasmcrell/apify-scrapers MCP server?

io.github.jlucasmcrell/apify-scrapers runs locally as a PyPI package, launched with uvx apify-data-scrapers. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · apify-data-scrapers

# add to Claude Code
claude mcp add jlucasmcrell-apify-scrapers -- uvx apify-data-scrapers
Common questions

What is the io.github.jlucasmcrell/apify-scrapers MCP server?

io.github.jlucasmcrell/apify-scrapers is an MCP server listed in the public MCP registry as io.github.jlucasmcrell/apify-scrapers. 40 Apify public-data tools for leads, news, SEO, jobs, SEC, procurement, and registries. This page covers its PyPI package (apify-data-scrapers).

Is the io.github.jlucasmcrell/apify-scrapers MCP server safe to use?

io.github.jlucasmcrell/apify-scrapers scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.jlucasmcrell/apify-scrapers MCP server expose?

io.github.jlucasmcrell/apify-scrapers exposes 40 tools: google_maps_search, glassdoor_jobs_search, sec_edgar_filings, usaspending_contracts, twitch_live_streams, and 35 more. Their descriptions and schemas cost roughly 14,994 tokens of context every time the server is loaded.

Is the io.github.jlucasmcrell/apify-scrapers MCP server still maintained?

io.github.jlucasmcrell/apify-scrapers is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.jlucasmcrell/apify-scrapers MCP server under?

io.github.jlucasmcrell/apify-scrapers declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.