com.mcparmory/files-com
PYPI · MCPARMORY-FILES-COM · 2 COMPONENTS
Manage files, users, and automated workflows across cloud storage and protocols
Available components
Last scanned (7 hours ago)
Scores higher than 81% of PyPI 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 2 of 40 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- 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 Management67
- Stability observed for 20 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 current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −5
- Stability: pass → 0.63 functional
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- 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 pypi/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 | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 40 packages
| Packages resolved | 40 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_bandwidth_snapshots List Bandwidth Snapshots ~108
Retrieve a paginated list of bandwidth snapshots. Results can be sorted by the logged timestamp in ascending or descending order.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Use the field name as the key and 'asc' or 'desc' as the value. Valid sortable field is 'logged_at'. |
No output schema declared.
No examples provided.
list_bandwidth_snapshots_remote List Bandwidth Snapshots (Remote) ~110
Retrieve a paginated list of remote bandwidth snapshots. Results can be sorted by the logged timestamp in ascending or descending order.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Use the field name as the key and 'asc' or 'desc' as the value. Valid sortable field is 'logged_at'. |
No output schema declared.
No examples provided.
list_behaviors_by_path List Behaviors by Path ~158
Retrieve a list of behaviors from a specified folder path, with optional filtering, sorting, and recursive traversal capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The folder path where behaviors are located. This path determines the starting point for the behavior listing. |
| per_page | string | – | Maximum number of behavior records to return per page. Recommended to use 1,000 or less for optimal performance. |
| recursive | string | – | Include behaviors from parent directories above the specified path when enabled. Controls whether the listing is limited to the exact path or includes the hierarchy above it. |
| sort_by | object | – | Sort results by the behavior field in ascending or descending order. Specify as an object with the field name as key and sort direction as value. |
No output schema declared.
No examples provided.
list_bundle_downloads List Bundle Downloads ~146
Retrieve a paginated list of bundle downloads with optional filtering by bundle or bundle registration ID, and sorting capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_id | string | – | Filter results to downloads associated with a specific bundle by its ID. |
| bundle_registration_id | string | – | Filter results to downloads associated with a specific bundle registration by its ID. |
| 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. Only `created_at` is supported as a valid sort field. |
No output schema declared.
No examples provided.
list_bundle_notifications List Bundle Notifications ~87
Retrieve a paginated list of notifications for a specific bundle or all bundles. Use pagination parameters to control result size and retrieval.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_id | string | – | Filter notifications by a specific bundle ID. Omit to retrieve notifications for all bundles. |
| per_page | string | – | Maximum number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
No output schema declared.
No examples provided.
list_bundle_recipients List Bundle Recipients ~113
Retrieve a list of recipients associated with a specific bundle. Supports pagination and sorting by registration status.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_id | string | yes | The ID of the bundle for which to list recipients. |
| 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. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Valid field is `has_registrations`. |
No output schema declared.
No examples provided.
list_bundle_registrations List Bundle Registrations ~76
Retrieve a paginated list of bundle registrations, optionally filtered by a specific bundle ID.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_id | string | – | Filter results to registrations associated with a specific bundle by its ID. |
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
No output schema declared.
No examples provided.
list_bundles List Bundles ~110
Retrieve a paginated list of bundles with optional sorting. Use pagination parameters to control result size and sorting to organize bundles by creation date or code.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of bundle records to return per page. Recommended to use 1,000 or less for optimal performance, though up to 10,000 is supported. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Supports sorting by `created_at` or `code` fields. |
No output schema declared.
No examples provided.
list_cipher_uses List Cipher Uses ~73
Retrieve a paginated list of cipher uses associated with the authenticated user. Use the per_page parameter to control result set size.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, though up to 10,000 is supported. |
No output schema declared.
No examples provided.
list_cipher_uses_by_user List Cipher Uses by User ~115
Retrieve a paginated list of cipher uses for a specific user. Use user_id value of 0 to retrieve cipher uses for the current authenticated session's user.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of cipher use records to return per page. Maximum allowed is 10,000, though 1,000 or fewer is recommended for optimal performance. |
| user_id | string | yes | The unique identifier of the user whose cipher uses should be retrieved. Use 0 to refer to the current session's authenticated user. |
No output schema declared.
No examples provided.
list_clickwraps List Clickwraps ~66
Retrieve a paginated list of clickwraps. Use the per_page parameter to control the number of records returned in each page.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of clickwrap records to return per page. Recommended to use 1,000 or less for optimal performance. |
No output schema declared.
No examples provided.
list_dns_records List DNS Records ~74
Retrieve the DNS records configured for a site. Results can be paginated to manage large record sets.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of DNS records to return per page. Recommended to use 1,000 or less for optimal performance, though up to 10,000 records can be retrieved in a single request. |
No output schema declared.
No examples provided.
list_dns_records_site List Site DNS Records ~75
Retrieve the DNS records configured for a site. Results can be paginated to manage large record sets.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of DNS records to return per page. Recommended to use 1,000 or less for optimal performance, though up to 10,000 records can be retrieved in a single request. |
No output schema declared.
No examples provided.
list_exavault_reserved_ip_addresses List ExaVault Reserved IP Addresses ~90
Retrieve a paginated list of all public IP addresses reserved and used by ExaVault for its services. Use this to configure firewall rules or IP allowlists for ExaVault connectivity.
| 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. |
No output schema declared.
No examples provided.
list_external_events List External Events ~119
Retrieve a paginated list of external events with optional sorting. Use this to monitor and track events from remote servers across your file management system.
| 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 up to 10,000 is supported. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Valid sortable fields are: remote_server_type, site_id, folder_behavior_id, event_type, created_at, or status. |
No output schema declared.
No examples provided.
list_file_history List File History ~195
Retrieve the change history for a specific file, with optional filtering by date range and customizable sorting and pagination.
| 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 only include history entries created on or before this date and time. |
| path | string | yes | The file path to retrieve history for. |
| per_page | string | – | Number of records to return per page. Maximum is 10,000; 1,000 or less is recommended. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Use object notation (e.g., `sort_by[user_id]=desc`). Valid fields are `user_id` and `created_at`. |
| start_at | string | – | Filter to only include history entries created on or after this date and time. |
No output schema declared.
No examples provided.
list_folder_history List Folder History ~170
Retrieve the change history for a specific folder, with optional filtering by date range and customizable sorting and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| display | string | – | Control the detail level of returned records: `full` for complete details or `parent` for parent-only information. |
| end_at | string | – | Filter to exclude history entries created after this date and time. |
| path | string | yes | The folder path for which to retrieve history. |
| per_page | string | – | Number of history records to return per page. Recommended maximum is 1,000 for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Supported fields are `user_id` and `created_at`. |
| start_at | string | – | Filter to exclude history entries created before this date and time. |
No output schema declared.
No examples provided.
list_folders List Folders ~169
List folders at a specified path with optional filtering, previews, and metadata. Supports site-wide search when enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The folder path to list contents from. |
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
| preview_size | string | – | Size of file previews to include in the response. |
| search_all | boolean | – | When enabled, searches the entire site and ignores the specified folder path. Use only for ad-hoc human searches, not automated processes, as results are best-effort and not real-time guaranteed. |
| with_previews | boolean | – | Include file preview data in the response. |
| with_priority_color | boolean | – | Include file priority color metadata in the response. |
No output schema declared.
No examples provided.
list_form_field_sets List Form Field Sets ~69
Retrieve a paginated list of form field sets. Use pagination to control the number of records returned per page.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, with a maximum of 10,000. |
No output schema declared.
No examples provided.
list_group_members List Group Members ~95
Retrieve a paginated list of users who are members of a specific group. Use pagination parameters to control result size and navigate through large member lists.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The unique identifier of the group whose members you want to retrieve. |
| per_page | string | – | Number of user records to return per page. Recommended to use 1,000 or less for optimal performance; maximum allowed is 10,000. |
No output schema declared.
No examples provided.
list_group_permissions List Group Permissions ~167
Retrieve a paginated list of permissions for a specific group. Supports filtering, sorting, and optionally including inherited permissions from parent groups.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The ID of the group for which to list permissions. Note: This parameter is deprecated; use the `filter[group_id]` query parameter for filtering instead. |
| include_groups | boolean | – | When enabled, includes permissions inherited from the group's parent groups 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`. |
No output schema declared.
No examples provided.
list_group_users List Group Users ~113
Retrieve a paginated list of users belonging to a group. Use the per_page parameter to control result set size.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | – | Group ID. If provided, will return group_users of this group. |
| 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. |
| user_id | string | – | User ID. If provided, will return group_users of this user. |
No output schema declared.
No examples provided.
list_groups List Groups ~121
Retrieve a paginated list of groups with optional filtering by IDs and sorting capabilities. Use this operation to browse available groups in your system.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | string | – | Filter results to include only groups with the specified IDs. Provide as a comma-separated list of group identifiers. |
| per_page | string | – | Maximum number of group 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. The `name` field is supported for sorting. |
No output schema declared.
No examples provided.
list_history List History ~202
Retrieve the complete action history for the site with optional filtering by date range and customizable display format.
| Name | Type | Req | Description |
|---|---|---|---|
| display | string | – | Control the detail level of returned history entries. Use `full` for complete details or `parent` for parent-only view. Leave blank for default format. |
| end_at | string | – | Filter to exclude history entries after this date and time. Leave blank to include all later entries. |
| per_page | string | – | Number of history records to return per page. Maximum allowed is 10,000, though 1,000 or fewer is recommended for optimal performance. |
| 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' |
| start_at | string | – | Filter to exclude history entries before this date and time. Leave blank to include all earlier entries. |
No output schema declared.
No examples provided.
list_history_export_results List History Export Results ~98
Retrieve a paginated list of results from a completed history export. Use the history export ID to fetch the exported records with configurable page size.
| Name | Type | Req | Description |
|---|---|---|---|
| history_export_id | string | yes | The unique identifier of the history export whose results you want to retrieve. |
| per_page | string | – | Number of results to return per page. Recommended to use 1,000 or less for optimal performance, though up to 10,000 is supported. |
No output schema declared.
No examples provided.
list_inbox_recipients List Inbox Recipients ~114
Retrieve a list of recipients associated with a specific inbox. Use sorting and pagination to manage large result sets.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | The unique identifier of the inbox for which to list recipients. |
| 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. Only `has_registrations` is supported as a sortable field. |
No output schema declared.
No examples provided.
list_inbox_registrations List Inbox Registrations ~104
Retrieve a paginated list of inbox registrations, optionally filtered by a specific inbox. Use pagination parameters to control result set size.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_behavior_id | string | – | Filter results by the ID of the associated inbox. When provided, only registrations for that specific inbox are returned. |
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, with a maximum of 10,000. |
No output schema declared.
No examples provided.
list_inbox_uploads List Inbox Uploads ~131
Retrieve a paginated list of uploads associated with inboxes. Filter by specific inbox or inbox registration, and optionally sort results by creation date.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | – | Filter uploads by the associated inbox ID. |
| inbox_registration_id | string | – | Filter uploads by the associated inbox registration ID. |
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Only `created_at` is supported as a valid sort field. |
No output schema declared.
No examples provided.
list_invoices List Invoices ~61
Retrieve a paginated list of invoices. Use the per_page parameter to control the number of results returned per page.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of invoice records to return per page. Recommended to use 1,000 or less for optimal performance. |
No output schema declared.
No examples provided.
list_ip_addresses List IP Addresses ~76
Retrieve a paginated list of IP addresses associated with the current site. Use the per_page parameter to control result set size.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, though the API supports up to 10,000 records per page. |
No output schema declared.
No examples provided.
list_locks List Locks for Path ~103
Retrieve all locks for a specified path, with optional support for including locks from child objects and pagination control.
| Name | Type | Req | Description |
|---|---|---|---|
| include_children | boolean | – | Whether to include locks from child objects in addition to the specified path. |
| path | string | yes | The resource path for which to retrieve locks. |
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, with a maximum of 10,000. |
No output schema declared.
No examples provided.
list_logins List Logins ~186
Retrieve a paginated list of site login history with optional filtering by date range and sorting capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| display | string | – | Control the response format. Use `full` for complete details or `parent` for parent-level information only. |
| end_at | string | – | Filter to exclude login records after this date and time. Leave blank to include all later entries. |
| per_page | string | – | Number of records to return per page. Recommended maximum is 1,000 for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Use format `sort_by[field_name]=direction` where field_name is `user_id` or `created_at` and direction is `asc` or `desc`. |
| start_at | string | – | Filter to exclude login records before this date and time. Leave blank to include all earlier entries. |
No output schema declared.
No examples provided.
list_message_comment_reactions List Message Comment Reactions ~84
Retrieve all reactions added to a specific message comment. Results are paginated and can be controlled via the per_page parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| message_comment_id | string | yes | The ID of the message comment for which to retrieve reactions. |
| per_page | string | – | Maximum number of reactions to return per page. Recommended to use 1,000 or less for optimal performance. |
No output schema declared.
No examples provided.
list_message_comments List Message Comments ~79
Retrieve all comments associated with a specific message. Results are paginated and can be controlled via the per_page parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The ID of the message for which to retrieve comments. |
| per_page | string | – | Maximum number of comments to return per page. Recommended to use 1,000 or less for optimal performance. |
No output schema declared.
No examples provided.
list_message_reactions List Message Reactions ~77
Retrieve all reactions added to a specific message. Supports pagination to control the number of results returned per page.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The ID of the message to retrieve reactions for. |
| per_page | string | – | Maximum number of reactions to return per page. Recommended to use 1,000 or less for optimal performance. |
No output schema declared.
No examples provided.
list_messages List Messages ~86
Retrieve a paginated list of messages for a specific project. Use pagination parameters to control the number of results returned per page.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of messages to return per page. Recommended to use 1,000 or less for optimal performance. |
| project_id | string | yes | The project ID for which to retrieve messages. Required to scope results to a specific project. |
No output schema declared.
No examples provided.
list_notifications List Notifications ~146
Retrieve a paginated list of notifications with optional sorting and ancestor path inclusion. Use this to display notification feeds or audit logs with flexible filtering options.
| Name | Type | Req | Description |
|---|---|---|---|
| include_ancestors | boolean | – | When enabled and a `path` filter is applied, include notifications from all parent paths in addition to the specified path. Has no effect if `path` is not specified. |
| per_page | string | – | Maximum number of notification records to return per page. Recommended to use 1,000 or less for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Valid sortable fields are `path`, `user_id`, or `group_id`. |
No output schema declared.
No examples provided.
list_payments List Payments ~71
Retrieve a paginated list of payments. Use the per_page parameter to control the number of records returned per page.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of payment records to return per page. Recommended to use 1,000 or less for optimal performance, though up to 10,000 is supported. |
No output schema declared.
No examples provided.
list_permissions List Permissions ~143
Retrieve a paginated list of permissions with optional sorting and group inheritance filtering. Use this to view all permissions in the system, optionally including permissions inherited from group memberships.
| Name | Type | Req | Description |
|---|---|---|---|
| include_groups | boolean | – | When filtering by user or group, include permissions inherited from the user's group memberships in addition to directly assigned permissions. |
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, though up to 10,000 is supported. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Valid sortable fields are: group_id, path, user_id, or permission. |
No output schema declared.
No examples provided.
list_public_keys List Public Keys ~70
Retrieve a paginated list of public keys. Use the per_page parameter to control the number of results returned per page.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, with a maximum of 10,000. |
No output schema declared.
No examples provided.
list_public_keys_by_user List Public Keys by User ~100
Retrieve a paginated list of public keys for a specified user. Use user ID `0` to retrieve keys for the current authenticated session.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of public keys to return per page. Recommended to use 1,000 or less for optimal performance. |
| user_id | string | yes | The unique identifier of the user whose public keys should be retrieved. Use `0` to refer to the current authenticated user. |
No output schema declared.
No examples provided.
list_public_keys_current_user List Public Keys for Current User ~77
Retrieve a paginated list of public keys associated with the user account. Use the per_page parameter to control pagination size.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, though the API supports up to 10,000 records per page. |
No output schema declared.
No examples provided.
list_remote_servers List Remote Servers ~70
Retrieve a paginated list of remote servers. Use the per_page parameter to control the number of results returned per page.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, with a maximum of 10,000. |
No output schema declared.
No examples provided.
list_requests List Requests ~121
Retrieve a paginated list of requests with optional filtering and sorting. By default, shows only the current user's requests unless the user is a site admin.
| Name | Type | Req | Description |
|---|---|---|---|
| mine | boolean | – | Filter to show only requests belonging to the current user. Defaults to true for non-admin users. |
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Only the `destination` field is supported for sorting. |
No output schema declared.
No examples provided.
list_requests_folder List Requests Folder ~145
Retrieve a list of requests, optionally filtered by folder path and user ownership. Results can be paginated and sorted by destination.
| Name | Type | Req | Description |
|---|---|---|---|
| mine | boolean | – | Filter to show only requests created by the current user. Defaults to true for non-admin users. |
| path | string | yes | The folder path to filter requests. Use `/` to represent the root directory. Required parameter. |
| per_page | string | – | Number of records to return per page. Maximum allowed is 10,000, though 1,000 or less is recommended for optimal performance. |
| sort_by | object | – | Sort results by a specified field in ascending or descending order. Valid field is `destination`. |
No output schema declared.
No examples provided.
list_requests_user List User Requests ~69
Retrieve a paginated list of user requests. 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, with a maximum of 10,000. |
No output schema declared.
No examples provided.
list_reserved_ip_addresses List Reserved IP Addresses ~66
Retrieve a paginated list of all reserved public IP addresses available in the system.
| 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. |
No output schema declared.
No examples provided.
list_sftp_host_keys List SFTP Host Keys ~68
Retrieve a paginated list of SFTP host keys. Use pagination to manage large result sets efficiently.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, with a maximum of 10,000. |
No output schema declared.
No examples provided.
list_site_ip_addresses List Site IP Addresses ~72
Retrieve a paginated list of IP addresses associated with the current site. Use the per_page parameter to control result set size.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance, with a maximum of 10,000. |
No output schema declared.
No examples provided.
list_usage_snapshots List Usage Snapshots ~62
Retrieve a paginated list of usage snapshots. Use the per_page parameter to control the number of records returned per page.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | string | – | Number of records to return per page. Recommended to use 1,000 or less for optimal performance. |
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 PyPI package, launched with uvx mcparmory-files-com. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-files-com
claude mcp add com-mcparmory-files-com -- uvx mcparmory-files-com
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 PyPI package (mcparmory-files-com).
Is the com.mcparmory/files-com MCP server safe to use?
com.mcparmory/files-com scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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.
What licence is the com.mcparmory/files-com MCP server under?
com.mcparmory/files-com declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.