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.

Shipstry Launch Data

REMOTE · SHIPSTRY.COM

Weekly product launch data from Shipstry: launches, winners, and category benchmarks.

Available components

69 Trust /100

Last scanned (23 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Search and Retrieval

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 Security74
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 952 tokens (~136/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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 65% of tool parameters carry a description.Partial
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 current MCP spec version (2026-07-28).Pass
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.

  • 17 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Oct 26 69

    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 17 Oct 2026 · Probed https://shipstry.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=shipstry.com CN=WE1,O=Google Trust Services,C=US 4 Sept 2026 3 Dec 2026 ECDSA 256 ECDSA-SHA256 1baf20d2df0f548813c32e1fa2f901f6
SANs: shipstry.com, dev.shipstry.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of shipstry.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
shipstry.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://shipstry.com/mcp Verified 200
http (plaintext) http://shipstry.com/mcp HTTPS enforced 301 https://shipstry.com/mcp
MCP tools · 7 exposed · ~809 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
check_url ~42

Check whether a website URL is already listed on Shipstry, using the same normalization as submission duplicate detection. Only approved listings are visible.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

get_category_landscape ~153

Benchmark a category over a window of ship weeks: how many products launched, the vote distribution (mean, p50, p75, p90, max), the top launches, how many medals were awarded, and the tags that appear most. Use this to judge how crowded a space is and what a winning launch looks like there.

NameTypeReqDescription
categorystringyesCategory slug. One of: developer-tools, design-tools, marketing-sales, finance, education, health-wellness, social, ecommerce, entertainment, ai-ml, travel, productivity, data-analytics, web3, securi…
weeksinteger–How many ship weeks back to include.

No output schema declared.

No examples provided.

get_launch ~94

Fetch one approved launch with its description, tags, awards, and maker name. Identify it by Shipstry product id, product slug, its Shipstry URL, or its own website URL.

NameTypeReqDescription
idstring–Shipstry product id. Every result returned by the other tools includes one.
slugstring––
urlstring–Either the Shipstry product URL or the product's own website URL.

No output schema declared.

No examples provided.

get_winners ~99

Weekly or monthly medal winners (gold, silver, bronze). Returns the most recent periods by default, or one period when `period` is given. Use this to see what actually won, not just what launched.

NameTypeReqDescription
limitinteger––
periodstring–Award period: YYYYMMDD for weeks, YYYY-MM for months. Omit for the most recent periods.
scopestring–Weekly or monthly award periods.

No output schema declared.

No examples provided.

list_categories ~38

List Shipstry's product categories with the number of approved products in each. Call this first when you need a valid category slug for the other tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_ship_week ~182

List the products that launched in one ship week (Monday-Sunday UTC, keyed YYYYMMDD). Defaults to the current week. During Fog Mode vote counts for the current week are hidden and the order is random.

NameTypeReqDescription
categorystring–Filter to one category. One of: developer-tools, design-tools, marketing-sales, finance, education, health-wellness, social, ecommerce, entertainment, ai-ml, travel, productivity, data-analytics, web…
limitinteger––
offsetinteger––
shipWeekstring–Monday of the week in YYYYMMDD form, for example '20260907'. Defaults to the current ship week.
sortstring–Vote order is forced to random while Fog Mode hides the current week's ranking.

No output schema declared.

No examples provided.

search_launches ~201

Search approved Shipstry launches by keyword, category, or tag. Keyword matching covers product name and tagline. Returns compact records with votes, ship week, awards, and the canonical Shipstry URL.

NameTypeReqDescription
categorystring–Category slug. One of: developer-tools, design-tools, marketing-sales, finance, education, health-wellness, social, ecommerce, entertainment, ai-ml, travel, productivity, data-analytics, web3, securi…
limitinteger––
offsetinteger––
querystring–Keyword matched against product name and tagline.
sortstring–hot = all-time by votes, new = newest first, week = launched in the current ship week, month = launched this month.
tagstring–Tag slug, for example 'vpn' or 'beta'. See get_category_landscape for tags common in a category.

No output schema declared.

No examples provided.

Install

How do I install the Shipstry Launch Data MCP server?

Shipstry Launch Data is a hosted endpoint at https://shipstry.com/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 · shipstry.com

# add to Claude Code
claude mcp add --transport http com-shipstry-launch-data 'https://shipstry.com/mcp'
Common questions

What is the Shipstry Launch Data MCP server?

Shipstry Launch Data is an MCP server listed in the public MCP registry as com.shipstry/launch-data. Weekly product launch data from Shipstry: launches, winners, and category benchmarks. This page covers its hosted endpoint (https://shipstry.com/mcp).

Is the Shipstry Launch Data MCP server safe to use?

Shipstry Launch Data scores 69 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 Shipstry Launch Data MCP server expose?

Shipstry Launch Data exposes 7 tools: list_categories, search_launches, get_launch, list_ship_week, get_winners, and 2 more. Their descriptions and schemas cost roughly 809 tokens of context every time the server is loaded.

Does the Shipstry Launch Data MCP server require authentication?

No. We connected to Shipstry Launch Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Shipstry Launch Data MCP server still maintained?

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