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 →
add_file_comment_reaction Add File Comment Reaction ~78
Add an emoji reaction to a file comment. This allows users to express feedback or acknowledgment on specific comments within a file.
| Name | Type | Req | Description |
|---|---|---|---|
| emoji | string | yes | The emoji character or emoji code to use as the reaction on the file comment. |
| file_comment_id | string | yes | The unique identifier of the file comment to attach the reaction to. |
No output schema declared.
No examples provided.
add_public_key Add Public Key ~82
Add a new SSH public key to your account for authentication purposes. Each key requires a descriptive title for easy identification.
| Name | Type | Req | Description |
|---|---|---|---|
| public_key | string | yes | The complete SSH public key content (typically starts with 'ssh-rsa', 'ssh-ed25519', or similar algorithm identifier). |
| title | string | yes | A descriptive label to identify this key within your account. |
No output schema declared.
No examples provided.
add_user_to_group Add User to Group ~97
Add a user to a group with optional administrator privileges. The user will gain access to all group resources based on their assigned role.
| Name | Type | Req | Description |
|---|---|---|---|
| admin | boolean | – | Grant group administrator privileges to the user, allowing them to manage group membership and settings. |
| group_id | string | yes | The ID of the group to which the user will be added. |
| user_id | string | yes | The ID of the user to add to the group. |
No output schema declared.
No examples provided.
copy_file Copy File ~82
Copy a file or folder to a specified destination. Optionally copy only the directory structure without file contents.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | The destination path where the file or folder will be copied to. |
| path | string | yes | The file or folder path to copy from. |
| structure | boolean | – | If true, copy only the directory structure without copying file contents. |
No output schema declared.
No examples provided.
create_api_key Create API Key ~184
Create a new API key for programmatic access to the API. Configure the key's name, expiration date, description, and permission level to control its capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A user-supplied description to help identify the purpose or context of this API key. |
| expires_at | string | – | The date and time when this API key will automatically expire and become invalid. Specify in ISO 8601 format. |
| name | string | – | An internal name for this API key for your own reference and organization. |
| permission_set | string | – | The permission level for this API key. `full` grants complete API access, `desktop_app` restricts to file and share link operations, `sync_app` for sync functionality, `office_integration` for office… |
No output schema declared.
No examples provided.
create_api_key_admin Create API Key for User ~198
Create a new API key for the specified user with configurable permissions and optional expiration. Use user_id `0` to create a key for the current session's user.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional user-supplied description to help identify the purpose or context of this API key. |
| expires_at | string | – | Optional expiration date and time for the API key in ISO 8601 format. After this date, the key will no longer be valid. |
| name | string | – | Optional internal name for the API key for your own reference and organization. |
| permission_set | string | – | Permission level for this API key. `full` grants all permissions, `desktop_app` restricts to file and share link operations, and other sets provide specialized access for specific applications. |
| user_id | string | yes | The user ID for which to create the API key. Use `0` to create a key for the current authenticated user. |
No output schema declared.
No examples provided.
create_api_key_site Create Site API Key ~161
Create a new API key for authenticating requests to the Files.com. Configure the key's name, expiration date, description, and permission level to control its access scope.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A user-supplied description to help identify the purpose or context of this API key. |
| expires_at | string | – | The date and time when this API key will automatically expire and become invalid. Specified in ISO 8601 format. |
| name | string | – | An internal name for this API key to help you identify and manage it. |
| permission_set | string | – | The permission level for this API key, controlling which operations it can perform. Desktop app keys are limited to file and share link operations, while full keys have unrestricted access. |
No output schema declared.
No examples provided.
create_api_key_user Create API Key ~163
Create a new API key for programmatic access to your account. Configure the key's name, permissions, expiration date, and optional description.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional user-supplied description to help identify the purpose or context of this API key. |
| expires_at | string | – | Optional expiration date and time for this API key in ISO 8601 format. After this date, the key will no longer be valid for authentication. |
| name | string | – | Optional internal name for this API key to help you identify and manage it. |
| permission_set | string | – | Permission level for this API key. Controls which operations and resources the key can access. Desktop app keys are limited to file and share link operations, while full keys have unrestricted access. |
No output schema declared.
No examples provided.
create_as2_partner Create AS2 Partner ~159
Create a new AS2 partner configuration for secure EDI communication. Requires an associated AS2 station and partner identification details including certificates and response URI.
| Name | Type | Req | Description |
|---|---|---|---|
| as2_station_id | string | yes | The ID of the AS2 station that this partner will be associated with. |
| name | string | yes | The AS2 identifier name for this partner, used in AS2 message headers for partner identification. |
| public_certificate | string | yes | The public certificate in PEM format used to verify signatures and encrypt messages from this partner. |
| server_certificate | string | – | The remote server's certificate for validating secure connections to the partner's AS2 endpoint. |
| uri | string | yes | The base URL where AS2 responses and acknowledgments will be sent to this partner. |
No output schema declared.
No examples provided.
create_as2_station Create AS2 Station ~150
Create a new AS2 station for secure EDI communication. Requires cryptographic credentials including a private key and public certificate for message signing and encryption.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name identifier for the AS2 station. Used to reference this station in AS2 communications and configurations. |
| private_key | string | yes | The private key used for signing outbound AS2 messages and decrypting inbound messages. Must be in PEM format. |
| private_key_password | string | – | Optional password protecting the private key. Required if the private key is encrypted. |
| public_certificate | string | yes | The public certificate corresponding to the private key, used for message authentication and encryption verification. Must be in PEM or DER format. |
No output schema declared.
No examples provided.
create_bundle Create Bundle ~519
Create a shareable bundle that packages files and folders with configurable access controls, expiration, and submission handling. Bundles can require registration, limit access to specific recipients, and apply watermarks to previewed items.
| Name | Type | Req | Description |
|---|---|---|---|
| clickwrap_id | string | – | ID of the clickwrap agreement to display to bundle recipients before access is granted. |
| code | string | – | Custom code that forms the public-facing URL slug for this bundle. Must be unique and URL-safe. |
| description | string | – | Public-facing description displayed to bundle recipients explaining the bundle's contents and purpose. |
| dont_separate_submissions_by_folder | boolean | – | When enabled, prevents automatic creation of subfolders for uploads from different users. Use with caution due to security implications when accepting anonymous uploads from multiple sources. |
| expires_at | string | – | Date and time when the bundle automatically expires and becomes inaccessible. Specified in ISO 8601 format. |
| form_field_set_id | string | – | ID of the form field set to associate with this bundle. Captured data from form submissions will be stored with uploads. |
| inbox_id | string | – | ID of the inbox where bundle submissions will be delivered. If not specified, submissions go to the default location. |
| max_uses | string | – | Maximum number of times the bundle can be accessed before it becomes unavailable. Unlimited if not specified. |
| note | string | – | Internal note for bundle management purposes. Not visible to bundle recipients. |
| path_template | string | – | Template for organizing submission subfolders using uploader metadata. Supports placeholders for name, email, IP address, company, and custom form fields using double-brace syntax. |
| paths | array | yes | List of file and folder paths to include in this bundle. Paths are processed in the order specified. |
| permissions | string | – | Access level granted to recipients for folders within this bundle. Controls whether recipients can view, download, upload, or modify contents. |
| require_registration | boolean | – | When enabled, recipients must provide their name and email address before accessing the bundle. |
| require_share_recipient | boolean | – | When enabled, only recipients who received an invitation email through the Files.com interface can access the bundle. |
| send_email_receipt_to_uploader | boolean | – | When enabled, an email receipt confirming successful upload is sent to the uploader. Only applicable for bundles with write permissions. |
| watermark_attachment_file | string | – | Base64-encoded file content for upload. Image file to apply as a watermark overlay on all bundle item previews. Uploaded as binary file data. |
No output schema declared.
No examples provided.
create_clickwrap Create Clickwrap ~194
Create a new clickwrap agreement that users must accept. Clickwraps can be configured for use with bundles, inboxes, and user registrations.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Body text of Clickwrap (supports Markdown formatting). |
| name | string | – | Display name for this clickwrap agreement, used when presenting multiple clickwrap options to users. |
| use_with_bundles | string | – | Determines how this clickwrap applies to bundle operations: 'none' disables it, 'available' makes it optional, 'require' makes acceptance mandatory. |
| use_with_inboxes | string | – | Determines how this clickwrap applies to inbox operations: 'none' disables it, 'available' makes it optional, 'require' makes acceptance mandatory. |
| use_with_users | string | – | Determines how this clickwrap applies to user registration via email invitation: 'none' disables it, 'require' makes acceptance mandatory during password setup. |
No output schema declared.
No examples provided.
create_external_event Create External Event ~65
Create a new external event with a specified status. This operation allows you to log events from external systems with their current processing state.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The content or payload of the event being created. |
| status | string | yes | The current processing state of the event. |
No output schema declared.
No examples provided.
create_folder Create Folder ~90
Create a new folder at the specified path. Optionally create parent directories and set a custom modification time.
| Name | Type | Req | Description |
|---|---|---|---|
| mkdir_parents | boolean | – | Whether to automatically create any missing parent directories in the path. |
| path | string | yes | The file system path where the folder should be created. |
| provided_mtime | string | – | Custom modification timestamp for the created folder in ISO 8601 date-time format. |
No output schema declared.
No examples provided.
create_form_field_set Create Form Field Set ~96
Create a new form field set with a title and optional collection of form fields. Form field sets organize related fields for structured data collection.
| Name | Type | Req | Description |
|---|---|---|---|
| form_fields | array | – | Array of form fields to include in this set. Order is preserved and determines field display sequence. Each item should represent a field configuration. |
| title | string | – | Display title for the form field set. Used to identify and label the set in user interfaces. |
No output schema declared.
No examples provided.
create_group Create Group ~135
Create a new group with specified members and administrators. Optionally include group name, notes, and assign users and admins during creation.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_ids | string | – | Comma-delimited list of user IDs to designate as group administrators. Administrators have elevated permissions within the group. |
| name | string | – | The name of the group. Used for identification and display purposes. |
| notes | string | – | Optional notes or description for the group. Useful for documenting the group's purpose or additional context. |
| user_ids | string | – | Comma-delimited list of user IDs to add as members of the group. Order is not significant. |
No output schema declared.
No examples provided.
create_group_user Create Group User ~744
Create a new user within a specified group with configurable authentication, permissions, and access settings.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_ips | string | – | Newline-delimited list of IP addresses permitted to access this user's account. |
| announcements_read | boolean | – | Whether the user has read all announcements displayed in the UI. |
| authenticate_until | string | – | Date and time at which the user account will be automatically deactivated. |
| authentication_method | string | – | The authentication method used for this user's login credentials. |
| billing_permission | boolean | – | Whether this user can perform operations on account settings, payments, and invoices. |
| bypass_inactive_disable | boolean | – | Whether this user is exempt from automatic deactivation due to inactivity. |
| bypass_site_allowed_ips | boolean | – | Whether this user can bypass site-wide IP blacklist restrictions. |
| company | string | – | The user's company or organization name. |
| dav_permission | boolean | – | Whether the user can connect and authenticate via WebDAV protocol. |
| disabled | boolean | – | Whether the user account is disabled. Disabled users cannot log in and do not consume billing seats. |
| string | – | The user's email address. | |
| ftp_permission | boolean | – | Whether the user can access files and folders via FTP or FTPS protocols. |
| grant_permission | string | – | Permission level to grant on the user's root folder. Options include full access, read-only, write, list, or history. |
| group_id | string | yes | The group ID to associate with the new user. |
| header_text | string | – | Custom text message displayed to the user in the UI header. |
| language | string | – | The user's preferred language for the UI. |
| name | string | – | The user's full name. |
| notes | string | – | Internal notes or comments about the user for administrative reference. |
| notification_daily_send_time | string | – | The hour of the day (0-23) when daily notifications should be sent to the user. |
| office_integration_enabled | boolean | – | Whether to enable integration with Microsoft Office for the web applications. |
| password_validity_days | string | – | Number of days a user can use the same password before being required to change it. |
| receive_admin_alerts | boolean | – | Whether the user receives administrative alerts such as certificate expiration and usage overages. |
| require_2fa | string | – | Whether two-factor authentication is required for this user's login. |
| require_password_change | boolean | – | Whether the user must change their password on the next login. |
| restapi_permission | boolean | – | Whether the user can authenticate and access the REST API. |
| self_managed | boolean | – | Whether this user manages their own credentials or is a shared/bot account with managed credentials. |
| sftp_permission | boolean | – | Whether the user can access files and folders via SFTP protocol. |
| site_admin | boolean | – | Whether the user has administrator privileges for this site. |
| skip_welcome_screen | boolean | – | Whether to skip displaying the welcome screen to the user on first login. |
| ssl_required | string | – | Whether SSL/TLS encryption is required for this user's connections. |
| sso_strategy_id | string | – | The ID of the SSO (Single Sign On) strategy to use for this user's authentication. |
| subscribe_to_newsletter | boolean | – | Whether the user is subscribed to receive newsletter communications. |
| time_zone | string | – | The user's time zone for scheduling and time-based operations. |
| user_root | string | – | Root folder path for FTP access and optionally SFTP if configured site-wide. Not used for API, desktop, or web interface access. |
| username | string | – | User's username |
No output schema declared.
No examples provided.
create_history_export Create History Export ~489
Initiate a history export with optional filtering by date range, user, action type, interface, and target object. Returns an export job that can be monitored for completion.
| Name | Type | Req | Description |
|---|---|---|---|
| end_at | string | – | End date and time for the export range (inclusive). Use ISO 8601 format. |
| query_action | string | – | Filter exported history records by action type performed (e.g., file operations, user management, authentication events). |
| query_destination | string | – | Filter results to include only file move operations with this destination path. |
| query_failure_type | string | – | When filtering for login failures, restrict results to failures of this specific type. |
| query_file_id | string | – | Filter results to include only actions related to the specified file ID. |
| query_folder | string | – | Filter results to include only actions on files or folders within this folder path. |
| query_interface | string | – | Filter exported history records by the interface or protocol used to perform the action. |
| query_ip | string | – | Filter results to include only actions originating from this IP address. |
| query_parent_id | string | – | Filter results to include only actions within the parent folder specified by this folder ID. |
| query_path | string | – | Filter results to include only actions related to this file or folder path. |
| query_src | string | – | Filter results to include only file move operations originating from this source path. |
| query_target_id | string | – | Filter results to include only actions on objects (users, API keys, etc.) matching this target object ID. |
| query_target_name | string | – | Filter results to include only actions on objects (users, groups, etc.) matching this name or username. |
| query_target_permission | string | – | When filtering for permission-related actions, restrict results to permissions at this access level. |
| query_target_permission_set | string | – | When filtering for API key actions, restrict results to API keys with this permission set. |
| query_target_platform | string | – | When filtering for API key actions, restrict results to API keys associated with this platform. |
| query_user_id | string | – | Filter results to include only actions performed by the user with this user ID. |
| query_username | string | – | Filter results to include only actions performed by this username. |
| start_at | string | – | Start date and time for the export range (inclusive). Use ISO 8601 format. |
No output schema declared.
No examples provided.
create_message Create Message ~79
Create a new message attached to a specific project. Messages can be used for project communication and collaboration.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The content of the message to be created. |
| project_id | string | yes | The unique identifier of the project to which this message should be attached. |
| subject | string | yes | The subject line or title for the message. |
No output schema declared.
No examples provided.
create_notification Create Notification ~437
Create a notification rule that triggers on specified file system actions within a path. Configure which actions trigger notifications, who performs them, and how notifications are aggregated.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | – | The ID of the group to notify. Provide `user_id`, `username` or `group_id`. |
| message | string | – | Custom message to include in notification emails sent when the rule is triggered. |
| notify_on_copy | boolean | – | When enabled, copying or moving resources into this path will trigger a notification in addition to upload events. |
| notify_on_delete | boolean | – | When enabled, deleting files from this path will trigger a notification. |
| notify_on_download | boolean | – | When enabled, downloading files from this path will trigger a notification. |
| notify_on_move | boolean | – | When enabled, moving files to this path will trigger a notification. |
| notify_on_upload | boolean | – | When enabled, uploading new files to this path will trigger a notification. |
| notify_user_actions | boolean | – | When enabled, actions initiated by the user account itself will still result in a notification. |
| path | string | – | Path |
| recursive | boolean | – | When enabled, notifications will be triggered for actions in all subfolders under this path. |
| send_interval | string | – | The time interval over which notifications are aggregated before being sent. Longer intervals batch multiple events into a single notification. |
| trigger_by_share_recipients | boolean | – | When enabled, notifications will be triggered for actions performed by users who have access through a share link or shared folder. |
| triggering_filenames | array | – | Array of filename patterns to match against the action path. Supports wildcards to filter which files trigger notifications. Patterns are evaluated in order. |
| triggering_group_ids | array | – | Array of group IDs. When specified, only actions performed by members of these groups will trigger notifications. |
| triggering_user_ids | array | – | Array of user IDs. When specified, only actions performed by these users will trigger notifications. |
| user_id | string | – | The id of the user to notify. Provide `user_id`, `username` or `group_id`. |
No output schema declared.
No examples provided.
create_permission Create Permission ~104
Create a new permission with specified access level and optional recursive application to subfolders.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | – | Group ID |
| path | string | – | Folder path |
| permission | string | – | The access level type to assign. Determines what actions are permitted. |
| recursive | boolean | – | Whether to apply this permission to all subfolders in addition to the target folder. |
| user_id | string | – | User ID. Provide `username` or `user_id` |
No output schema declared.
No examples provided.
create_project Create Project ~59
Create a new project with specified global access permissions. Global access determines who can view or modify the project across your organization.
| Name | Type | Req | Description |
|---|---|---|---|
| global_access | string | yes | Sets the global access level for the project, controlling visibility and permissions for all users in the organization. |
No output schema declared.
No examples provided.
create_public_key Create Public Key ~86
Create a new SSH public key for authentication. The key is stored with an internal reference title for easy identification.
| Name | Type | Req | Description |
|---|---|---|---|
| public_key | string | yes | The complete SSH public key content in standard format (typically starting with ssh-rsa, ssh-ed25519, or similar). |
| title | string | yes | A descriptive name or label for this public key to help identify it among multiple keys. |
No output schema declared.
No examples provided.
create_public_key_for_user Create Public Key for User ~126
Create a new SSH public key for a user account. The key can be associated with the current session's user by providing a user_id of 0.
| Name | Type | Req | Description |
|---|---|---|---|
| public_key | string | yes | The complete SSH public key content (typically starting with ssh-rsa, ssh-ed25519, or similar). |
| title | string | yes | A descriptive label for this public key to help identify it among multiple keys. |
| user_id | string | yes | The ID of the user to create the public key for. Use 0 to create a key for the current session's authenticated user. |
No output schema declared.
No examples provided.
create_remote_server Create Remote Server ~615
Create a remote server configuration for cloud storage or file transfer integration. Supports multiple storage backends including AWS S3, Azure, Google Cloud Storage, and various other cloud providers.
| Name | Type | Req | Description |
|---|---|---|---|
| aws | object | – | AWS S3 connection settings (access key, secret key) |
| azure_blob_storage | object | – | Azure Blob Storage connection settings |
| azure_files_storage | object | – | Azure File Storage connection settings |
| backblaze_b2 | object | – | Backblaze B2 connection settings |
| enable_dedicated_ips | boolean | – | When enabled, restricts remote server connections to dedicated IP addresses only. |
| filebase | object | – | Filebase connection settings |
| files_agent_permission_set | string | – | File permissions level for the files agent: read_only allows downloads only, write_only allows uploads only, read_write allows both operations. |
| files_agent_root | string | – | Local root directory path where the files agent will access files. |
| google_cloud_storage | object | – | Google Cloud Storage connection settings |
| hostname | string | – | Hostname or IP address |
| max_connections | string | – | Maximum number of parallel connections to the remote server. Ignored for S3 connections which parallelize automatically. |
| name | string | – | Internal display name for this remote server configuration. |
| one_drive_account_type | string | – | OneDrive account type: personal for individual accounts or business_other for business/organizational accounts. |
| pin_to_site_region | boolean | – | When enabled, all communications with this remote server route through the primary region of the site. Can be overridden by site-wide settings. |
| port | string | – | Port for remote server. Not needed for S3. |
| private_key | string | – | Private key for SFTP or other key-based authentication methods. |
| private_key_passphrase | string | – | Passphrase to decrypt the private key if it is encrypted. |
| rackspace | object | – | Rackspace Cloud Files connection settings |
| s3_bucket | string | – | AWS S3 bucket name where files will be stored. |
| s3_compatible | object | – | S3-compatible storage connection settings |
| s3_region | string | – | AWS region code where the S3 bucket is located. |
| server_certificate | string | – | SSL certificate validation mode: require_match enforces exact certificate matching, allow_any accepts any valid certificate. |
| server_host_key | string | – | Remote server SSH host key in OpenSSH format (as would appear in ~/.ssh/known_hosts). When provided, the server's host key must match exactly. |
| server_type | string | – | Type of remote server to configure. Determines which authentication credentials and configuration parameters are required. |
| ssl | string | – | SSL/TLS requirement level: if_available uses SSL when supported, require enforces SSL, require_implicit uses implicit SSL, never disables SSL. |
| ssl_certificate | string | – | SSL client certificate for mutual TLS authentication with the remote server. |
| wasabi | object | – | Wasabi storage connection settings |
No output schema declared.
No examples provided.
create_sftp_host_key Create SFTP Host Key ~92
Create a new SFTP host key for secure file transfer authentication. The host key consists of a friendly name and the associated private key data.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | A user-friendly name to identify this SFTP host key for reference and management purposes. |
| private_key | string | – | The private key data in PEM format used for SFTP host authentication. This should be the complete private key content. |
No output schema declared.
No examples provided.
create_user Create User ~822
Create a new user account with configurable authentication, permissions, and security settings. Supports multiple authentication methods and granular access control across protocols (FTP, SFTP, WebDAV, REST API).
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_ips | string | – | Comma-separated or newline-delimited list of IP addresses permitted to access this user account. Leave empty to allow all IPs. |
| announcements_read | boolean | – | Indicates whether the user has acknowledged all announcements displayed in the UI. |
| authenticate_until | string | – | Date and time after which the user account will be automatically deactivated. Useful for temporary or contract-based access. |
| authentication_method | string | – | Authentication mechanism used for this user. Determines how credentials are validated and managed. |
| billing_permission | boolean | – | Grant permission to manage account operations, payments, and invoices. Restricted to trusted users only. |
| bypass_inactive_disable | boolean | – | Prevent this user from being automatically disabled due to inactivity, overriding site-wide inactivity policies. |
| bypass_site_allowed_ips | boolean | – | Allow this user to bypass site-wide IP address blacklists and restrictions. |
| company | string | – | User's organization or company name for identification and organizational purposes. |
| dav_permission | boolean | – | Enable WebDAV protocol access for this user. |
| disabled | boolean | – | Disable user account. Disabled users cannot log in and do not consume billing seats. Can be automatically applied after inactivity. |
| string | – | User's email address used for login, notifications, and account recovery. | |
| ftp_permission | boolean | – | Enable FTP/FTPS protocol access for this user. |
| grant_permission | string | – | Default permission level for the user's root folder. Options include full access, read-only, write, list, or history viewing. |
| header_text | string | – | Custom message displayed in the UI header for this user. Useful for notifications or instructions. |
| language | string | – | User's preferred language for the UI interface. |
| name | string | – | User's full name for display and identification purposes. |
| notes | string | – | Internal notes or comments about the user for administrative reference. Not visible to the user. |
| notification_daily_send_time | string | – | Hour of day (0-23) when daily notification digests should be sent to this user. |
| office_integration_enabled | boolean | – | Enable integration with Microsoft Office for the web applications. |
| password_validity_days | string | – | Number of days before the user must change their password. Enforces periodic password rotation. |
| receive_admin_alerts | boolean | – | Send administrative alerts to this user, including certificate expiration warnings and account overages. |
| require_2fa | string | – | Two-factor authentication requirement for this user. Can override system-wide settings. |
| require_password_change | boolean | – | Require the user to change their password on the next login attempt. |
| restapi_permission | boolean | – | Enable REST API access for this user. |
| self_managed | boolean | – | Indicate whether the user manages their own credentials or is a shared/bot account with managed credentials. |
| sftp_permission | boolean | – | Enable SFTP protocol access for this user. |
| site_admin | boolean | – | Grant site administrator privileges to this user, allowing management of other users and system settings. |
| skip_welcome_screen | boolean | – | Skip the welcome/onboarding screen on first login to the UI. |
| ssl_required | string | – | SSL/TLS encryption requirement for this user's connections. Can override system-wide settings. |
| sso_strategy_id | string | – | ID of the SSO (Single Sign On) strategy to use for this user's authentication. |
| subscribe_to_newsletter | boolean | – | Subscribe this user to the system newsletter for updates and announcements. |
| time_zone | string | – | User's time zone for scheduling notifications and displaying timestamps in the UI. |
| user_root | string | – | Root folder path for FTP access and optionally SFTP (if configured site-wide). Does not apply to API, desktop, or web interface access. |
| username | string | – | User's username |
No output schema declared.
No examples provided.
create_user_request Create User Request ~97
Create a new user request with details about a specific user. This operation registers a request associated with the provided user's email and name.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | yes | Detailed description or content of the user request, providing context about what is being requested. |
| string | yes | Email address of the user associated with this request. Used for identification and communication purposes. | |
| name | string | yes | Full name of the user associated with this request. |
No output schema declared.
No examples provided.
delete_api_key Delete API Key ~52
Permanently delete an API key by its ID. This action cannot be undone and will immediately revoke access for any integrations using this key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the API key to delete. |
No output schema declared.
No examples provided.
delete_as2_partner Delete AS2 Partner ~47
Delete an AS2 partner configuration. This operation permanently removes the specified AS2 partner from the system.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the AS2 partner to delete. |
No output schema declared.
No examples provided.
delete_as2_station Delete AS2 Station ~50
Delete an AS2 station by its ID. This operation permanently removes the AS2 station configuration and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the AS2 station to delete. |
No output schema declared.
No examples provided.
delete_automation Delete Automation ~39
Permanently delete an automation by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the automation to delete. |
No output schema declared.
No examples provided.
delete_behavior Delete Behavior ~38
Permanently delete a behavior by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the behavior to delete. |
No output schema declared.
No examples provided.
delete_bundle Delete Bundle ~38
Permanently delete a bundle by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the bundle to delete. |
No output schema declared.
No examples provided.
delete_bundle_notification Delete Bundle Notification ~45
Delete a specific bundle notification by its ID. This operation permanently removes the bundle notification from the system.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the bundle notification to delete. |
No output schema declared.
No examples provided.
delete_clickwrap Delete Clickwrap ~41
Permanently delete a clickwrap by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the clickwrap to delete. |
No output schema declared.
No examples provided.
delete_file Delete File ~86
Delete a file or folder at the specified path. Use the recursive parameter to delete non-empty folders; otherwise, deletion will fail if the folder contains items.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The file system path to the file or folder to delete. |
| recursive | boolean | – | When true, recursively deletes folders and their contents. When false, deletion fails if the target folder is not empty. |
No output schema declared.
No examples provided.
delete_file_comment Delete File Comment ~44
Delete a specific file comment by its ID. This operation permanently removes the comment from the file.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the file comment to delete. |
No output schema declared.
No examples provided.
delete_form_field_set Delete Form Field Set ~50
Delete a form field set by its ID. This operation permanently removes the specified form field set and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the form field set to delete. |
No output schema declared.
No examples provided.
delete_group Delete Group ~38
Permanently delete a group by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the group to delete. |
No output schema declared.
No examples provided.
delete_message Delete Message ~38
Permanently delete a message by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the message to delete. |
No output schema declared.
No examples provided.
delete_message_comment Delete Message Comment ~45
Delete a specific message comment by its ID. This operation permanently removes the comment from the message thread.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the message comment to delete. |
No output schema declared.
No examples provided.
delete_notification Delete Notification ~38
Permanently delete a notification by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the notification to delete. |
No output schema declared.
No examples provided.
delete_permission Delete Permission ~41
Delete a permission by its ID. This operation permanently removes the specified permission from the system.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the permission to delete. |
No output schema declared.
No examples provided.
delete_project Delete Project ~38
Permanently delete a project by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the project to delete. |
No output schema declared.
No examples provided.
delete_public_key Delete Public Key ~41
Permanently delete a public key by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the public key to delete. |
No output schema declared.
No examples provided.
delete_remote_server Delete Remote Server ~41
Permanently delete a remote server by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the remote server to delete. |
No output schema declared.
No examples provided.
delete_request Delete Request ~41
Delete a specific request by its ID. This operation permanently removes the request from the system.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the request to delete. |
No output schema declared.
No examples provided.
delete_sftp_host_key Delete SFTP Host Key ~51
Delete an SFTP host key by its ID. This operation permanently removes the specified host key from the system.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the SFTP host key to delete. |
No output schema declared.
No examples provided.
delete_style Delete Style ~49
Delete a style by its path. This operation permanently removes the style from the system.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The path identifier of the style to delete. This uniquely identifies which style resource to remove. |
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.