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.

com.mcparmory/apify

PYPI · MCPARMORY-APIFY · 2 COMPONENTS · SCANNED SEP 20

Build, deploy, and run web scraping and automation actors in the cloud

Available components

oci · ghcr.io/mcparmory/apify:1.0.5 48 pypi · mcparmory-apify 75
0 this week 75 Trust /100
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 Security87
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Install-script risk not yet assessed.Unverified
  • 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 23887 tokens (~213/item across 112 items; 112 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 Management87
  • Stability observed for 26 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 Safety97
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 15 of 17 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "charge_run_event" implies "charge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
  • An AI judge read all 112 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the com.mcparmory/apify MCP server?

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

pypi · mcparmory-apify

# add to Claude Code
claude mcp add com-mcparmory-apify -- uvx mcparmory-apify
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mcparmory-apify": {
      "command": "uvx",
      "args": [
        "mcparmory-apify"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mcparmory-apify": {
      "command": "uvx",
      "args": [
        "mcparmory-apify"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-mcparmory-apify -- uvx mcparmory-apify
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcparmory-apify": {
      "type": "local",
      "command": [
        "uvx",
        "mcparmory-apify"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mcparmory-apify --command uvx --arg mcparmory-apify
# ~/.hermes/config.yaml
mcp_servers:
  com-mcparmory-apify:
    command: "uvx"
    args: ["mcparmory-apify"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mcparmory-apify": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcparmory-apify"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-mcparmory-apify -t stdio -c uvx -a mcparmory-apify
// mcp.json
{
  "mcpServers": {
    "com-mcparmory-apify": {
      "command": "uvx",
      "args": [
        "mcparmory-apify"
      ]
    }
  }
}
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.

  • 20 Sept 26 +16
    • Malware scan: unverified → pass ▲ security
  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 15 Sept 26 +16
    • Malware scan: unverified → pass ▲ security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified ▼ security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Sept 26 −18
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.80 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 20 Sept 2026 · Analysed pypi/mcparmory-apify@1.0.5

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 41 packages
Packages resolved 41
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 112 exposed · ~23,887 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
run_task_sync_get_dataset_items ~853

Runs an Actor task synchronously and returns the resulting dataset items directly in the response. Optionally override task input via the POST body and control output format, pagination, and field selection through query parameters.

NameTypeReqDescription
actorTaskIdstringyesThe unique identifier of the Actor task to run, either as a task ID or a tilde-separated string combining the owner's username and task name.
bodyobject–Optional JSON object to override specific input fields defined in the Actor task configuration. Fields not included in this payload retain their default values from the task or Actor input schema. Mu…
buildstring–Specifies which Actor build version to execute, provided as a build tag or build number. Defaults to the build defined in the task configuration, typically the latest tag.
delimiterstring–Single character used as the field delimiter in CSV output. Only applicable when format is csv. URL-encode special characters as needed. Defaults to a comma.
descboolean–When set to true, results are returned in reverse order from how they were stored. Defaults to ascending (insertion) order.
fieldsstring–Comma-separated list of field names to include in each returned item, excluding all other fields. Output fields are ordered according to the order specified in this list.
flattenstring–Comma-separated list of fields whose nested object values should be flattened into dot-notation keys on the parent object. The original nested object is replaced by the flattened representation.
formatstring–Output format for the returned dataset items. Supported values are json, jsonl, csv, html, xlsx, xml, and rss. Defaults to json.
limitnumber–Maximum number of items to include in the response. When omitted, all available items are returned.
maxItemsnumber–Maximum number of dataset items that will be charged for pay-per-result Actors. Does not cap the number of items returned — only limits billing. Accessible inside the Actor via the ACTOR_MAX_PAID_DAT…
maxTotalChargeUsdnumber–Maximum total cost in USD allowed for the run, intended for pay-per-event Actors to cap charges. Accessible inside the Actor via the ACTOR_MAX_TOTAL_CHARGE_USD environment variable.
memorynumber–Memory allocated to the run in megabytes. Must be a power of 2 and at least 128 MB. Defaults to the memory limit set in the task configuration.
offsetnumber–Number of items to skip from the beginning of the dataset before returning results. Useful for pagination. Defaults to 0.
omitstring–Comma-separated list of field names to exclude from each returned item. All other fields are retained.
restartOnErrorboolean–When set to true, the run will automatically restart if it encounters a failure.
skipEmptyboolean–When set to true, items with no fields or all-null values are excluded from the output. Note that the total number of returned items may be less than the specified limit when this option is active.
skipHeaderRowboolean–When set to true, omits the header row from csv format output.
skipHiddenboolean–When set to true, fields whose names begin with the # character are excluded from the output.
timeoutnumber–Maximum duration in seconds the run is allowed to execute before being timed out. If not provided, the timeout defined in the task configuration is used.
unwindstring–Comma-separated list of fields to unwind, processed in the specified order. Array fields produce one record per element merged with the parent; object fields are merged directly into the parent. Item…
xmlRootstring–Overrides the name of the root XML element in xml format output. Defaults to items.
xmlRowstring–Overrides the name of the element wrapping each individual record in xml format output. Defaults to item.

No output schema declared.

No examples provided.

test_webhook ~51

Sends a test dispatch to the specified webhook using a dummy payload. Useful for verifying that the webhook endpoint is correctly configured and reachable.

NameTypeReqDescription
webhookIdstringyesThe unique identifier of the webhook to test.

No output schema declared.

No examples provided.

unlock_queue_requests ~143

Unlocks all currently locked requests in the specified request queue that are held by the calling client. Within an Actor run, this releases locks held by both the current run and the same clientKey; outside a run, it releases all locks associated with the provided clientKey.

NameTypeReqDescription
clientKeystring–A unique string identifier (1–32 characters) representing the client accessing the queue, used to track whether multiple clients have accessed the same queue. If omitted, the system treats the reques…
queueIdstringyesThe unique identifier of the request queue, either as a queue ID or in the format username~queue-name.

No output schema declared.

No examples provided.

update_actor ~820

Updates the settings and configuration of an existing Actor by applying only the properties provided in the JSON request body. Returns the full updated Actor object after the changes are applied.

NameTypeReqDescription
actorIdstringyesThe unique ID of the Actor, or a tilde-separated string combining the owner's username and Actor name.
actorPermissionLevelstring–Specifies the permission level the Actor requires at runtime. Use LIMITED_PERMISSIONS for restricted access or FULL_PERMISSIONS for unrestricted platform access.
actorStandbyBuildstring–The build tag or version to use when starting the Actor in Standby mode.
actorStandbyMemoryMbytesinteger–The amount of memory in megabytes allocated when the Actor runs in Standby mode.
bodystring–The raw JSON request body payload containing the Actor settings to update, serialized as a string.
categoriesarray–An array of category identifiers under which the Actor is classified in Apify Store. Required when making the Actor public. Use constants from the apify-shared-js package.
contentTypestring–The MIME content type of the request body, which must be set to application/json.
defaultRunOptionsBuildstring–The default build tag or version to use when starting a run, such as a version tag.
defaultRunOptionsMemoryMbytesinteger–The default amount of memory in megabytes allocated to each Actor run.
descriptionstring–A short human-readable description of what the Actor does.
desiredRequestsPerActorRuninteger–The target number of concurrent requests the Actor Standby should aim to handle per active Actor run.
disableStandbyFieldsOverrideboolean–When true, prevents automatic overriding of Standby-related fields by the platform.
forcePermissionLevelstring–Overrides the permission level the Actor is forced to run with, regardless of the actorPermissionLevel setting.
idleTimeoutSecsinteger–The number of seconds a Standby Actor run may remain idle without receiving requests before it is shut down.
isDeprecatedboolean–Whether the Actor is marked as deprecated, signaling to users that it should no longer be used.
isEnabledboolean–Whether the Actor Standby mode is enabled, allowing the Actor to remain warm and handle requests without cold-start delays.
isPublicboolean–Whether the Actor is publicly visible in Apify Store. Setting this to true also requires providing a title and categories.
maxItemsinteger–The maximum number of items the Actor is allowed to return in a single run.
maxRequestsPerActorRuninteger–The maximum number of concurrent requests allowed per Actor run when operating in Standby mode.
namestring–The internal name identifier for the Actor.
pricingInfosarray–An array of pricing information objects associated with the Actor. Order is not significant.
restartOnErrorboolean–Whether the Actor should automatically restart if it encounters an error during a run.
seoDescriptionstring–The SEO-optimized description used for the Actor's page in Apify Store search results.
seoTitlestring–The SEO-optimized title used for the Actor's page in Apify Store search results.
shouldPassActorInputboolean–Whether the Actor's input schema should be forwarded to the Standby Actor run when it is initialized.
taggedBuildsobject–An object for managing build tags using a patch strategy — existing tags not included are preserved. Assign a tag by providing a buildId, or remove a tag by setting its value to null.
timeoutSecsinteger–The default maximum run duration in seconds before the run is forcefully stopped.
titlestring–The display title shown for the Actor in Apify Store. Required when making the Actor public.
versionsarray–An array of version objects defining the Actor's available versions and their source configurations. Order is not significant.

No output schema declared.

No examples provided.

update_actor_env_var ~199

Updates an existing environment variable for a specific Actor version. Only the properties included in the request body will be modified; omitted properties retain their current values.

NameTypeReqDescription
actorIdstringyesThe unique identifier of the Actor, either as an Actor ID or a tilde-separated combination of the owner's username and Actor name.
envVarNamestringyesThe exact name of the environment variable to update, as it appears in the Actor version's configuration.
isSecretboolean–Indicates whether the environment variable should be treated as a secret. Secret variables are encrypted at rest and masked in logs.
namestringyesThe updated name for the environment variable, typically uppercase with underscores following standard environment variable naming conventions.
valuestringyesThe updated value to assign to the environment variable.
versionNumberstringyesThe version number of the Actor whose environment variable you want to update, in major.minor format.

No output schema declared.

No examples provided.

update_actor_version ~335

Updates a specific version of an Actor with the provided fields, leaving unspecified properties unchanged. Send a JSON payload with only the fields you want to modify.

NameTypeReqDescription
actorIdstringyesThe Actor's unique ID or a tilde-separated combination of the owner's username and Actor name identifying which Actor to update.
applyEnvVarsToBuildboolean–When set to true, the defined environment variables are also injected into the build process, not just runtime execution.
buildTagstring–Tag label assigned to builds created from this version, used to reference the build when running the Actor.
envVarsarray–List of environment variables to make available to the Actor during execution and optionally during builds.
gitHubGistUrlstring–The URL of the GitHub Gist containing the Actor's source code; required when sourceType is GITHUB_GIST.
gitRepoUrlstring–The URL of the Git repository containing the Actor's source code; required when sourceType is GIT_REPO.
sourceFilesarray–Array of source file objects representing the Actor's code when sourceType is SOURCE_FILES; each item defines a file path and its content.
sourceTypestring–Defines where the Actor's source code originates, which determines which of the source URL fields are required.
tarballUrlstring–The URL of the tarball archive containing the Actor's source code; required when sourceType is TARBALL.
versionNumberstringyesThe version number of the Actor to update, following major.minor versioning format.

No output schema declared.

No examples provided.

update_dataset ~118

Updates a dataset's name and general access level by dataset ID or username-scoped name. Returns the full updated dataset object.

NameTypeReqDescription
datasetIdstringyesThe unique identifier of the dataset to update, either as a standalone dataset ID or in the format username~dataset-name.
generalAccessstring–Controls who can access the dataset: restrict to specific users, allow anyone with the ID or name to read, or inherit from the user's default sharing setting.
namestring–The new display name to assign to the dataset.

No output schema declared.

No examples provided.

update_key_value_store ~149

Updates a key-value store's name and general access level using the provided JSON payload. Returns the updated store object reflecting the applied changes.

NameTypeReqDescription
generalAccessstring–The general access level for the key-value store, controlling who can read or interact with it. Use RESTRICTED to limit access, ANYONE_WITH_ID_CAN_READ or ANYONE_WITH_NAME_CAN_READ for broader read a…
namestring–The new name to assign to the key-value store.
storeIdstringyesThe unique identifier of the key-value store to update, either as a store ID or in the format username~store-name.

No output schema declared.

No examples provided.

update_queue_request ~392

Updates an existing request in a queue, allowing you to modify its properties or mark it as handled. Setting `handledAt` to the current time removes the request from the head of the queue and releases any lock on it.

NameTypeReqDescription
clientKeystring–A unique string identifier (1–32 characters) representing the client making this call, used to detect whether the queue is being accessed by multiple clients simultaneously.
forefrontstring–Controls whether the updated request is repositioned to the front of the queue (`true`) or remains at the end (`false`). Defaults to `false`.
headersobject–A key-value map of HTTP headers to include when executing this request.
idstringyesThe unique identifier assigned to this request object, used to reference it within the queue.
imagestring–An optional URI pointing to an image associated with this request, must be a valid URI.
labelstring–An optional label for categorizing or routing the request during processing.
methodstring–The HTTP method to use when executing this request (e.g., GET, POST, PUT, DELETE).
noRetryboolean–When set to `true`, prevents the request from being retried automatically if its processing fails.
payloadobject–The body payload to send with the request, typically used for POST or PUT requests.
queueIdstringyesThe ID of the request queue, either as a direct queue ID or in the format `username~queue-name`.
requestIdstringyesThe unique ID of the request to update within the queue.
uniqueKeystringyesA unique key used to deduplicate requests; requests sharing the same key are treated as identical and will not be added more than once.
urlstringyesThe target URL for this request, must be a valid URI.

No output schema declared.

No examples provided.

update_request_queue ~98

Updates a request queue's name and resource access level by submitting a JSON payload with the desired changes. Returns the full updated request queue object upon success.

NameTypeReqDescription
bodyobject–JSON object containing the fields to update on the request queue, such as its name or general resource access level.
queueIdstringyesThe unique identifier of the request queue to update, either as a queue ID or in the format username~queue-name.

No output schema declared.

No examples provided.

update_run ~149

Updates an Actor run's status message and/or general resource access level. Use this to communicate progress to users via the Apify Console UI or to control who can view the run and its associated storages and logs.

NameTypeReqDescription
bodyobject–Request body containing the fields to update on the run. Supports setting a status message (with an optional terminal flag indicating it is the final message) and/or the general resource access level…
runIdstringyesThe unique identifier of the Actor run to update.

No output schema declared.

No examples provided.

update_schedule ~285

Updates an existing schedule by its ID, applying only the properties provided in the request body while leaving unspecified properties unchanged. Returns the full updated schedule object.

NameTypeReqDescription
actionsarray–An ordered list of action objects that the schedule will execute when triggered. Each item defines the type and configuration of an action to perform.
cronExpressionstring–The cron expression defining when the schedule triggers, using standard five-field cron syntax (minute, hour, day-of-month, month, day-of-week).
descriptionstring–A human-readable explanation of the schedule's purpose or context, useful for documentation and identification.
isEnabledboolean–Whether the schedule is active and will trigger its actions at the defined times. Set to false to pause the schedule without deleting it.
isExclusiveboolean–Whether the schedule runs exclusively, preventing overlapping executions if a previous run is still in progress when the next trigger fires.
namestring–A short machine-friendly identifier for the schedule, typically used for referencing it programmatically.
scheduleIdstringyesThe unique identifier of the schedule to update.
timezonestring–The IANA timezone name used to interpret the cron expression, ensuring triggers fire at the correct local time.
titlestring–A human-friendly display name for the schedule, intended for presentation in UIs or dashboards.

No output schema declared.

No examples provided.

update_task ~525

Update the settings, input configuration, and runtime options of an existing Actor task. Only properties included in the request body are modified; omitted properties retain their current values.

NameTypeReqDescription
actorStandbyBuildstring–The Actor build tag or version to use when the task is running in Standby mode.
actorStandbyMemoryMbytesinteger–Amount of memory in megabytes allocated to each task run when operating in Standby mode; must be a power of 2.
actorTaskIdstringyesThe unique identifier of the task to update, either as a task ID or a tilde-separated combination of the owner's username and task name.
desiredRequestsPerActorRuninteger–The target number of requests to process per Actor run when the task is operating in Standby mode.
disableStandbyFieldsOverrideboolean–When true, prevents task-level Standby field values from overriding the Actor's default Standby configuration.
idleTimeoutSecsinteger–Duration in seconds the Standby Actor is allowed to remain idle before it is considered inactive and shut down.
inputobject–The user-defined JSON input configuration passed to the Actor when the task is executed; structure depends on the specific Actor's input schema.
isEnabledboolean–Whether the task is enabled and available to be run; disabled tasks cannot be triggered.
maxItemsinteger–Maximum number of output dataset items the task is allowed to produce before the run is stopped.
maxRequestsPerActorRuninteger–The upper limit on the number of requests that can be processed per Actor run in Standby mode.
namestring–The URL-friendly name of the task, used to identify it within the owner's account.
optionsBuildstring–The Actor build tag or version to use when running the task, such as a version tag or 'latest'.
optionsMemoryMbytesinteger–Amount of memory in megabytes allocated to each task run; must be a power of 2.
restartOnErrorboolean–Whether the task run should automatically restart if it encounters an error during execution.
shouldPassActorInputboolean–When true, the Actor's own input is passed through to the task run in addition to the task's configured input.
timeoutSecsinteger–Maximum duration in seconds the task run is allowed to execute before it is forcefully stopped.
titlestring–A human-readable display title for the task, distinct from its URL-friendly name.

No output schema declared.

No examples provided.

update_task_input ~123

Updates the input configuration of a specific actor task by merging the provided JSON object with the existing input. Only the properties included in the request body are updated; omitted properties retain their current values.

NameTypeReqDescription
actorTaskIdstringyesThe unique identifier of the actor task to update, either as a standalone task ID or as a tilde-separated combination of the owner's username and the task's name.
bodyobject–A JSON object containing the input fields to update on the task. Only the specified properties will be modified; any properties not included will remain unchanged.

No output schema declared.

No examples provided.

update_webhook ~396

Updates an existing webhook's configuration by its ID, applying only the properties provided in the JSON request body. Returns the full updated webhook object.

NameTypeReqDescription
actorIdstring–The ID of the Actor whose events should trigger this webhook. Scopes the webhook to a specific Actor.
actorRunIdstring–The ID of the Actor run whose events should trigger this webhook. Scopes the webhook to a specific run.
actorTaskIdstring–The ID of the Actor task whose events should trigger this webhook. Scopes the webhook to a specific task.
descriptionstring–A human-readable description of the webhook's purpose or configuration for identification.
doNotRetryboolean–When true, failed webhook delivery attempts will not be retried automatically.
eventTypesarray–List of event types that trigger this webhook, such as actor run lifecycle events. Order is not significant; each item must be a valid event type string.
headersTemplatestring–A template string defining custom HTTP headers included with each webhook request. Supports variable interpolation using double curly brace syntax.
ignoreSslErrorsboolean–When true, SSL certificate errors on the target request URL are ignored. Use with caution in production environments.
isAdHocboolean–Indicates whether the webhook is ad hoc (created for a single run) rather than a persistent webhook.
payloadTemplatestring–A template string defining the JSON payload sent with each webhook request. Supports variable interpolation using double curly brace syntax.
requestUrlstring–The destination URL to which the webhook will send HTTP POST requests when triggered. Must be a valid URI.
shouldInterpolateStringsboolean–When true, string values within the payload and headers templates will have variable placeholders interpolated before the request is sent.
webhookIdstringyesThe unique identifier of the webhook to update.

No output schema declared.

No examples provided.

Common questions

What is the com.mcparmory/apify MCP server?

com.mcparmory/apify is an MCP server listed in the public MCP registry as com.mcparmory/apify. Build, deploy, and run web scraping and automation actors in the cloud. This page covers its PyPI package (mcparmory-apify).

Is the com.mcparmory/apify MCP server safe to use?

com.mcparmory/apify scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 com.mcparmory/apify MCP server expose?

com.mcparmory/apify exposes 112 tools: list_actors, create_actor, get_actor, update_actor, delete_actor, and 107 more. Their descriptions and schemas cost roughly 23,887 tokens of context every time the server is loaded.

Is the com.mcparmory/apify MCP server still maintained?

com.mcparmory/apify 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.