Apify
NPM · @PIPEWORX/MCP-APIFY · 2 COMPONENTS
Apify MCP — run web-scraping Actors and fetch their dataset results.
Available components
Last scanned (8 hours ago)
Scores higher than 72% of npm servers
Category Web Scraping
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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-apify). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 603 tokens (~201/item across 3 items; 3 tools + 0 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 79
First indexed and scored.
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 npm/@pipeworx/mcp-apify@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-apify |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-apify/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3587979028 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:8ed5731ffd28a38b5da054a721fb0fe5f93254edef0bc8f9280bc2b2ee70325e633dfc7a08a959147c83cb9b43728bc1d13b22a5e110042c87f6bfba2 |
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 →
apify_dataset_items ~184
Fetch items from an existing Apify dataset (e.g. the output of a prior Actor run). Example: apify_dataset_items({ datasetId: "abc123", limit: 50, _apiKey: "your-token" }).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your Apify API token (get one at https://console.apify.com/sign-up). |
| clean | boolean | – | If true (default), return only non-empty items and skip hidden fields. |
| datasetId | string | yes | The dataset ID (or username~dataset-name). Returned as `defaultDatasetId` from an Actor run. |
| limit | number | – | Maximum number of items to return. Default 100 (Apify itself has no default limit; we cap for readability). |
| offset | number | – | Number of items to skip from the start. Default 0. |
No output schema declared.
No examples provided.
apify_run_actor ~241
Run an Apify Actor (a cloud scraping/automation program) and get its dataset results in a single blocking call. The run is capped at 300 seconds. Pass the Actor input as an `input` object — its shape depends on the Actor. Example: apify_run_actor({ actorId: "apify~web-scraper", input: { startUrls: [{ url: "https://example.com" }] }, _apiKey: "your-token" }). Browse Actors at https://apify.com/store.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your Apify API token (get one at https://console.apify.com/sign-up, Settings → Integrations). |
| actorId | string | yes | Actor identifier. Use the tilde form "username~actor-name" (e.g. "apify~web-scraper"), a "username/actor-name" form (auto-normalized to tilde), or the raw Actor ID. |
| input | object | – | The Actor input JSON. Passed as the run INPUT. Shape is Actor-specific — see the Actor page in the Apify Store. Optional; defaults to {}. |
No output schema declared.
No examples provided.
apify_scrape_url ~126
Scrape a single web page (or crawl from it) and get clean, RAG-friendly markdown content. Convenience wrapper around the "apify~website-content-crawler" Actor. Example: apify_scrape_url({ url: "https://docs.apify.com/api/v2", _apiKey: "your-token" }).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your Apify API token (get one at https://console.apify.com/sign-up). |
| url | string | yes | The URL to scrape, e.g. "https://example.com/article". |
No output schema declared.
No examples provided.
How do I install the Apify MCP server?
Apify runs locally as an npm package, launched with npx -y @pipeworx/mcp-apify. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-apify
claude mcp add pipeworx-io-apify -- npx -y @pipeworx/mcp-apify
What is the Apify MCP server?
Apify is an MCP server listed in the public MCP registry as io.github.pipeworx-io/apify. Apify MCP, run web-scraping Actors and fetch their dataset results. This page covers its npm package (@pipeworx/mcp-apify).
Is the Apify MCP server safe to use?
Apify scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Apify MCP server expose?
Apify exposes 3 tools: apify_run_actor, apify_scrape_url, apify_dataset_items. Their descriptions and schemas cost roughly 551 tokens of context every time the server is loaded.
Is the Apify MCP server still maintained?
Apify 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 Apify MCP server under?
Apify declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.