io.github.jlucasmcrell/apify-scrapers
PYPI · APIFY-DATA-SCRAPERS · SCANNED SEP 20
40 Apify public-data tools for leads, news, SEO, jobs, SEC, procurement, and registries.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 1 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add jlucasmcrell-apify-scrapers -- uvx apify-data-scrapers
{
"mcpServers": {
"jlucasmcrell-apify-scrapers": {
"command": "uvx",
"args": [
"apify-data-scrapers"
]
}
}
} {
"servers": {
"jlucasmcrell-apify-scrapers": {
"command": "uvx",
"args": [
"apify-data-scrapers"
]
}
}
} codex mcp add jlucasmcrell-apify-scrapers -- uvx apify-data-scrapers
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jlucasmcrell-apify-scrapers": {
"type": "local",
"command": [
"uvx",
"apify-data-scrapers"
],
"enabled": true
}
}
} openclaw mcp add jlucasmcrell-apify-scrapers --command uvx --arg apify-data-scrapers
mcp_servers:
jlucasmcrell-apify-scrapers:
command: "uvx"
args: ["apify-data-scrapers"] {
"McpServers": {
"jlucasmcrell-apify-scrapers": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"apify-data-scrapers"
]
}
}
} assistant mcp add jlucasmcrell-apify-scrapers -t stdio -c uvx -a apify-data-scrapers
{
"mcpServers": {
"jlucasmcrell-apify-scrapers": {
"command": "uvx",
"args": [
"apify-data-scrapers"
]
}
}
} 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.
- 20 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 13423 → 15117 ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Package version: 1.2.0 → 1.4.0 functional
- Package version: 1.2.0 → 1.3.1 functional
- Package version: 1.2.0 → 1.3.0 functional
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 +4
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- MCP protocol: fail → pass ▲ functional
- Dependency health: 0.98 → pass functional
- Package version: 1.0.13 → 1.2.0 functional
- Package version: 1.0.13 → 1.1.2 functional
- 14 Sept 26 0
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Schema quality: 10078 → 12793 ▼ functional
- Schema quality: 10078 → 11864 ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 1.0.11 → 1.0.13 functional
- Package version: 1.0.11 → 1.0.12 functional
- 13 Sept 26 +14
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- Package version: 1.0.6 → 1.0.11 functional
- Package version: 1.0.6 → 1.0.10 functional
- Package version: 1.0.6 → 1.0.9 functional
- Package version: 1.0.6 → 1.0.7 functional
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 20 Sept 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 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
wisconsin_business_search Wisconsin Business Entity Registry 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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_details | boolean | – | Add registered agent, office addresses, annual-report year, former name, and foreign-entity details. |
| max_results | integer | – | Maximum records returned and billed. |
| search_query | string | yes | Full or partial Wisconsin business name. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| results | array | yes | – |
| run | object | – | – |
| status | string | yes | – |
No examples provided.
youtube_video_search 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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Maximum number of unique video records to return. Defaults to 25. |
| search_query | string | yes | Keyword or phrase to search for on YouTube (e.g. 'small business marketing'). |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| results | array | yes | – |
| run | object | – | – |
| status | string | yes | – |
No examples provided.
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 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.