com.mcparmory/apify
OCI · GHCR.IO/MCPARMORY/APIFY:1.0.5 · 2 COMPONENTS · SCANNED SEP 20
Build, deploy, and run web scraping and automation actors in the cloud
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 Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
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: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management83
- Stability observed for 25 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/apify MCP server?
com.mcparmory/apify runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/apify:1.0.5. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/apify:1.0.5
claude mcp add com-mcparmory-apify -- docker run --rm -i ghcr.io/mcparmory/apify:1.0.5
{
"mcpServers": {
"com-mcparmory-apify": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/apify:1.0.5"
]
}
}
} {
"servers": {
"com-mcparmory-apify": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/apify:1.0.5"
]
}
}
} codex mcp add com-mcparmory-apify -- docker run --rm -i ghcr.io/mcparmory/apify:1.0.5
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-apify": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/apify:1.0.5"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-apify:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/apify:1.0.5"] {
"McpServers": {
"com-mcparmory-apify": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/apify:1.0.5"
]
}
}
} {
"mcpServers": {
"com-mcparmory-apify": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/apify:1.0.5"
]
}
}
} 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.
- 19 Sept 26 −2
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 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 −2
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 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.
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 oci/ghcr.io/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 | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
abort_build Abort Build ~81
Aborts a running or starting Actor build, immediately halting execution and returning the build's full details. Builds already in a terminal state (FINISHED, FAILED, ABORTING, TIMED-OUT) are unaffected by this call.
| Name | Type | Req | Description |
|---|---|---|---|
| buildId | string | yes | The unique identifier of the Actor build to abort, available in the build's Info tab. |
No output schema declared.
No examples provided.
abort_run Abort Run ~111
Aborts a currently starting or running Actor run, returning full run details. Runs already in a terminal state (FINISHED, FAILED, ABORTING, TIMED-OUT) are unaffected.
| Name | Type | Req | Description |
|---|---|---|---|
| gracefully | boolean | – | When true, the run is aborted gracefully by sending 'aborting' and 'persistState' events before force-stopping after 30 seconds, which is useful if you intend to resurrect the run later. |
| runId | string | yes | The unique identifier of the Actor run to abort. |
No output schema declared.
No examples provided.
add_queue_request Add Queue Request ~241
Adds a new URL request to a specified request queue for processing. If a request with the same uniqueKey already exists in the queue, returns the ID of the existing request instead of creating a duplicate.
| Name | Type | Req | Description |
|---|---|---|---|
| clientKey | string | – | A unique string identifier (1–32 characters) representing the client making this request, used to detect whether the queue has been accessed by multiple clients. |
| forefront | string | – | Controls where the request is inserted in the queue. Set to true to add at the front (head) of the queue, or false to append at the end. Defaults to false. |
| method | string | yes | The HTTP method to use when executing this request (e.g., GET, POST, PUT, DELETE). |
| queueId | string | yes | The ID of the target request queue, or a combined identifier in the format username~queue-name. |
| uniqueKey | string | yes | A unique key used to deduplicate requests — requests sharing the same uniqueKey are treated as identical and will not be added twice. |
| url | string | yes | The fully qualified URL to be fetched or processed by this request, must be a valid URI. |
No output schema declared.
No examples provided.
append_dataset_items Append Dataset Items ~120
Appends one or more JSON objects to the end of the specified dataset. The entire request is rejected with a 400 error if any item fails schema validation; payloads must not exceed 5 MB.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | – | A single JSON object or an array of JSON objects to append to the dataset in order; total payload must not exceed 5 MB, so split larger arrays into smaller batches. |
| datasetId | string | yes | The unique identifier of the target dataset, either as a dataset ID or in the format username~dataset-name. |
No output schema declared.
No examples provided.
batch_add_requests Batch Add Requests ~230
Adds up to 25 requests to a specified request queue in a single batch operation. Returns arrays of successfully processed and unprocessed requests, with unprocessed entries recommended for retry using exponential backoff.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | – | An array of request objects to add to the queue, with a maximum of 25 items per batch. Each item should include the request details such as URL and uniqueKey; order within the array does not affect q… |
| clientKey | string | – | A unique string identifier (1–32 characters) representing the calling client, used to detect whether the queue is being accessed by multiple clients simultaneously. Omitting this value causes the sys… |
| forefront | string | – | Controls whether each request in the batch is inserted at the front (head) or back (end) of the queue. Accepts a boolean string value; defaults to false, placing requests at the end. |
| queueId | string | yes | The unique identifier of the target request queue, either as a queue ID or in the format username~queue-name. |
No output schema declared.
No examples provided.
batch_delete_queue_requests Batch Delete Queue Requests ~200
Batch-deletes up to 25 requests from a specified request queue, identified by their ID or uniqueKey. Any requests that fail due to rate limiting or internal errors are returned in the response for retry, with exponential backoff recommended.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body, which must be set to application/json. |
| body | array | – | An array of request objects to delete, each identified by either an ID or uniqueKey field. The batch is limited to 25 requests; order is not significant. |
| clientKey | string | – | A unique string identifier (1–32 characters) representing the client accessing the queue, used to detect whether the queue has been accessed by multiple clients. If omitted, the system treats this ca… |
| queueId | string | yes | The 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.
build_actor Build Actor ~255
Triggers a new build for a specified Actor version, compiling its source code and dependencies into a runnable image. Returns the resulting build object, which may reflect a terminal or transitional status depending on wait time.
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | yes | The unique ID of the Actor, or a tilde-separated string combining the owner's username and Actor name. |
| betaPackages | boolean | – | When enabled, the Actor is built using beta versions of Apify NPM packages instead of the default latest stable versions. |
| tag | string | – | A label applied to the build upon successful completion; if omitted, the tag defaults to the value set in the Actor version's buildTag property. |
| useCache | boolean | – | When enabled, the build system reuses cached layers to speed up the build process; cache is disabled by default. |
| version | string | yes | The Actor version number to build, corresponding to a version defined in the Actor's configuration. |
| waitForFinish | number | – | Number of seconds the server will wait for the build to complete before returning a response; must be between 0 and 60, where 0 returns immediately with a transitional status and higher values may re… |
No output schema declared.
No examples provided.
charge_run_event Charge Run Event ~129
Charge for one or more occurrences of a configured pay-per-event (PPE) billing event within a specific Actor run. Must be called from within the Actor run using the same API token that started the run.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | The number of event occurrences to charge for in this request; must be a positive integer. |
| eventName | string | yes | The name of the billing event to charge for, which must exactly match one of the events configured in the Actor's pay-per-event settings. |
| runId | string | yes | The unique identifier of the Actor run to charge events against. |
No output schema declared.
No examples provided.
check_key_value_store_record_exists Check Key-Value Store Record Exists ~95
Checks whether a record exists in a key-value store under a specific key without retrieving its value. Useful for lightweight existence checks before performing read or write operations.
| Name | Type | Req | Description |
|---|---|---|---|
| recordKey | string | yes | The key identifying the record to check for existence within the key-value store. |
| storeId | string | yes | The unique identifier of the key-value store, either as a store ID or in the format username~store-name. |
No output schema declared.
No examples provided.
create_actor Create Actor ~753
Creates a new Actor on the Apify platform with the specified configuration, including source code versions, run options, and publishing settings. At least one version of the source code must be defined; set isPublic to true along with a title and categories to list the Actor in Apify Store.
| Name | Type | Req | Description |
|---|---|---|---|
| actorStandbyBuild | string | – | The build tag or version to use when starting the Actor in Standby mode. |
| actorStandbyMemoryMbytes | integer | – | Memory allocation in megabytes for the Actor when running in Standby mode. |
| body | string | – | Raw JSON string representing the default input body passed to the Actor run. |
| categories | array | – | List of Apify Store category identifiers under which the Actor is classified; required when isPublic is true. Use constants from the apify-shared-js package. |
| contentType | string | – | MIME content type of the input body, specifying encoding and format for correct parsing. |
| defaultRunOptionsBuild | string | – | The default build tag or version to use when starting a run, such as a semantic version tag or 'latest'. |
| defaultRunOptionsMemoryMbytes | integer | – | Default memory allocation in megabytes for each Actor run; must be a power of 2. |
| description | string | – | Short human-readable description of what the Actor does, displayed in Apify Store and the Actor detail page. |
| desiredRequestsPerActorRun | integer | – | Target number of requests to be processed per Actor run in Standby mode, used for autoscaling decisions. |
| disableStandbyFieldsOverride | boolean | – | When true, prevents automatic overriding of Standby-related fields by the platform during Actor configuration updates. |
| forcePermissionLevel | string | – | Specifies the permission level the Actor requires at runtime; use LIMITED_PERMISSIONS to restrict access or FULL_PERMISSIONS for unrestricted access. See Actor permissions documentation for details. |
| idleTimeoutSecs | integer | – | Duration in seconds after which an idle Standby Actor instance is terminated to free resources. |
| isEnabled | boolean | – | Whether the Actor is enabled and available to be run; set to false to disable the Actor without deleting it. |
| isPublic | boolean | – | Whether the Actor is publicly listed in Apify Store; requires title and categories to be set when true. |
| maxItems | integer | – | Maximum number of output items the Actor is allowed to produce per run; used for pay-per-result pricing enforcement. |
| maxRequestsPerActorRun | integer | – | Hard upper limit on the number of requests processed per Actor run in Standby mode. |
| name | string | – | Unique identifier name for the Actor, used in URLs and API references. |
| pricingInfos | array | – | List of pricing information objects associated with the Actor, defining monetization tiers or pay-per-result configurations. |
| restartOnError | boolean | – | Whether the Actor run should automatically restart if it encounters an error during execution. |
| seoDescription | string | – | SEO-optimized description for the Actor's store page, used for search engine indexing. |
| seoTitle | string | – | SEO-optimized title for the Actor's store page, used for search engine indexing. |
| shouldPassActorInput | boolean | – | Whether the Actor's input should be forwarded to Standby mode instances when they are activated. |
| timeoutSecs | integer | – | Default maximum run duration in seconds; the run is terminated if it exceeds this limit. |
| title | string | – | Display title for the Actor shown in Apify Store; required when making the Actor public. |
| versions | array | – | List of source code version objects defining the Actor's versioned implementations; at least one version is required. Each item follows the Version object schema. |
No output schema declared.
No examples provided.
create_actor_env_var Create Actor Version Environment Variable ~161
Creates a new environment variable for a specific version of an Actor. Requires a name and value, with an optional flag to mark the variable as secret.
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | yes | The unique identifier of the Actor, either as an Actor ID or a tilde-separated combination of the owner's username and Actor name. |
| isSecret | boolean | – | Indicates whether the environment variable should be treated as a secret, hiding its value from logs and the UI. |
| name | string | yes | The name of the environment variable, typically uppercase with underscores following standard environment variable naming conventions. |
| value | string | yes | The value assigned to the environment variable. |
| versionNumber | string | yes | The version number of the Actor to which the environment variable will be added. |
No output schema declared.
No examples provided.
create_actor_version Create Actor Version ~430
Creates a new version of an Actor by specifying a version number and source type along with the corresponding source details. The source type determines which additional properties are required (e.g., a Git repository URL for GIT_REPO, a tarball URL for TARBALL).
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | yes | The unique identifier of the Actor, either as an Actor ID or a tilde-separated combination of the owner's username and Actor name. |
| applyEnvVarsToBuild | boolean | – | When set to true, the defined environment variables are also injected into the build process, not just runtime execution. |
| buildTag | string | – | A tag label applied to builds created from this version, used to reference or promote specific builds (e.g., marking a build as the latest stable release). |
| envVars | array | – | A list of environment variables to make available to the Actor at runtime and optionally during builds. Each item should specify the variable name and value. |
| gitHubGistUrl | string | – | The URL of a GitHub Gist containing the Actor's source code; required when sourceType is GITHUB_GIST. |
| gitRepoUrl | string | – | The URL of the Git repository containing the Actor's source code; required when sourceType is GIT_REPO. |
| sourceFiles | array | – | An array of source file objects representing the Actor's code when sourceType is SOURCE_FILES. Each item defines a file's name, content, and format. |
| sourceType | string | – | Defines where the Actor's source code is hosted; must be one of the supported source types. Each value requires its own additional properties: SOURCE_FILES uses sourceFiles, GIT_REPO uses gitRepoUrl,… |
| tarballUrl | string | – | The URL of a tarball archive containing the Actor's source code; required when sourceType is TARBALL. |
| versionNumber | string | – | The semantic version number to assign to this Actor version, following a major.minor format. |
No output schema declared.
No examples provided.
create_dataset Create Dataset ~84
Creates a new dataset for storing structured data and returns its object. If a name is provided and a dataset with that name already exists, the existing dataset object is returned instead.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional unique human-readable name for the dataset, allowing easy identification and retrieval in the future. If omitted, the dataset is unnamed and subject to the platform's data retention policy. |
No output schema declared.
No examples provided.
create_key_value_store Create Key-Value Store ~83
Creates a new key-value store and returns its store object. If a store with the specified name already exists, the existing store is returned instead of creating a duplicate.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional unique name for the store, making it easy to identify and retrieve later. If omitted, an unnamed store is created and subject to the platform's data retention policy. |
No output schema declared.
No examples provided.
create_request_queue Create Request Queue ~86
Creates a new request queue and returns its object, or returns the existing queue object if a queue with the given name already exists. Unnamed queues are subject to the platform's data retention policy.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional unique name for the request queue, allowing easy identification and retrieval in the future. If omitted, an unnamed queue is created and subject to data retention limits. |
No output schema declared.
No examples provided.
create_schedule Create Schedule ~260
Creates a new schedule with the specified configuration, including timing, timezone, and associated actions. Returns the fully created schedule object upon success.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | – | List of actions to execute when the schedule triggers. Each item defines an action type and its configuration; order determines execution sequence. |
| cronExpression | string | – | Defines the schedule's timing using standard cron syntax (minute, hour, day-of-month, month, day-of-week). |
| description | string | – | Human-readable explanation of the schedule's purpose, useful for documentation and identifying what the schedule does. |
| isEnabled | boolean | – | Controls whether the schedule is active and will trigger at its configured times. Set to false to create the schedule in a paused state. |
| isExclusive | boolean | – | When true, ensures only one run of this schedule executes at a time, preventing overlapping executions if a previous run is still in progress. |
| name | string | – | Unique identifier name for the schedule, used to reference it programmatically. |
| timezone | string | – | IANA timezone name used to interpret the cron expression, ensuring the schedule fires at the correct local time. |
| title | string | – | Display-friendly label for the schedule shown in the UI, distinct from the programmatic name. |
No output schema declared.
No examples provided.
create_task Create Task ~80
Creates a new actor task with the specified configuration, including the target actor, build version, timeout, and memory settings. Returns the full task object upon successful creation.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | JSON object defining the new task's configuration, including the actor to run, the task name, and execution options such as build version, timeout, and memory allocation. |
No output schema declared.
No examples provided.
create_webhook Create Webhook ~567
Creates a new webhook that triggers HTTP POST requests to a target URL when specified Actor or task events occur. Use an idempotency key to safely retry creation without duplicating webhooks.
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | – | ID of the Actor to assign this webhook to. Provide inside the condition object along with optionally actorTaskId to scope the webhook to a specific Actor. |
| actorRunId | string | – | ID of a specific Actor run to associate with this webhook, used to scope the webhook to a particular run instance. |
| actorTaskId | string | – | ID of the Actor task to assign this webhook to. Provide inside the condition object to scope the webhook to a specific task run. |
| description | string | – | Optional human-readable label for the webhook to help identify its purpose. |
| doNotRetry | boolean | – | When true, failed webhook dispatch attempts will not be retried. Defaults to false, meaning Apify will retry on failure. |
| eventTypes | array | yes | List of event types that will trigger this webhook. Each item must be a valid Apify event string (e.g., ACTOR.RUN.SUCCEEDED, ACTOR.RUN.FAILED, ACTOR.RUN.ABORTED). Order is not significant. |
| headersTemplate | string | – | A JSON-like template string defining custom HTTP headers sent with the webhook request. Supports Apify template variables. Note: host, Content-Type, X-Apify-Webhook, X-Apify-Webhook-Dispatch-Id, and… |
| idempotencyKey | string | – | Unique key used to prevent duplicate webhook creation. Multiple requests with the same key will only create the webhook once and return the existing webhook on subsequent calls. Use a UUID or suffici… |
| ignoreSslErrors | boolean | – | When true, SSL certificate errors on the target requestUrl will be ignored during webhook dispatch. Defaults to false. |
| isAdHoc | boolean | – | When true, marks the webhook as ad-hoc (not permanently assigned to an Actor or task). Defaults to false for standard persistent webhooks. |
| payloadTemplate | string | – | A JSON-like template string defining the payload sent to the requestUrl. Supports Apify template variables (e.g., {{userId}}, {{resource}}). If shouldInterpolateStrings is true, variables inside stri… |
| requestUrl | string | yes | The target URL to which webhook event data is sent as an HTTP POST request with a JSON payload. Must be a valid absolute URI. |
| shouldInterpolateStrings | boolean | – | When true, Apify template variables found inside string values within the payloadTemplate are interpolated. When false, only top-level variable placeholders are replaced. |
No output schema declared.
No examples provided.
delete_actor Delete Actor ~61
Permanently deletes the specified Actor and all associated data. This action is irreversible.
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | yes | The unique identifier of the Actor to delete, either as a standalone Actor ID or as a tilde-separated combination of the owner's username and Actor name. |
No output schema declared.
No examples provided.
delete_actor_run Delete Actor Run ~67
Permanently deletes a finished actor run. Only completed runs can be deleted, and only by the user or organization that initiated the run.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | The unique identifier of the actor run to delete. The run must be in a finished state before it can be deleted. |
No output schema declared.
No examples provided.
delete_actor_version Delete Actor Version ~95
Permanently deletes a specific version of an Actor's source code. This action is irreversible and removes the version along with its associated configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | yes | The unique identifier of the Actor, either as a standalone Actor ID or as a tilde-separated combination of the owner's username and Actor name. |
| versionNumber | string | yes | The version number of the Actor to delete, following major.minor versioning format. |
No output schema declared.
No examples provided.
delete_actor_version_env_var Delete Actor Version Environment Variable ~118
Permanently deletes a specific environment variable from a given Actor version. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | yes | The unique identifier of the Actor, either as an Actor ID or a tilde-separated combination of the owner's username and Actor name. |
| envVarName | string | yes | The exact name of the environment variable to delete, typically uppercase with underscores as separators. |
| versionNumber | string | yes | The version number of the Actor from which the environment variable will be deleted, following major.minor versioning format. |
No output schema declared.
No examples provided.
delete_build Delete Build ~68
Permanently deletes a specific Actor build by its ID. The current default build for an Actor cannot be deleted; only users with build permissions for the Actor may perform this action.
| Name | Type | Req | Description |
|---|---|---|---|
| buildId | string | yes | The unique identifier of the Actor build to delete, found in the build's Info tab. |
No output schema declared.
No examples provided.
delete_dataset Delete Dataset ~71
Permanently deletes a specific dataset and its associated data. This action is irreversible and removes the dataset from the account.
| Name | Type | Req | Description |
|---|---|---|---|
| datasetId | string | yes | The unique identifier of the dataset to delete, accepted either as a standalone dataset ID or as a combined username and dataset name in the format `username~dataset-name`. |
No output schema declared.
No examples provided.
delete_key_value_store Delete Key-Value Store ~71
Permanently deletes a key-value store and all of its contents. This action is irreversible and removes the store along with all stored key-value pairs.
| Name | Type | Req | Description |
|---|---|---|---|
| storeId | string | yes | The unique identifier of the key-value store to delete, either as a store ID or in the format username~store-name. |
No output schema declared.
No examples provided.
delete_key_value_store_record Delete Key-Value Store Record ~85
Permanently removes a single record from a key-value store by its key. The store itself and all other records remain unaffected.
| Name | Type | Req | Description |
|---|---|---|---|
| recordKey | string | yes | The key identifying the specific record to delete within the store. |
| storeId | string | yes | The unique identifier of the key-value store, either as a store ID or in the format username~store-name. |
No output schema declared.
No examples provided.
delete_queue_request Delete Queue Request ~135
Permanently removes a specific request from a request queue by its ID. Use this to discard requests that are no longer needed for processing.
| Name | Type | Req | Description |
|---|---|---|---|
| clientKey | string | – | A unique string (1–32 characters) identifying the client making this call, used to track whether the queue has been accessed by multiple clients. If omitted, the system treats this call as originatin… |
| queueId | string | yes | The unique identifier of the request queue, either as a queue ID or in the format username~queue-name. |
| requestId | string | yes | The unique identifier of the request to delete from the queue. |
No output schema declared.
No examples provided.
delete_request_lock Delete Request Lock ~201
Releases a lock on a specific request in a queue, making it available for other clients to process. Only the client that originally locked the request (via the lock head operation) can delete its lock.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body, which must be application/json. |
| clientKey | string | – | A unique string identifier (1–32 characters) representing the client releasing the lock. Must match the client key used when the lock was originally acquired. |
| forefront | string | – | Controls where the request is re-inserted in the queue after the lock is removed — set to true to place it at the front of the queue, or false to append it to the end. |
| queueId | string | yes | The unique identifier of the request queue, either as a queue ID or in the format username~queue-name. |
| requestId | string | yes | The unique identifier of the request whose lock should be deleted. |
No output schema declared.
No examples provided.
delete_request_queue Delete Request Queue ~67
Permanently deletes a request queue and all its associated data. This action is irreversible and removes the queue identified by its ID or name.
| Name | Type | Req | Description |
|---|---|---|---|
| queueId | string | yes | The unique identifier of the request queue to delete, either as a queue ID or in the format username~queue-name. |
No output schema declared.
No examples provided.
delete_schedule Delete Schedule ~40
Permanently deletes a schedule by its unique identifier. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| scheduleId | string | yes | The unique identifier of the schedule to delete. |
No output schema declared.
No examples provided.
delete_task Delete Task ~70
Permanently deletes the specified actor task and all associated configuration. This action is irreversible and removes the task from the account.
| Name | Type | Req | Description |
|---|---|---|---|
| actorTaskId | string | yes | The unique identifier of the task to delete, either as a standalone task ID or as a tilde-separated combination of the owner's username and task name. |
No output schema declared.
No examples provided.
delete_webhook Delete Webhook ~50
Permanently deletes a webhook by its unique identifier. This action is irreversible and will stop all event notifications associated with the webhook.
| Name | Type | Req | Description |
|---|---|---|---|
| webhookId | string | yes | The unique identifier of the webhook to delete. |
No output schema declared.
No examples provided.
get_account_limits Get Account Limits ~39
Retrieves a complete summary of the authenticated account's limits, current usage cycle, and usage statistics, equivalent to the Limits page in the Apify console.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_actor Get Actor ~76
Retrieves full details for a specific Actor, including its configuration, settings, and metadata. Use this to inspect an Actor before running it or to verify its current state.
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | yes | The unique identifier of the Actor to retrieve, either as an Actor ID or a tilde-separated combination of the owner's username and Actor name. |
No output schema declared.
No examples provided.
get_actor_build Get Actor Build ~135
Retrieves full details about a specific Actor build, including its status, timing, and resource usage. Supports synchronous waiting via an optional timeout parameter to avoid polling when monitoring build completion.
| Name | Type | Req | Description |
|---|---|---|---|
| buildId | string | yes | The unique identifier of the Actor build to retrieve. |
| waitForFinish | number | – | Maximum number of seconds the server will wait for the build to reach a terminal status before responding. Accepts values from 0 (default, return immediately) to 60. If the build finishes within the… |
No output schema declared.
No examples provided.
get_actor_env_var Get Actor Version Environment Variable ~119
Retrieves details of a specific environment variable for a given Actor version. If the variable is marked as secret, its value will be omitted from the response.
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | yes | The unique ID of the Actor, or a tilde-separated combination of the owner's username and Actor name. |
| envVarName | string | yes | The exact name of the environment variable to retrieve, typically uppercase with underscores. |
| versionNumber | string | yes | The version number of the Actor to retrieve the environment variable from, following major.minor versioning format. |
No output schema declared.
No examples provided.
get_actor_run Get Actor Run ~125
Retrieves all details about a specific Actor run, including its status, timing, and usage statistics. Optionally waits synchronously for the run to finish, eliminating the need for repeated polling.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | The unique identifier of the Actor run to retrieve. |
| waitForFinish | number | – | Maximum number of seconds the server will wait for the run to reach a terminal status before responding. Accepts values from 0 to 60; if the run finishes within the specified time the response will r… |
No output schema declared.
No examples provided.
get_actor_version Get Actor Version ~98
Retrieves detailed information about a specific version of an Actor, including its configuration and metadata. Useful for inspecting the exact state of a particular Actor version.
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | yes | The unique identifier of the Actor, either as a standalone Actor ID or as a tilde-separated combination of the owner's username and Actor name. |
| versionNumber | string | yes | The version number of the Actor to retrieve, following a major.minor versioning format. |
No output schema declared.
No examples provided.
get_build_log Get Build Log ~86
Retrieves the log output for a specific actor build. Supports real-time log streaming while the build is in progress.
| Name | Type | Req | Description |
|---|---|---|---|
| buildId | string | yes | The unique identifier of the actor build whose log you want to retrieve. |
| stream | boolean | – | When set to true, the response will stream log output continuously as long as the build is still running, rather than returning a static snapshot. |
No output schema declared.
No examples provided.
get_current_user Get Current User ~46
Retrieves both public and private profile data for the authenticated user account identified by the provided token. Note that plan, email, and profile fields are excluded when accessed from within an Actor run.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_dataset Get Dataset ~80
Retrieves metadata and storage information for a specific dataset by its ID. Note that item count fields may lag up to 5 seconds behind actual data; use the list dataset items endpoint to retrieve the dataset's contents.
| Name | Type | Req | Description |
|---|---|---|---|
| datasetId | string | yes | The unique identifier of the dataset, either as a standalone dataset ID or in the combined username~dataset-name format. |
No output schema declared.
No examples provided.
get_dataset_statistics Get Dataset Statistics ~67
Retrieves field-level statistics for a specified dataset. Returns aggregated metrics such as value counts, null rates, and type distributions for each field in the dataset.
| Name | Type | Req | Description |
|---|---|---|---|
| datasetId | string | yes | The unique identifier of the dataset, either as a dataset ID or in the format username~dataset-name. |
No output schema declared.
No examples provided.
get_default_actor_build Get Default Actor Build ~165
Retrieves the default build for a specified Actor, optionally waiting synchronously for the build to reach a terminal state. No authentication token is required, though unauthenticated requests will have certain usage cost fields omitted from the response.
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | yes | The unique identifier of the Actor, either as a standalone Actor ID or as a tilde-separated combination of the owner's username and Actor name. |
| waitForFinish | number | – | Maximum number of seconds the server will wait for the build to finish before returning; if the build completes within this window the response will reflect a terminal status (e.g. SUCCEEDED), otherw… |
No output schema declared.
No examples provided.
get_key_value_store Get Key-Value Store ~70
Retrieves full details about a specific key-value store, including its configuration and metadata. Use this to inspect store properties before reading or writing data.
| Name | Type | Req | Description |
|---|---|---|---|
| storeId | string | yes | The unique identifier of the key-value store to retrieve, either as a store ID or in the format username~store-name. |
No output schema declared.
No examples provided.
get_key_value_store_record Get Key-Value Store Record ~151
Retrieves the value stored under a specific key in a key-value store, returning the record with its original content type and encoding. Use the attachment parameter to fetch raw HTML content without Apify's security modifications.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment | boolean | – | When set to true, the response is served with a Content-Disposition: attachment header, prompting browsers to download the file rather than render it, and bypasses Apify's HTML security modifications… |
| recordKey | string | yes | The key under which the record is stored in the key-value store. |
| storeId | string | yes | The unique identifier of the key-value store, either as a store ID or in the format username~store-name. |
No output schema declared.
No examples provided.
get_last_actor_run Get Last Actor Run ~125
Retrieves the most recent run of a specified Actor, with optional filtering by run status. Also serves as the base path for accessing the last run's default storages (log, key-value store, dataset, and request queue) via sub-endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| actorId | string | yes | The unique ID of the Actor, or a tilde-separated combination of the owner's username and Actor name. |
| status | string | – | Filters the result to only return the last run matching the specified status, ensuring you retrieve a run in a particular state (e.g. only succeeded runs). |
No output schema declared.
No examples provided.
get_last_task_run Get Last Task Run ~122
Retrieves the most recent run of a specified actor task, with optional filtering by run status. Also serves as the base path for accessing the last run's default storages (log, key-value store, dataset, request queue) via sub-endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| actorTaskId | string | yes | The unique identifier of the actor task, either as a task ID or a tilde-separated combination of the owner's username and task name. |
| status | string | – | Restricts the result to the last run matching the specified status, ensuring runs in other states are ignored. |
No output schema declared.
No examples provided.
get_monthly_usage Get Monthly Usage ~81
Retrieves a complete summary of your usage for the current or a specified billing cycle, including storage, data transfer, and request queue usage with both an overall total and a daily breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The date within the billing cycle you want to retrieve usage for, in YYYY-MM-DD format. If omitted, the current billing cycle is returned. |
No output schema declared.
No examples provided.
get_queue_request Get Queue Request ~84
Retrieves a specific request from a request queue by its ID. Returns the full request details including URL, metadata, and processing status.
| Name | Type | Req | Description |
|---|---|---|---|
| queueId | string | yes | The unique identifier of the request queue, either as a queue ID or in the format username~queue-name. |
| requestId | string | yes | The unique identifier of the request to retrieve from the specified queue. |
No output schema declared.
No examples provided.
get_request_queue Get Request Queue ~71
Retrieves metadata and configuration details for a specific request queue. Returns the full queue object including its properties and current state.
| Name | Type | Req | Description |
|---|---|---|---|
| queueId | string | yes | The unique identifier of the request queue to retrieve. Accepts either the queue's ID or a combined username and queue name in the format username~queue-name. |
No output schema declared.
No examples provided.
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 container image (ghcr.io/mcparmory/apify:1.0.5).
Is the com.mcparmory/apify MCP server safe to use?
com.mcparmory/apify scores 48 out of 100 on VerifyMCP. 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.