Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Dropify

REMOTE · PRODUCTION.DROPIFY.CLOUD · 2 COMPONENTS

The hub for official-store product data: prices, stock and restocks on 500k+ merch products.

78 Trust /100

Last scanned (22 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1010 tokens (~144/item across 7 items; 7 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 Management7
  • Stability observed for 2 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 19 Nov 26 +41
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
  • 18 Nov 26 36

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://production.dropify.cloud/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=production.dropify.cloud CN=YE1,O=Let's Encrypt,C=US 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA384 557053f3affdc0498eaf26b1869bb627058
SANs: production.dropify.cloud
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of production.dropify.cloud. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cloud. DS published 7041 13 Verified
dropify.cloud. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="dropify"

Bearer realm="dropify"
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self';script-src 'self';style-src 'self' 'unsafe-inline';img-src 'self' data: https:;connect-src 'self' wss: https:;frame-src 'none';frame-ancestors 'none';object-src 'none';base-uri 'self';font-src 'self' https: data:;form-action 'self';script-src-attr 'none';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://production.dropify.cloud/api/v1/mcp Verified 200
http (plaintext) http://production.dropify.cloud/api/v1/mcp HTTPS enforced 308 https://production.dropify.cloud/api/v1/mcp
MCP tools · 7 exposed · ~868 tokens

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 →

Tool Tokens
get_product ~75

Returns one product by id. Each variant, such as a size, has its own price, stock and quantity. Use it after a list or search when you need stock by size. Quantity is null unless the store's count is known.

NameTypeReqDescription
idstringyesA product id from list_products, search_products or recent_changes.

No output schema declared.

No examples provided.

list_artists ~112

Lists the artists and brands this token reads, ordered by popularity, then name. Each has an id, slug, category, image, Dropify page and store count. Use it to find an artist's id or slug before you filter other tools.

NameTypeReqDescription
limitinteger–How many to return, 1 to 100. Default 20.
offsetinteger–How many to skip, for paging.
querystring–Part of an artist or brand name, in any case.

No output schema declared.

No examples provided.

list_products ~143

Lists products, newest first, with name, price, currency, stock, image and store link. Filter by artist, store or stock. Pass nextCursor back as cursor for the next page. Use search_products when you have words to match.

NameTypeReqDescription
artiststring–An artist id or slug from list_artists.
cursorstring–The nextCursor value from the page before.
in_stockboolean–True for in-stock products only, false for sold-out only.
limitinteger–How many to return, 1 to 50. Default 10.
storestring–A store id from list_stores.

No output schema declared.

No examples provided.

list_stores ~114

Lists the stores this token reads, with name, store URL, region, currency and artist. Pass an artist to get only that artist's stores. Regions are US, UK, EU, CA, AU, JP and KR. Use it to find a store id.

NameTypeReqDescription
artiststring–An artist id or slug from list_artists.
limitinteger–How many to return, 1 to 100. Default 20.
offsetinteger–How many to skip, for paging.

No output schema declared.

No examples provided.

my_access ~39

Returns this token's plan and the artists it covers. A null artist list means every artist and store. Call it first to learn what you can read.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recent_changes ~213

Returns the change feed, newest first. It covers restocks, new drops, price drops and rises, sell-outs and stock changes. Each change has its product, store, artist and time. Price and quantity come with their previous values. It returns the last 30 days unless you pass since. Use it for what restocked, dropped or changed price.

NameTypeReqDescription
artiststring–An artist id or slug from list_artists.
cursorstring–The nextCursor value from the page before.
limitinteger–How many to return, 1 to 50. Default 10.
sincestring–Only changes after this ISO-8601 time, like 2026-11-14T00:00:00Z. Default 30 days ago.
storestring–A store id from list_stores.
typestring–One of new, restock, price_drop, price_increase, sold_out, stock_up or stock_down.

No output schema declared.

No examples provided.

search_products ~172

Searches products by word and returns the same fields as list_products. Use it when someone names an item, like a hoodie or a vinyl. Narrow it with artist, store or in_stock. A search across every store ranks by best match. Within an artist or store, results list newest first.

NameTypeReqDescription
artiststring–An artist id or slug from list_artists.
in_stockboolean–True for in-stock products only, false for sold-out only.
limitinteger–How many to return, 1 to 50. Default 10.
offsetinteger–How many to skip, 0 to 200.
querystringyesWords to match, 2 to 100 characters.
storestring–A store id from list_stores.

No output schema declared.

No examples provided.

Install

How do I install the Dropify MCP server?

Dropify is a hosted endpoint at https://production.dropify.cloud/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · production.dropify.cloud

# add to Claude Code
claude mcp add --transport http xozxro-dropify-mcp 'https://production.dropify.cloud/api/v1/mcp'
Common questions

What is the Dropify MCP server?

Dropify is an MCP server listed in the public MCP registry as io.github.xozxro/dropify-mcp. The hub for official-store product data: prices, stock and restocks on 500k+ merch products. This page covers its hosted endpoint (https://production.dropify.cloud/api/v1/mcp).

Is the Dropify MCP server safe to use?

Dropify scores 78 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 Dropify MCP server expose?

Dropify exposes 7 tools: my_access, list_artists, list_stores, list_products, get_product, and 2 more. Their descriptions and schemas cost roughly 868 tokens of context every time the server is loaded.

Does the Dropify MCP server require authentication?

Yes. Dropify asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Dropify MCP server still maintained?

Dropify is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Dropify MCP server?

VerifyMCP ran 13 checks on Dropify, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.