com.mcparmory/files-com
OCI · GHCR.IO/MCPARMORY/FILES-COM:1.0.3 · 2 COMPONENTS · SCANNED SEP 20
Manage files, users, and automated workflows across cloud storage and protocols
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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 23890 tokens (~121/item across 197 items; 197 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 Management90
- Stability observed for 27 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 Safety98
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 29 of 31 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "share_bundle" implies "send" 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 197 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/files-com MCP server?
com.mcparmory/files-com runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/files-com:1.0.3. 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/files-com:1.0.3
claude mcp add com-mcparmory-files-com -- docker run --rm -i ghcr.io/mcparmory/files-com:1.0.3
{
"mcpServers": {
"com-mcparmory-files-com": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/files-com:1.0.3"
]
}
}
} {
"servers": {
"com-mcparmory-files-com": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/files-com:1.0.3"
]
}
}
} codex mcp add com-mcparmory-files-com -- docker run --rm -i ghcr.io/mcparmory/files-com:1.0.3
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-files-com": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/files-com:1.0.3"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-files-com:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/files-com:1.0.3"] {
"McpServers": {
"com-mcparmory-files-com": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/files-com:1.0.3"
]
}
}
} {
"mcpServers": {
"com-mcparmory-files-com": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/files-com:1.0.3"
]
}
}
} 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 +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.
- 18 Sept 26 −3
- Stability: pass → 0.83 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 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.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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/files-com:1.0.3
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 →
delete_user Delete User ~38
Permanently delete a user account by ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the user to delete. |
No output schema declared.
No examples provided.
delete_user_request Delete User Request ~45
Delete a specific user request by its ID. This operation permanently removes the user request from the system.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the user request to delete. |
No output schema declared.
No examples provided.
download_file Download File ~160
Download a file from the specified path with optional preview generation, metadata retrieval, or redirect handling. Supports stat mode to retrieve file information without initiating a download.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Controls the response behavior: leave blank for standard download, use 'stat' to retrieve file metadata without a download URL, or use 'redirect' to receive a 302 redirect directly to the file. |
| path | string | yes | The file path to download or retrieve information for. |
| preview_size | string | – | The size of the preview image to generate. Larger sizes provide higher resolution previews. |
| with_previews | boolean | – | Include preview image data in the response when available. |
| with_priority_color | boolean | – | Include priority color metadata in the response when available. |
No output schema declared.
No examples provided.
download_remote_server_configuration Download Remote Server Configuration ~58
Download the configuration file for a Remote Server. This file is required for integrating certain Remote Server types, such as the Files.com Agent.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the Remote Server for which to download the configuration file. |
No output schema declared.
No examples provided.
export_action_notifications Export Action Notifications ~310
Generate an export of action notification records filtered by date range, folder, file path, webhook configuration, and delivery status. Use this to audit webhook delivery history and troubleshoot notification failures.
| Name | Type | Req | Description |
|---|---|---|---|
| end_at | string | – | End date and time for the export range (inclusive). Notifications triggered after this timestamp will be excluded. |
| query_folder | string | – | Filter to notifications triggered by actions within a specific folder. Useful for isolating notifications from a particular directory. |
| query_message | string | – | Filter to notifications with a specific error message. Helps identify notifications that failed with particular error conditions. |
| query_path | string | – | Filter to notifications triggered by actions on a specific file or resource path. Use to track notifications for a particular file. |
| query_request_method | string | – | Filter by the HTTP method used in the webhook request (e.g., GET, POST, PUT). Narrows results to notifications sent with a specific request method. |
| query_request_url | string | – | Filter by the target webhook URL. Use to isolate notifications sent to a specific endpoint. |
| query_status | string | – | Filter by the HTTP status code returned from the webhook server. Helps identify notifications that received specific response codes. |
| query_success | boolean | – | Filter by webhook delivery success. Set to true for successful deliveries (HTTP 200 or 204 responses) or false for failed deliveries. |
| start_at | string | – | Start date and time for the export range (inclusive). Notifications triggered before this timestamp will be excluded. |
No output schema declared.
No examples provided.
get_action_notification_export Get Action Notification Export ~57
Retrieve details of a specific action notification export by its ID. Use this to view the status, configuration, and results of a previously created notification export.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the action notification export to retrieve. |
No output schema declared.
No examples provided.
get_api_key Get API Key ~48
Retrieve a specific API key by its ID. Use this to view details of an existing API key in your account.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the API key to retrieve. |
No output schema declared.
No examples provided.
get_as2_partner Get AS2 Partner ~47
Retrieve details for a specific AS2 partner by ID. Returns the partner's configuration and connection information.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the AS2 partner to retrieve. |
No output schema declared.
No examples provided.
get_as2_station Get AS2 Station ~51
Retrieve details for a specific AS2 station by its ID. Returns the configuration and status information for the AS2 station.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the AS2 station to retrieve. |
No output schema declared.
No examples provided.
get_automation Get Automation ~42
Retrieve details for a specific automation by its ID. Returns the automation configuration and current state.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the automation to retrieve. |
No output schema declared.
No examples provided.
get_automation_run Get Automation Run ~52
Retrieve details of a specific automation run by its ID. Returns the current state, execution history, and results of the automation run.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the automation run to retrieve. |
No output schema declared.
No examples provided.
get_behavior Get Behavior ~34
Retrieve detailed information about a specific behavior by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the behavior to retrieve. |
No output schema declared.
No examples provided.
get_bundle Get Bundle ~34
Retrieve detailed information about a specific bundle by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the bundle to retrieve. |
No output schema declared.
No examples provided.
get_bundle_notification Get Bundle Notification ~50
Retrieve details for a specific bundle notification by its ID. Use this to fetch the full notification record including its content and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the bundle notification to retrieve. |
No output schema declared.
No examples provided.
get_clickwrap Get Clickwrap ~47
Retrieve a specific clickwrap agreement by its ID. Returns the clickwrap details including its configuration and status.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the clickwrap agreement to retrieve. |
No output schema declared.
No examples provided.
get_current_api_key Get Current API Key ~42
Retrieve detailed information about the API key currently being used for authentication. This operation requires the API connection to be authenticated using an API key rather than other authentication methods.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_external_event Get External Event ~46
Retrieve details for a specific external event by its ID. Returns the complete event information including metadata and configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the external event to retrieve. |
No output schema declared.
No examples provided.
get_file_metadata Get File Metadata ~111
Retrieve metadata for a file or folder at the specified path, optionally including preview and priority information.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The file system path to the target file or folder. |
| preview_size | string | – | The size of the file preview to include in the response. Determines the resolution and detail level of preview data. |
| with_previews | boolean | – | Whether to include preview information in the response metadata. |
| with_priority_color | boolean | – | Whether to include priority color information in the response metadata. |
No output schema declared.
No examples provided.
get_file_migration Get File Migration ~51
Retrieve details of a specific file migration by its ID. Use this to check the status and information of a file migration operation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the file migration to retrieve. |
No output schema declared.
No examples provided.
get_form_field_set Get Form Field Set ~50
Retrieve a specific form field set by its ID. Returns the complete configuration and structure of the requested form field set.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the form field set to retrieve. |
No output schema declared.
No examples provided.
get_group Get Group ~34
Retrieve detailed information about a specific group by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the group to retrieve. |
No output schema declared.
No examples provided.
get_history_export Get History Export ~54
Retrieve details of a specific history export by its ID. Use this to check the status, metadata, and information about a previously created history export.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the history export to retrieve. |
No output schema declared.
No examples provided.
get_invoice Get Invoice ~44
Retrieve a specific invoice by its ID. Returns detailed invoice information including amounts, dates, and line items.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the invoice to retrieve. |
No output schema declared.
No examples provided.
get_message Get Message ~44
Retrieve a specific message by its ID. Returns the full message details including content, metadata, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the message to retrieve. |
No output schema declared.
No examples provided.
get_message_comment Get Message Comment ~43
Retrieve a specific message comment by its ID. Returns the full details of the requested comment.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the message comment to retrieve. |
No output schema declared.
No examples provided.
get_message_comment_reaction Get Message Comment Reaction ~54
Retrieve details of a specific message comment reaction by its ID. Use this to fetch information about a user's reaction to a message comment.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the message comment reaction to retrieve. |
No output schema declared.
No examples provided.
get_message_reaction Get Message Reaction ~50
Retrieve details of a specific message reaction by its ID. Use this to fetch information about a single reaction to a message.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the message reaction to retrieve. |
No output schema declared.
No examples provided.
get_notification Get Notification ~40
Retrieve a specific notification by its ID. Returns the full details of the requested notification.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the notification to retrieve. |
No output schema declared.
No examples provided.
get_payment Get Payment ~46
Retrieve details for a specific payment by its ID. Returns the payment information including amount, status, and transaction details.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the payment to retrieve. |
No output schema declared.
No examples provided.
get_project Get Project ~34
Retrieve detailed information about a specific project by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the project to retrieve. |
No output schema declared.
No examples provided.
get_public_key Get Public Key ~48
Retrieve a specific public key by its ID. Use this to fetch details of a previously created or stored public key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the public key to retrieve. |
No output schema declared.
No examples provided.
get_remote_server Get Remote Server ~48
Retrieve details for a specific remote server by its ID. Returns the configuration and status information for the requested remote server.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the remote server to retrieve. |
No output schema declared.
No examples provided.
get_sftp_host_key Get SFTP Host Key ~56
Retrieve details for a specific SFTP host key by its ID. Use this to view the configuration and properties of an existing host key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the SFTP host key to retrieve. |
No output schema declared.
No examples provided.
get_site_usage Get Site Usage ~37
Retrieve the most recent usage snapshot for a site, containing billing-related usage data. This provides a point-in-time view of resource consumption metrics.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_sso_strategy Get SSO Strategy ~57
Retrieve a specific SSO (Single Sign-On) strategy by its ID. Use this to view the configuration and details of an existing SSO strategy.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the SSO strategy to retrieve. |
No output schema declared.
No examples provided.
get_user Get User ~34
Retrieve detailed information for a specific user by their ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the user to retrieve. |
No output schema declared.
No examples provided.
get_user_request Get User Request ~49
Retrieve details for a specific user request by its ID. Returns the complete request information including status, content, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the user request to retrieve. |
No output schema declared.
No examples provided.
initiate_file_upload Initiate File Upload ~146
Initiate a file upload by specifying the target path, total file size, and number of parts. Optionally create parent directories and configure multipart upload parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| mkdir_parents | boolean | – | Whether to automatically create any missing parent directories in the path hierarchy. |
| parts | string | – | The number of parts to divide the file into for multipart upload. Determines parallelization strategy for the upload. |
| path | string | yes | The file path where the upload will be stored. Can be a new file or an existing file for append/restart operations. |
| size | string | – | The total file size in bytes, including any existing bytes if appending to or restarting an existing file. |
No output schema declared.
No examples provided.
list_action_notification_export_results List Action Notification Export Results ~92
Retrieve a paginated list of results from a specific action notification export. Use the export ID to filter results and control pagination with per_page.
| Name | Type | Req | Description |
|---|---|---|---|
| action_notification_export_id | string | yes | The unique identifier of the action notification export whose results you want to retrieve. |
| per_page | string | – | Maximum number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
No output schema declared.
No examples provided.
list_api_keys List API Keys ~91
Retrieve a paginated list of API keys with optional sorting by expiration date. Use this to view all API keys associated with your account.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of API keys to return per page. Recommended to use 1,000 or less for optimal performance. |
| sort_by | object | – | Sort the results by a specified field in ascending or descending order. Supports sorting by expiration date. |
No output schema declared.
No examples provided.
list_api_keys_current_user List API Keys for Current User ~99
Retrieve a paginated list of API keys for the authenticated user. Supports sorting by expiration date and customizable page size.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of API keys to return per page. Recommended to use 1,000 or less for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Supports sorting by expiration date (e.g., sort_by[expires_at]=desc). |
No output schema declared.
No examples provided.
list_api_keys_for_user List API Keys for User ~124
Retrieve a paginated list of API keys for a user. Use user_id `0` to list keys for the current session's user.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Maximum 10,000; 1,000 or less is recommended. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Valid field: `expires_at`. |
| user_id | string | yes | The user ID whose API keys to retrieve. Use `0` to operate on the current session's user. |
No output schema declared.
No examples provided.
list_api_keys_site List Site API Keys ~87
Retrieve a paginated list of API keys for your site. Optionally sort and filter results to manage your API credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Supports sorting by expiration date. |
No output schema declared.
No examples provided.
list_apps List Apps ~131
Retrieve a paginated list of all apps with optional sorting capabilities. Use pagination parameters to control result size and sorting to organize results by name or app type.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, though the API supports up to 10,000 records per page. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Valid sortable fields are `name` and `app_type`. Specify the field name as the key and the direction (asc or desc) as the value. |
No output schema declared.
No examples provided.
list_as2_incoming_messages List AS2 Incoming Messages ~133
Retrieve a list of incoming AS2 messages, optionally filtered by AS2 partner and sorted by specified fields. Supports pagination for managing large result sets.
| Name | Type | Req | Description |
|---|---|---|---|
| as2_partner_id | string | – | Filter messages by a specific AS2 partner ID. When provided, only messages from that partner will be returned. |
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Valid fields are `created_at` and `as2_partner_id`. |
No output schema declared.
No examples provided.
list_as2_outgoing_messages List AS2 Outgoing Messages ~133
Retrieve a list of outgoing AS2 messages, optionally filtered by AS2 partner and sorted by specified fields. Useful for monitoring message delivery status and history.
| Name | Type | Req | Description |
|---|---|---|---|
| as2_partner_id | string | – | Filter results to messages associated with a specific AS2 partner. If omitted, returns messages from all partners. |
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Supported fields are `created_at` and `as2_partner_id`. |
No output schema declared.
No examples provided.
list_as2_partners List AS2 Partners ~73
Retrieve a paginated list of AS2 partners configured in the system. Use the per_page parameter to control result set size.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, with a maximum of 10,000. |
No output schema declared.
No examples provided.
list_as2_stations List AS2 Stations ~73
Retrieve a paginated list of AS2 stations. Use the per_page parameter to control the number of records returned per page.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, with a maximum of 10,000. |
No output schema declared.
No examples provided.
list_automation_runs List Automation Runs ~115
Retrieve a paginated list of automation runs for a specific automation. Filter, sort, and control pagination to find the runs you need.
| Name | Type | Req | Description |
|---|---|---|---|
| automation_id | string | yes | The ID of the automation whose runs you want to list. |
| per_page | string | – | Maximum number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Supported fields are `created_at` and `status`. |
No output schema declared.
No examples provided.
list_automations List Automations ~145
Retrieve a paginated list of automations with optional filtering and sorting. Use this to view all automations in your account, including deleted ones if needed.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of automation records to return per page. Recommended to use 1,000 or less for optimal performance, though up to 10,000 is supported. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Valid sortable fields are: automation, disabled, last_modified_at, or name. |
| with_deleted | boolean | – | Include deleted automations in the results. Set to true to show all automations including those that have been deleted. |
No output schema declared.
No examples provided.
What is the com.mcparmory/files-com MCP server?
com.mcparmory/files-com is an MCP server listed in the public MCP registry as com.mcparmory/files-com. Manage files, users, and automated workflows across cloud storage and protocols. This page covers its container image (ghcr.io/mcparmory/files-com:1.0.3).
Is the com.mcparmory/files-com MCP server safe to use?
com.mcparmory/files-com scores 50 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/files-com MCP server expose?
com.mcparmory/files-com exposes 197 tools: list_action_notification_export_results, export_action_notifications, get_action_notification_export, retry_webhook_failure, get_current_api_key, and 192 more. Their descriptions and schemas cost roughly 23,890 tokens of context every time the server is loaded.
Is the com.mcparmory/files-com MCP server still maintained?
com.mcparmory/files-com 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.