com.mcparmory/files-com
OCI · GHCR.IO/MCPARMORY/FILES-COM:1.0.3 · 2 COMPONENTS
Manage files, users, and automated workflows across cloud storage and protocols
Available components
Last scanned (15 hours ago)
Scores higher than 85% of OCI servers
Category Documents and Files
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
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.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 177 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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.
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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 Oct 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.
- 14 Oct 26 −3
- Stability: pass → 0.80 functional
- 13 Oct 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed 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 →
list_usage_snapshots_daily List Daily Usage Snapshots ~123
Retrieve a paginated list of daily usage snapshots. Results can be sorted by date or snapshot ID to track usage patterns over time.
| 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 records per page. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Supported fields are `date` and `usage_snapshot_id`. Specify as an object with field name as key and sort direction as value. |
No output schema declared.
No examples provided.
list_user_groups List User Groups ~76
Retrieve a paginated list of users belonging to groups. Use the per_page parameter to control result set size for optimal performance.
| 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. |
No output schema declared.
No examples provided.
list_user_groups_2 List User Groups ~85
Retrieve all groups that a specific user belongs to. Supports pagination to handle large result sets.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance; maximum allowed is 10,000. |
| user_id | string | yes | The unique identifier of the user whose group memberships should be retrieved. |
No output schema declared.
No examples provided.
list_user_history List User History ~203
Retrieve a paginated list of history records for a specific user, with optional filtering by date range and customizable sorting and display format.
| Name | Type | Req | Description |
|---|---|---|---|
| display | string | – | Control the detail level of returned records. Use `full` for complete details or `parent` for parent-only information. |
| end_at | string | – | Filter to exclude history entries created after this date and time. Leave blank to include all later entries. |
| 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. Use field names `user_id` or `created_at` with direction indicators. |
| start_at | string | – | Filter to exclude history entries created before this date and time. Leave blank to include all earlier entries. |
| user_id | string | yes | The unique identifier of the user whose history records should be retrieved. |
No output schema declared.
No examples provided.
list_user_permissions List User Permissions ~153
Retrieve a list of permissions for a specific user, with optional filtering by group inheritance and sorting capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| include_groups | boolean | – | When enabled, includes permissions inherited from the user's group memberships in addition to directly assigned permissions. |
| per_page | string | – | Number of permission records 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. Valid sortable fields are group_id, path, user_id, or permission. |
| user_id | string | yes | The user ID to retrieve permissions for. Note: This parameter is deprecated; use the filter[user_id] query parameter instead for new implementations. |
No output schema declared.
No examples provided.
list_users List Users ~272
Retrieve a paginated list of users with optional filtering by ID, username, email, notes, or administrative and security settings.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | string | – | Filter results by one or more user IDs using comma-separated values. |
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
| qadmin | string | – | Filter results to include only administrative users when set to true. |
| qallowed_ips | string | – | Filter results to include only users with custom allowed IP address restrictions configured. |
| qemail | string | – | Filter results to users whose email address matches the provided value. |
| qnotes | string | – | Filter results to users whose notes field matches the provided value. |
| qpassword_validity_days | string | – | Filter results to include only users with custom password validity days settings configured. |
| qssl_required | string | – | Filter results to include only users with custom SSL requirement settings configured. |
| qusername | string | – | Filter results to users whose username matches the provided value. |
| sort_direction | string | – | Sort direction. Valid values: 'asc' or 'desc' |
| sort_field | string | – | Field to sort by. Valid values: 'path', 'folder', 'user_id', 'created_at' |
No output schema declared.
No examples provided.
move_file Move File ~70
Move a file or folder to a new location. The source path and destination path must both be valid within the file system.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | The destination path where the file or folder should be moved to. |
| path | string | yes | The current path of the file or folder to be moved. |
No output schema declared.
No examples provided.
release_lock Release Lock ~70
Release a lock on a resource by providing its path and token. This removes the lock, allowing other operations to proceed.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The resource path for which the lock should be released. |
| token | string | yes | The unique token that identifies and authorizes the release of this specific lock. |
No output schema declared.
No examples provided.
remove_file_comment_reaction Remove File Comment Reaction ~46
Remove a reaction from a file comment. Deletes the specified file comment reaction by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the file comment reaction to delete. |
No output schema declared.
No examples provided.
remove_group_member Remove Group Member ~72
Remove a user from a group by deleting their membership. This operation revokes the user's access to the group.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The unique identifier of the group from which the user will be removed. |
| user_id | string | yes | The unique identifier of the user to be removed from the group. |
No output schema declared.
No examples provided.
remove_message_comment_reaction Remove Message Comment Reaction ~44
Remove a reaction from a message comment. Deletes the specified reaction by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the message comment reaction to delete. |
No output schema declared.
No examples provided.
remove_message_reaction Remove Message Reaction ~49
Remove a reaction from a message by its reaction ID. This deletes the association between the user and the message reaction.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the message reaction to delete. |
No output schema declared.
No examples provided.
remove_user_from_group Remove User From Group ~98
Remove a user from a group by deleting the group membership record. This operation requires the group user ID along with the group and user IDs for verification.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The unique identifier of the group from which the user will be removed. |
| id | string | yes | The unique identifier of the group user membership record to delete. |
| user_id | string | yes | The unique identifier of the user to remove from the group. |
No output schema declared.
No examples provided.
request_file Request File ~100
Request a file from specified users by destination filename and folder path. Optionally target specific users; if no users are specified, the request is sent broadly.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | The destination filename (without file extension) being requested. |
| path | string | yes | The folder path where the requested file is located. |
| user_ids | string | – | List of user IDs to request the file from. Provide as comma-separated values when sent as a string. |
No output schema declared.
No examples provided.
resend_welcome_email Resend Welcome Email ~57
Resend the welcome email to a user. This operation is useful when the initial welcome email was not received or needs to be sent again.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the user who should receive the welcome email. |
No output schema declared.
No examples provided.
reset_user_2fa Reset User 2FA ~69
Initiate a two-factor authentication reset for a user who has lost access to their existing 2FA methods. This process allows the user to regain account access and reconfigure their authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the user whose 2FA needs to be reset. |
No output schema declared.
No examples provided.
retry_webhook_failure Retry Webhook Failure ~53
Retry a failed action webhook by its failure ID. This operation allows you to re-attempt delivery of a webhook that previously failed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the action webhook failure to retry. |
No output schema declared.
No examples provided.
share_bundle Share Bundle ~63
Send email(s) with a shareable link to a bundle. Optionally include a custom note in the email message.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the bundle to share. |
| note | string | – | Optional custom message to include in the share email. |
No output schema declared.
No examples provided.
share_bundle_with_recipient Share Bundle With Recipient ~154
Share a bundle with a recipient by creating a bundle recipient record. Optionally send a share notification email immediately upon creation.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_id | string | yes | The ID of the bundle to share with the recipient. |
| company | string | – | The company name associated with the recipient. |
| name | string | – | The full name of the recipient. |
| note | string | – | An optional message to include in the share notification email sent to the recipient. |
| recipient | string | yes | The email address of the recipient to share the bundle with. |
| share_after_create | boolean | – | When true, automatically sends a share notification email to the recipient upon creation. When false, the recipient is added without sending an email. |
No output schema declared.
No examples provided.
share_inbox_with_recipient Share Inbox With Recipient ~148
Grant a recipient access to an inbox by sharing it with their email address. Optionally send them a notification email upon creation.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company name associated with the recipient for organizational context. |
| inbox_id | string | yes | The ID of the inbox to be shared with the recipient. |
| name | string | – | Full name of the recipient for identification purposes. |
| note | string | – | Optional message to include in the notification email sent to the recipient. |
| recipient | string | yes | Email address of the recipient who will receive access to the inbox. |
| share_after_create | boolean | – | When true, automatically sends a sharing notification email to the recipient upon creation. |
No output schema declared.
No examples provided.
sync_sso_strategy Sync SSO Strategy ~61
Synchronize provisioning data between the local system and the remote SSO server for the specified strategy. This operation ensures user and group data are up-to-date across both systems.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the SSO strategy to synchronize. |
No output schema declared.
No examples provided.
test_webhook Test Webhook ~186
Execute a test request to a webhook URL to validate connectivity and configuration. Supports custom headers, multiple encoding formats, and optional file payload.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action identifier to include in the test request body. |
| encoding | string | – | HTTP encoding format for the request body: JSON, XML, or RAW (form data). |
| file_as_body | boolean | – | Whether to send file data as the raw request body instead of as a form field. |
| file_form_field | string | – | Form field name to use when sending file data as a named parameter in the POST body. |
| headers | object | – | Custom HTTP headers to include in the test request as key-value pairs. |
| method | string | – | HTTP method for the test request: GET or POST. |
| url | string | yes | The webhook URL endpoint to test. Must be a valid HTTP or HTTPS URL. |
No output schema declared.
No examples provided.
unlock_user Unlock User ~46
Unlock a user account that has been locked due to failed login attempts. This restores the user's ability to authenticate.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the user account to unlock. |
No output schema declared.
No examples provided.
update_api_key_by_id Update API Key ~150
Update an existing API key's configuration including name, description, expiration date, and permission set.
| 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 expire and become invalid. |
| id | string | yes | The unique identifier of the API key to update. |
| name | string | – | An internal name for the API key to help you organize and identify it. |
| permission_set | string | – | The permission set determines what operations this API key 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.
update_as2_partner Update AS2 Partner ~145
Update an AS2 partner's configuration including name, certificates, and response URI. Allows modification of existing AS2 partner settings for secure EDI communication.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the AS2 partner to update. |
| name | string | – | The AS2 partner's display name or identifier. |
| public_certificate | string | – | The public certificate used for verifying signatures and encrypting messages from this AS2 partner. |
| server_certificate | string | – | The remote server's certificate for establishing secure connections and validating the AS2 partner's identity. |
| uri | string | – | The base URL where AS2 responses and acknowledgments should be sent to this partner. |
No output schema declared.
No examples provided.
update_as2_station Update AS2 Station ~109
Update an AS2 station configuration including its name, private key, and public certificate credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the AS2 station to update. |
| name | string | – | The AS2 station name or identifier. |
| private_key | string | – | The private key used for signing AS2 messages. |
| private_key_password | string | – | The password protecting the private key. |
| public_certificate | string | – | The public certificate used for verifying AS2 message signatures. |
No output schema declared.
No examples provided.
update_automation Update Automation ~370
Update an existing automation configuration. Modify automation properties such as schedule, trigger type, associated syncs/users, and behavior settings.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A descriptive label for this automation. |
| destination_folders | array | – | List of destination folder objects with 'folder_path' (required) and optional 'file_path' keys |
| destination_paths | array | – | List of simple destination path strings |
| disabled | boolean | – | When true, prevents this automation from executing. |
| id | string | yes | The unique identifier of the automation to update. |
| interval | string | – | The execution frequency for this automation. Determines how often the automation runs based on calendar intervals. |
| name | string | – | A human-readable name for this automation. |
| schedule_days | array | – | Days of week for the schedule (e.g., 'monday', 'tuesday') |
| schedule_times | array | – | Times in HH:MM format for the schedule |
| schedule_timezone | string | – | Timezone for the schedule (e.g., 'UTC', 'America/New_York') |
| source | string | – | The source path associated with this automation. |
| sync_ids | string | – | Comma-separated list of sync IDs this automation is associated with. |
| trigger | string | – | The mechanism that initiates automation execution. Determines whether the automation runs on a schedule, in response to events, or via external triggers. |
| trigger_actions | array | – | When trigger is set to 'action', specifies which action types activate the automation. Valid actions include create, read, update, destroy, move, and copy operations. |
| user_ids | string | – | Comma-separated list of user IDs this automation is associated with. |
| value | object | – | A structured object containing automation type-specific configuration parameters and settings. |
No output schema declared.
No examples provided.
update_bundle Update Bundle ~456
Update an existing bundle's configuration, including access controls, expiration, paths, and metadata. Allows modification of sharing permissions, recipient requirements, and submission handling.
| Name | Type | Req | Description |
|---|---|---|---|
| clickwrap_id | string | – | The clickwrap agreement to associate with this bundle for user acceptance. |
| code | string | – | A unique code that forms the final segment of the bundle's public URL. |
| description | string | – | A public-facing description displayed to bundle users. |
| dont_separate_submissions_by_folder | boolean | – | When enabled, prevents automatic creation of subfolders for uploads from different users. Use with caution due to potential security implications with anonymous multi-user uploads. |
| expires_at | string | – | The date and time when the bundle expires and becomes inaccessible. Use ISO 8601 format. |
| form_field_set_id | string | – | The form field set to associate with this bundle for collecting uploader information. |
| id | string | yes | The unique identifier of the bundle to update. |
| inbox_id | string | – | The inbox to associate with this bundle for organizing submissions. |
| max_uses | string | – | The maximum number of times the bundle can be accessed before becoming unavailable. |
| note | string | – | An internal note for bundle administrators, not visible to users. |
| path_template | string | – | A template for organizing submission subfolders using uploader metadata. Supports placeholders for name, email, IP address, company, and custom form fields. |
| paths | array | – | A list of file and folder paths to include in the bundle. Order is preserved as specified. |
| permissions | string | – | The permission level for accessing folders within this bundle. |
| require_registration | boolean | – | When enabled, displays a registration form to capture the downloader's name and email address. |
| require_share_recipient | boolean | – | When enabled, restricts access to only recipients who have been explicitly invited via email through the Files.com interface. |
| send_email_receipt_to_uploader | boolean | – | When enabled, sends a delivery receipt to the uploader upon bundle access. Only applicable for writable bundles. |
| watermark_attachment_file | string | – | Base64-encoded file content for upload. A watermark image file to overlay on all bundle item previews for branding or security purposes. |
No output schema declared.
No examples provided.
update_bundle_notification Update Bundle Notification ~85
Update notification settings for a bundle, controlling when notifications are triggered for registration and upload actions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the bundle notification to update. |
| notify_on_registration | boolean | – | Enable or disable notifications when a registration action occurs for this bundle. |
| notify_on_upload | boolean | – | Enable or disable notifications when an upload action occurs for this bundle. |
No output schema declared.
No examples provided.
update_clickwrap Update Clickwrap ~210
Update an existing Clickwrap agreement configuration, including its name and usage settings across bundles, inboxes, and user registrations.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the Clickwrap agreement to update. |
| name | string | – | Display name for the Clickwrap agreement, used when presenting multiple agreements to users for selection. |
| use_with_bundles | string | – | Controls whether this Clickwrap is available for Bundle operations. Set to 'require' to mandate acceptance, 'available' to offer optionally, or 'none' to disable. |
| use_with_inboxes | string | – | Controls whether this Clickwrap is available for Inbox operations. Set to 'require' to mandate acceptance, 'available' to offer optionally, or 'none' to disable. |
| use_with_users | string | – | Controls whether this Clickwrap is required for user registrations via email invitation. Applies only when users are invited to set their own password. Set to 'require' to mandate acceptance or 'none… |
No output schema declared.
No examples provided.
update_file_comment Update File Comment ~61
Update the body text of an existing file comment. Allows modification of comment content after initial creation.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The new comment text content to replace the existing body. |
| id | string | yes | The unique identifier of the file comment to update. |
No output schema declared.
No examples provided.
update_file_metadata Update File Metadata ~82
Update metadata for a file or folder, including priority color and modification timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The file or folder path to update. |
| priority_color | string | – | Priority or bookmark color to assign to the file or folder. |
| provided_mtime | string | – | The modification timestamp to set for the file or folder in ISO 8601 format. |
No output schema declared.
No examples provided.
update_form_field_set Update Form Field Set ~94
Update an existing form field set by modifying its title and/or associated form fields. Changes are applied to the specified form field set.
| Name | Type | Req | Description |
|---|---|---|---|
| form_fields | array | – | Array of form fields to associate with this field set. Order may be significant for display purposes. |
| id | string | yes | The unique identifier of the form field set to update. |
| title | string | – | The display title for this form field set. |
No output schema declared.
No examples provided.
update_group Update Group ~115
Update an existing group's properties including name, notes, members, and administrators. Provide only the fields you want to modify.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_ids | string | – | Comma-separated list of user IDs to designate as group administrators. |
| id | string | yes | The unique identifier of the group to update. |
| name | string | – | The name of the group. |
| notes | string | – | Additional notes or description for the group. |
| user_ids | string | – | Comma-separated list of user IDs to add as members of the group. |
No output schema declared.
No examples provided.
update_group_membership Update Group Membership ~91
Update a user's membership status in a group, including their administrator privileges. Allows modification of a user's role within the specified group.
| Name | Type | Req | Description |
|---|---|---|---|
| admin | boolean | – | Whether the user should have administrator privileges within the group. |
| group_id | string | yes | The unique identifier of the group containing the membership to update. |
| user_id | string | yes | The unique identifier of the user whose group membership should be updated. |
No output schema declared.
No examples provided.
update_group_user Update Group User ~102
Update a user's membership in a group, including their administrator status. Modify group user associations and permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| admin | boolean | – | Whether the user should have administrator privileges within the group. |
| group_id | string | yes | The group to which the user belongs or should be associated. |
| id | string | yes | The unique identifier of the group user membership record to update. |
| user_id | string | yes | The user to be added or updated in the group membership. |
No output schema declared.
No examples provided.
update_message Update Message ~93
Update an existing message with new subject and body content. The message will be associated with the specified project.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The new content body for the message. |
| id | string | yes | The unique identifier of the message to update. |
| project_id | string | yes | The project ID to which this message should be attached or reassigned. |
| subject | string | yes | The new subject line for the message. |
No output schema declared.
No examples provided.
update_message_comment Update Message Comment ~59
Update the body text of an existing message comment. Allows modification of comment content after initial creation.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The updated text content for the message comment. |
| id | string | yes | The unique identifier of the message comment to update. |
No output schema declared.
No examples provided.
update_notification Update Notification ~368
Update notification settings for a specific notification rule, including trigger conditions, aggregation intervals, and recipient filters.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the notification rule to update. |
| message | string | – | Custom message text to include in notification emails sent for this rule. |
| notify_on_copy | boolean | – | When enabled, copying or moving resources into the monitored path will trigger notifications in addition to upload events. |
| notify_on_delete | boolean | – | When enabled, file deletions from the monitored path will trigger notifications. |
| notify_on_download | boolean | – | When enabled, file downloads from the monitored path will trigger notifications. |
| notify_on_move | boolean | – | When enabled, file moves to the monitored path will trigger notifications. |
| notify_on_upload | boolean | – | When enabled, file uploads to the monitored path will trigger notifications. |
| notify_user_actions | boolean | – | When enabled, notifications will be sent for actions initiated by the user account itself, not just external actions. |
| recursive | boolean | – | When enabled, notifications will apply to all subfolders within the monitored path. |
| send_interval | string | – | The time interval over which notifications are aggregated before sending. Valid values are five_minutes, fifteen_minutes, hourly, or daily. |
| trigger_by_share_recipients | boolean | – | When enabled, actions performed by share recipients will trigger notifications. |
| triggering_filenames | array | – | Array of filename patterns (supporting wildcards) to match against action paths. Only actions on matching files will trigger notifications. |
| 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. |
No output schema declared.
No examples provided.
update_public_key Update Public Key ~76
Update the title or metadata of an existing public key. This allows you to change the internal reference name for a key that has already been created.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the public key to update. |
| title | string | yes | A descriptive name or label for the public key used for internal reference and identification. |
No output schema declared.
No examples provided.
update_remote_server Update Remote Server ~608
Update configuration for a remote server connection. Modify authentication credentials, connection settings, storage bucket details, and security parameters for cloud storage providers (S3, Azure, Google Cloud, etc.) or traditional servers (FTP, SFTP, WebDAV).
| 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 | – | Restrict remote server connections to dedicated IP addresses only. |
| filebase | object | – | Filebase connection settings |
| files_agent_permission_set | string | – | Permission level for the files agent to access local files. |
| files_agent_root | string | – | Local root directory path for the files agent. |
| google_cloud_storage | object | – | Google Cloud Storage connection settings |
| hostname | string | – | Hostname or IP address of the remote server. |
| id | string | yes | The unique identifier of the remote server to update. |
| max_connections | string | – | Maximum number of parallel connections to the remote server. Ignored for S3 connections which parallelize automatically. |
| name | string | – | Internal name for the remote server for reference and identification. |
| one_drive_account_type | string | – | OneDrive account type: personal for individual accounts or business_other for organizational accounts. |
| pin_to_site_region | boolean | – | Force all communications with this remote server through the primary region of the site. Can be overridden by site-wide settings. |
| port | string | – | Port number for the remote server connection. Not required for S3 or cloud storage providers. |
| private_key | string | – | Private key for SSH or certificate-based authentication. |
| private_key_passphrase | string | – | Passphrase to decrypt the private key if it is encrypted. |
| rackspace | object | – | Rackspace Cloud Files connection settings |
| s3_bucket | string | – | S3 bucket name for file storage. |
| s3_compatible | object | – | S3-compatible storage connection settings |
| s3_region | string | – | AWS region code for S3 bucket location. |
| server_certificate | string | – | SSL certificate validation mode: require_match to validate against server certificate, or allow_any to accept any certificate. |
| server_host_key | string | – | SSH host key in OpenSSH format (as would appear in ~/.ssh/known_hosts). If provided, the server host key must match exactly. |
| server_type | string | – | Type of remote server connection. |
| ssl | string | – | SSL/TLS requirement for the connection: if_available to use when supported, require to mandate SSL, require_implicit for implicit SSL, or never to disable. |
| ssl_certificate | string | – | SSL client certificate for mutual TLS authentication. |
| wasabi | object | – | Wasabi storage connection settings |
No output schema declared.
No examples provided.
update_remote_server_configuration Update Remote Server Configuration ~246
Submit local configuration changes, commit them, and retrieve the updated configuration file for a remote server. This operation is used by Remote Server integrations such as the Files.com Agent to synchronize agent configuration state.
| Name | Type | Req | Description |
|---|---|---|---|
| config_version | string | – | The version identifier of the agent configuration being submitted. |
| hostname | string | – | The hostname or IP address of the remote server. |
| id | string | yes | The unique identifier of the remote server to update. |
| permission_set | string | – | The permission level for the agent, controlling access scope. |
| port | string | – | The network port on which the agent listens for incoming connections. |
| private_key | string | – | The private key used for secure authentication and encryption. |
| public_key | string | – | The public key corresponding to the private key for secure communication. |
| root | string | – | The local filesystem root path where the agent operates and stores files. |
| server_host_key | string | – | The server's host key used for SSH-based authentication and verification. |
| status | string | – | The current operational state of the agent, either running or shutdown. |
| subdomain | string | – | The subdomain identifier for the remote server configuration. |
No output schema declared.
No examples provided.
update_sftp_host_key Update SFTP Host Key ~96
Update an SFTP host key's friendly name and/or private key data. Specify the host key ID and provide the fields you want to modify.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the SFTP host key to update. |
| name | string | – | A user-friendly name to identify this SFTP host key. |
| private_key | string | – | The private key data in PEM format or other standard key format. |
No output schema declared.
No examples provided.
update_style Update Style ~74
Update a style configuration by uploading a new branding file. Specify the style path and provide the binary file for custom branding.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Base64-encoded file content for upload. Binary file containing the logo or branding assets for custom styling. |
| path | string | yes | The path identifier for the style to update. |
No output schema declared.
No examples provided.
update_user Update User ~747
Update user account settings, permissions, and authentication configuration. Allows modification of user profile, access controls, security settings, and notification preferences.
| 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 | – | Mark whether the user has acknowledged all announcements displayed in the UI. |
| authenticate_until | string | – | Scheduled date and time when this user account will be automatically deactivated. |
| authentication_method | string | – | Authentication method used for this user account. |
| billing_permission | boolean | – | Grant this user permission to manage account settings, process payments, and view invoices. |
| bypass_inactive_disable | boolean | – | Prevent this user from being automatically disabled due to inactivity, overriding site-wide settings. |
| bypass_site_allowed_ips | boolean | – | Allow this user to bypass site-wide IP address restrictions and blacklists. |
| company | string | – | User's organization or company name. |
| dav_permission | boolean | – | Enable or disable WebDAV protocol access for this user. |
| disabled | boolean | – | Disable or enable the user account. Disabled users cannot log in and do not consume billing seats. Users may be automatically disabled after prolonged inactivity based on site configuration. |
| string | – | User's email address. | |
| ftp_permission | boolean | – | Enable or disable FTP and FTPS protocol access for this user. |
| grant_permission | string | – | Permission level to grant on the user's root folder. Options include full access, read-only, write, list directory contents, or history access. |
| header_text | string | – | Custom message text displayed to this user in the UI header. |
| language | string | – | User's preferred language for the UI. |
| name | string | – | User's full name. |
| notes | string | – | Internal notes or comments about this user for administrative reference. |
| notification_daily_send_time | string | – | Hour of the day (0-23) when daily notifications 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 a user can use the same password before being required to change it. |
| receive_admin_alerts | boolean | – | Enable or disable receipt of administrative alerts such as certificate expiration warnings and account overages. |
| require_2fa | string | – | Two-factor authentication requirement setting for this user. |
| require_password_change | boolean | – | Require this user to change their password on the next login. |
| restapi_permission | boolean | – | Enable or disable REST API access for this user. |
| self_managed | boolean | – | Indicate whether this user manages their own credentials or is a shared/bot account with managed credentials. |
| sftp_permission | boolean | – | Enable or disable SFTP protocol access for this user. |
| site_admin | boolean | – | Grant or revoke site administrator privileges for this user. |
| skip_welcome_screen | boolean | – | Skip the welcome screen when this user first logs into the UI. |
| ssl_required | string | – | SSL/TLS encryption requirement setting for this user's connections. |
| sso_strategy_id | string | – | SSO (Single Sign On) strategy ID associated with this user for federated authentication. |
| subscribe_to_newsletter | boolean | – | Subscribe or unsubscribe this user from the newsletter. |
| time_zone | string | – | 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. |
No output schema declared.
No examples provided.
update_user_account Update User Account ~764
Update user account settings, permissions, and authentication configuration. Allows modification of user profile, access controls, security settings, and notification preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_ips | string | – | Comma-separated or newline-delimited list of IP addresses permitted to access this user account. |
| announcements_read | boolean | – | Whether the user has read all announcements displayed in the UI. |
| authenticate_until | string | – | Date and time when the user account will be automatically deactivated. |
| authentication_method | string | – | The authentication method used for this user account. |
| billing_permission | boolean | – | Whether the user can perform operations on account settings, payments, and invoices. |
| bypass_inactive_disable | boolean | – | Whether the user is exempt from automatic deactivation due to inactivity. |
| bypass_site_allowed_ips | boolean | – | Whether the 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 access files via WebDAV protocol. |
| disabled | boolean | – | Whether the user account is disabled. Disabled users cannot log in and do not count toward billing. Users may be automatically disabled after an inactivity period based on site settings. |
| string | – | The user's email address. | |
| ftp_permission | boolean | – | Whether the user can access files and accounts 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 access. |
| header_text | string | – | Custom text message displayed to the user in the UI header for notifications or announcements. |
| id | string | yes | The unique identifier of the user to update. |
| 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 warnings and account overages. |
| require_2fa | string | – | Two-factor authentication requirement setting for this user. |
| require_password_change | boolean | – | Whether the user must change their password on the next login. |
| restapi_permission | boolean | – | Whether the user can access and use the REST API. |
| self_managed | boolean | – | Whether the user manages their own credentials or is a shared/bot account with managed credentials. |
| sftp_permission | boolean | – | Whether the user can access files and accounts via SFTP protocol. |
| site_admin | boolean | – | Whether the user has administrator privileges for this site. |
| skip_welcome_screen | boolean | – | Whether to skip the welcome screen when the user first logs into the UI. |
| ssl_required | string | – | SSL/TLS encryption requirement setting for this user's connections. |
| sso_strategy_id | string | – | The ID of the SSO (Single Sign On) strategy assigned to this user, if applicable. |
| 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 at the site level. Not used for API, desktop, or web interface access. |
No output schema declared.
No examples provided.
upload_file Upload File ~310
Upload a file to the specified path, supporting multipart uploads, append operations, and optional parent directory creation. Supports various upload actions including standard upload, append, and multipart completion.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | The type of upload action to perform: `upload` for standard file upload, `append` to append to existing file, `attachment` for attachment handling, `put` for direct replacement, `end` to finalize mul… |
| etags_etag | array | yes | Array of etag identifiers for multipart upload validation, used to verify part integrity. Order corresponds to part numbers. |
| etags_part | array | yes | Array of part numbers corresponding to each etag, indicating the sequence of multipart upload segments. Order must match the etags array. |
| length | string | – | The length of the file being uploaded in bytes. |
| mkdir_parents | boolean | – | Whether to automatically create parent directories in the path if they do not already exist. |
| parts | string | – | The number of parts to fetch or process for multipart uploads. |
| path | string | yes | The file system path where the file will be uploaded or operated on. |
| provided_mtime | string | – | User-provided modification timestamp for the uploaded file in ISO 8601 format. |
| size | string | – | The total size of the file in bytes. |
| structure | string | – | When copying a folder, set to `true` to copy only the directory structure without file contents. |
No output schema declared.
No examples provided.
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
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 52 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.