com.mcparmory/shopify-admin
PYPI · MCPARMORY-SHOPIFY-ADMIN · 2 COMPONENTS · SCANNED SEP 20
Manage products, orders, customers, inventory, and store configuration
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 Security87
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
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: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 14807 tokens (~83/item across 177 items; 177 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 Safety93
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 25 of 35 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_application_charge" implies "charge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 177 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
How do I install the com.mcparmory/shopify-admin MCP server?
com.mcparmory/shopify-admin runs locally as a PyPI package, launched with uvx mcparmory-shopify-admin. 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-shopify-admin
claude mcp add com-mcparmory-shopify-admin -- uvx mcparmory-shopify-admin
{
"mcpServers": {
"com-mcparmory-shopify-admin": {
"command": "uvx",
"args": [
"mcparmory-shopify-admin"
]
}
}
} {
"servers": {
"com-mcparmory-shopify-admin": {
"command": "uvx",
"args": [
"mcparmory-shopify-admin"
]
}
}
} codex mcp add com-mcparmory-shopify-admin -- uvx mcparmory-shopify-admin
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-shopify-admin": {
"type": "local",
"command": [
"uvx",
"mcparmory-shopify-admin"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-shopify-admin --command uvx --arg mcparmory-shopify-admin
mcp_servers:
com-mcparmory-shopify-admin:
command: "uvx"
args: ["mcparmory-shopify-admin"] {
"McpServers": {
"com-mcparmory-shopify-admin": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-shopify-admin"
]
}
}
} assistant mcp add com-mcparmory-shopify-admin -t stdio -c uvx -a mcparmory-shopify-admin
{
"mcpServers": {
"com-mcparmory-shopify-admin": {
"command": "uvx",
"args": [
"mcparmory-shopify-admin"
]
}
}
} 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.
- 20 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 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 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
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 pypi/mcparmory-shopify-admin@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 |
Background: How many MCP packages publish verified provenance →
Dependencies 46 packages
| Packages resolved | 46 |
|---|---|
| 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 →
search_gift_cards Search Gift Cards ~177
Search for gift cards using indexed fields like balance, email, or creation date. Results are paginated and can be filtered, sorted, and limited to specific fields.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | Comma-separated list of field names to include in the response. Omit to return all fields. |
| limit | – | – | Maximum number of results to return per request, between 1 and 250. Defaults to 50 results. |
| order | – | – | The field and direction to sort results by. Specify a field name followed by ASC or DESC (for example: balance DESC or created_at ASC). Defaults to sorting by disabled_at in descending order. |
| query | – | – | The search query text to match against indexed gift card fields including created_at, updated_at, disabled_at, balance, initial_value, amount_spent, email, and last_characters. |
No output schema declared.
No examples provided.
send_customer_invite Send Customer Invite ~47
Sends an account invitation email to a customer, allowing them to create or access their account.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The unique identifier of the customer who will receive the invitation. |
No output schema declared.
No examples provided.
send_fulfillment_order_cancellation_request Send Fulfillment Order Cancellation Request ~106
Sends a cancellation request to the fulfillment service for a specific fulfillment order. This notifies the fulfillment provider that the order should be cancelled if not yet fulfilled.
| Name | Type | Req | Description |
|---|---|---|---|
| fulfillment_order_id | string | yes | The unique identifier of the fulfillment order to cancel. This ID references a specific fulfillment order within your Shopify store. |
| message | – | – | An optional message explaining the reason for the cancellation request. This message is typically sent to the fulfillment service to provide context for the cancellation. |
No output schema declared.
No examples provided.
send_fulfillment_request Send Fulfillment Request ~125
Sends a fulfillment request to the fulfillment service for a specific fulfillment order, optionally targeting specific line items or including a message for the fulfillment provider.
| Name | Type | Req | Description |
|---|---|---|---|
| fulfillment_order_id | string | yes | The unique identifier of the fulfillment order to request fulfillment for. |
| fulfillment_order_line_items | – | – | An optional list of specific line items from the fulfillment order to request for fulfillment. If omitted, all unfulfilled line items in the order are included in the request. |
| message | – | – | An optional message to include with the fulfillment request, typically for communicating special instructions or notes to the fulfillment service. |
No output schema declared.
No examples provided.
set_customer_default_address Set Customer Default Address ~79
Designates a specific address as the default address for a customer. This address will be used as the primary contact address for the customer account.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | string | yes | The unique identifier of the address to set as the customer's default address. |
| customer_id | string | yes | The unique identifier of the customer whose default address is being updated. |
No output schema declared.
No examples provided.
update_article Update Article ~68
Updates an existing article within a blog. Modify article content, metadata, and publishing settings by providing the blog and article identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | string | yes | The unique identifier of the article to update. |
| blog_id | string | yes | The unique identifier of the blog containing the article to update. |
No output schema declared.
No examples provided.
update_carrier_service Update Carrier Service ~48
Updates an existing carrier service configuration. Only the application that originally created the carrier service can modify it.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier_service_id | string | yes | The unique identifier of the carrier service to update. |
No output schema declared.
No examples provided.
update_custom_collection Update Custom Collection ~50
Updates the properties of an existing custom collection, such as title, description, image, or sort order of products.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_collection_id | string | yes | The unique identifier of the custom collection to update. |
No output schema declared.
No examples provided.
update_customer Update Customer ~61
Updates an existing customer's information in Shopify. Modify customer details such as name, email, phone, and other profile attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The unique identifier of the customer to update. This ID is required to specify which customer record should be modified. |
No output schema declared.
No examples provided.
update_customer_address Update Customer Address ~69
Updates an existing address for a customer. Provide the customer ID and address ID to modify the address details.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | string | yes | The unique identifier of the specific address to update for the customer. |
| customer_id | string | yes | The unique identifier of the customer whose address is being updated. |
No output schema declared.
No examples provided.
update_customer_addresses Update Customer Addresses ~110
Perform bulk operations on multiple addresses for a specific customer, such as setting a default address or removing addresses in batch.
| Name | Type | Req | Description |
|---|---|---|---|
| address_ids | integer | – | Array of address IDs to include in the bulk operation. The order may be significant depending on the operation type. |
| customer_id | string | yes | The unique identifier of the customer whose addresses will be modified. |
| operation | string | – | The type of bulk operation to perform on the specified addresses (e.g., set as default, delete, or activate). |
No output schema declared.
No examples provided.
update_customer_saved_search Update Customer Saved Search ~83
Updates an existing customer saved search with new criteria or settings. This allows modification of a previously created saved search that customers can use to filter and organize customer data.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_saved_search_id | string | yes | The unique identifier of the customer saved search to update. This ID is returned when the saved search is created and is required to target the correct search for modification. |
No output schema declared.
No examples provided.
update_discount_code Update Discount Code ~77
Updates an existing discount code associated with a price rule. Modify discount code properties such as code value, usage limits, and other configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| discount_code_id | string | yes | The unique identifier of the discount code to update. |
| price_rule_id | string | yes | The unique identifier of the price rule that contains the discount code being updated. |
No output schema declared.
No examples provided.
update_fulfillment Update Fulfillment ~68
Update fulfillment details for a specific order, such as tracking information, status, or line items included in the shipment.
| Name | Type | Req | Description |
|---|---|---|---|
| fulfillment_id | string | yes | The unique identifier of the fulfillment to update. |
| order_id | string | yes | The unique identifier of the order containing the fulfillment to update. |
No output schema declared.
No examples provided.
update_fulfillment_service Update Fulfillment Service ~52
Update the configuration and settings of an existing fulfillment service, such as its name, callback URLs, or tracking capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| fulfillment_service_id | string | yes | The unique identifier of the fulfillment service to update. |
No output schema declared.
No examples provided.
update_fulfillment_tracking Update Fulfillment Tracking ~53
Updates the tracking information for a fulfillment, allowing you to modify shipment tracking details after the fulfillment has been created.
| Name | Type | Req | Description |
|---|---|---|---|
| fulfillment_id | string | yes | The unique identifier of the fulfillment whose tracking information should be updated. |
No output schema declared.
No examples provided.
update_gift_card Update Gift Card ~55
Updates an existing gift card's expiry date, note, and template suffix. The gift card's balance cannot be modified through the API.
| Name | Type | Req | Description |
|---|---|---|---|
| gift_card_id | string | yes | The unique identifier of the gift card to update. |
No output schema declared.
No examples provided.
update_inventory_item Update Inventory Item ~72
Updates an existing inventory item in your store's inventory system. Use this to modify properties like SKU, tracked status, or other inventory attributes for a specific item.
| Name | Type | Req | Description |
|---|---|---|---|
| inventory_item_id | string | yes | The unique identifier of the inventory item to update. This ID is assigned by Shopify when the inventory item is created. |
No output schema declared.
No examples provided.
update_metafield Update Metafield ~73
Updates an existing metafield by ID. Modify metafield properties such as namespace, key, value, and type.
| Name | Type | Req | Description |
|---|---|---|---|
| metafield_id | string | yes | The unique identifier of the metafield to update. This ID is returned when a metafield is created and is required to target the specific metafield for modification. |
No output schema declared.
No examples provided.
update_order_risk Update Order Risk ~73
Updates an existing order risk for a specific order. Note that you cannot modify an order risk that was created by another application.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The unique identifier of the order containing the risk to be updated. |
| risk_id | string | yes | The unique identifier of the order risk to be updated. |
No output schema declared.
No examples provided.
update_product Update Product ~58
Updates a product's details, variants, images, and SEO metadata. Use metafields_global_title_tag and metafields_global_description_tag to manage SEO title and description tags.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | The unique identifier of the product to update. |
No output schema declared.
No examples provided.
update_product_image Update Product Image ~72
Update metadata and properties of an existing product image, such as alt text, position, or other image attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| image_id | string | yes | The unique identifier of the image within the product to be updated. |
| product_id | string | yes | The unique identifier of the product that contains the image to be updated. |
No output schema declared.
No examples provided.
update_recurring_application_charge_capped_amount Update Recurring Application Charge Capped Amount ~106
Updates the capped amount of an active recurring application charge. This allows you to modify the maximum billing cap for an existing charge without canceling and recreating it.
| Name | Type | Req | Description |
|---|---|---|---|
| recurring_application_charge_id | string | yes | The unique identifier of the recurring application charge to update. This must be an active charge. |
| recurring_application_chargecapped_amount | integer | – | The new maximum billing cap amount for the recurring charge, specified as a monetary value in the store's currency. |
No output schema declared.
No examples provided.
update_redirect Update Redirect ~61
Updates an existing redirect configuration in the online store. Modify redirect rules by specifying the redirect ID and providing updated redirect details.
| Name | Type | Req | Description |
|---|---|---|---|
| redirect_id | string | yes | The unique identifier of the redirect to update. This ID is required to locate and modify the specific redirect rule. |
No output schema declared.
No examples provided.
update_script_tag Update Script Tag ~75
Updates an existing script tag in the online store. Modify script tag properties such as source URL, event triggers, or display scope.
| Name | Type | Req | Description |
|---|---|---|---|
| script_tag_id | string | yes | The unique identifier of the script tag to update. This ID is returned when the script tag is created and is required to target the correct script tag for modification. |
No output schema declared.
No examples provided.
update_smart_collection Update Smart Collection ~51
Updates an existing smart collection by ID. Modify collection properties such as title, rules, sorting, and visibility settings.
| Name | Type | Req | Description |
|---|---|---|---|
| smart_collection_id | string | yes | The unique identifier of the smart collection to update. |
No output schema declared.
No examples provided.
update_smart_collection_order Update Smart Collection Order ~127
Updates the sorting configuration for products in a smart collection, allowing you to manually order specific products at the top or apply an automatic sort order.
| Name | Type | Req | Description |
|---|---|---|---|
| products | – | – | An ordered array of product IDs to pin at the top of the collection. Pass an empty array to clear any previously pinned products and return to automatic sorting. |
| smart_collection_id | string | yes | The unique identifier of the smart collection to update. |
| sort_order | – | – | The automatic sorting method to apply to the collection (e.g., alphabetical, price, newest). If not specified, the current sort order is preserved. |
No output schema declared.
No examples provided.
What is the com.mcparmory/shopify-admin MCP server?
com.mcparmory/shopify-admin is an MCP server listed in the public MCP registry as com.mcparmory/shopify-admin. Manage products, orders, customers, inventory, and store configuration. This page covers its PyPI package (mcparmory-shopify-admin).
Is the com.mcparmory/shopify-admin MCP server safe to use?
com.mcparmory/shopify-admin scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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/shopify-admin MCP server expose?
com.mcparmory/shopify-admin exposes 177 tools: list_application_charges, get_application_charge, list_application_credits, get_application_credit, list_article_authors, and 172 more. Their descriptions and schemas cost roughly 14,807 tokens of context every time the server is loaded.
Is the com.mcparmory/shopify-admin MCP server still maintained?
com.mcparmory/shopify-admin 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.