Ship Check
REMOTE · UXCONTINUUM.COM
Scan a deployed app URL for exposed keys, open Supabase tables and missing security headers.
Available components
Last scanned (1 hour ago)
Scores higher than 68% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Security
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2121 tokens (~192/item across 11 items; 11 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 Management37
- Stability observed for 11 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
- 57% of tool parameters carry a description.Partial
- Structured output schemas are declared (27% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 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
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 0
- Tool “ship_check” rewrote its description, which is the text the model reads security
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 13. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 70
First indexed and scored.
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://uxcontinuum.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=uxcontinuum.com | CN=YR1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | RSA 2048 | SHA256-RSA | 6be02fc808838c52d79634d0a3f2d177c9a |
| SANs: uxcontinuum.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of uxcontinuum.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| uxcontinuum.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://uxcontinuum.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://uxcontinuum.com/api/mcp | HTTPS enforced | 308 | https://uxcontinuum.com/api/mcp |
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 →
agent_cost_estimate Agent cost per shipped task ~80
Estimate blended cost per shipped task for a month of agent runs, given a retry rate.
| Name | Type | Req | Description |
|---|---|---|---|
| avgCostPerTask | number | yes | – |
| modelId | string | – | Model id to scale avgCostPerTask by, defaults to sonnet-5 |
| retryRatePct | number | yes | – |
| runsPerMonth | number | yes | – |
No output schema declared.
No examples provided.
book_call Book a call with Matt ~244
Book a free 30-minute intro call with Matt Turley (Continuum) directly on his calendar. The booking is confirmed immediately and Cal.com emails the invite to the user and to Matt. First call get_availability and pass the exact start of an open slot. Only book when the user has asked for the call and agreed to the time; pass their real name, email and time zone. notes: a short, factual summary of what the user wants to discuss (shown to Matt). Returns the booking id, meeting link and reschedule/cancel links. Limit 2 upcoming calls per email.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's own email; the invite goes there. | |
| event | string | – | – |
| name | string | yes | The user's name. |
| notes | string | – | What the user wants to discuss, up to 1000 characters. |
| start | string | yes | Slot start from get_availability, ISO 8601 with Z or an offset, e.g. 2026-10-05T15:00:00Z. |
| timezone | string | yes | The user's IANA time zone, e.g. America/New_York. |
No output schema declared.
No examples provided.
cursor_auto_cost_estimate Cursor Auto vs pinned model cost ~90
Estimate Cursor Auto blended cost versus pinning a single model.
| Name | Type | Req | Description |
|---|---|---|---|
| autoModelMix | object | yes | Map of model id to weight, must sum to 1 |
| avgInputTokens | number | yes | – |
| avgOutputTokens | number | yes | – |
| pinnedModelId | string | yes | – |
| requestsPerDay | number | yes | – |
| workDaysPerMonth | number | yes | – |
No output schema declared.
No examples provided.
get_availability Get open call times with Matt ~205
List open slots for a free 30-minute intro call with Matt Turley (Continuum), read live from his Cal.com calendar. Use it when the user wants to talk to Matt, get help with a project, or book a call, before calling book_call. Window: date_from to date_to (YYYY-MM-DD), at most 14 days; defaults to the next 7 days. Times are returned in the requested timezone (IANA name, default UTC). Read-only: it books nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | First day, YYYY-MM-DD. Default today. |
| date_to | string | – | Last day, YYYY-MM-DD, at most 14 days after date_from. Default date_from + 6 days. |
| event | string | – | Which call. intro-30 = free 30-minute intro call. |
| timezone | string | – | IANA time zone for the returned times, e.g. America/New_York. Default UTC. |
No output schema declared.
No examples provided.
leak_check Leak Check (older name for ship_check) ~89
Older name for ship_check, kept for existing callers. Same scan, same input, same result. Prefer ship_check.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Skip the 24h cache and scan again (use after deploying a fix). |
| url | string | yes | The live, publicly reachable URL of the deployed app, e.g. https://my-app.lovable.app. A bare domain gets https://. |
| Name | Type | Req | Description |
|---|---|---|---|
| cached | boolean | yes | – |
| counts | object | yes | – |
| findings | array | yes | – |
| human_review | object | yes | – |
| limitations | string | yes | – |
| overall_status | string | yes | – |
| report_url | string|null | yes | – |
| scan_id | string|null | yes | Pass to request_human_review. Null if the result could not be stored. |
| scanned_at | string | yes | – |
| score | number | yes | 0-100. Each red finding costs 30 points, each yellow 10. |
| summary | string | yes | – |
| url | string | yes | – |
| verdict | string | yes | – |
No examples provided.
list_services Continuum services and prices ~68
List Continuum service offerings and published prices (the same list as uxcontinuum.com/pricing), plus how to reach Matt: get_availability and book_call to book a free 30-minute call, send_message to send him a note, request_estimate for a ballpark from published pricing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_estimate Request a project estimate ~246
Get a ballpark price for a software project from Continuum's published pricing, and send the request to Matt Turley, who replies personally with a real quote. Use it when the user asks what a build, fix, review, ongoing support or AI-search visibility work would cost. The ballpark is the matching published offer(s) and price range from uxcontinuum.com/pricing, not a quote. Show it to the user labeled that way. Then offer a call: get_availability and book_call.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | – |
| string | yes | The user's own email, for Matt's quote. | |
| name | string | yes | The user's name. |
| project_description | string | yes | What the user wants built or fixed, 10 to 4000 characters. |
| project_type | string | – | launch-review (check an app before launch), fix-existing-app (stabilize or rescue an app), new-build (MVP from scratch), ongoing-support (maintenance or a product team on retainer), ai-visibility (ge… |
| timeline | string | – | – |
No output schema declared.
No examples provided.
request_human_review Request a human review ($299) ~153
Get a senior engineer (Matt Turley, 20 years shipping software) to review by hand the app behind a ship_check scan: the paid $299 Ship Check. Returns a Stripe Checkout link and a call booking link for the user to open themselves. This call charges nothing and never pays on the user's behalf. Only call it when the user asks for a human review or agrees to one. Pass the user's own email so Matt can follow up personally; no automated email is sent to it. Show the user checkout_url and booking_url.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's email, for the checkout and for Matt to reply to. | |
| scan_id | string | yes | The scan_id returned by ship_check. |
| Name | Type | Req | Description |
|---|---|---|---|
| booking_url | string | yes | Book a 30-minute call with Matt instead of, or before, paying. |
| checkout_url | string|null | yes | Stripe Checkout for the human review. The user opens and pays it themselves. |
| price | string | yes | – |
| report_url | string|null | yes | – |
| scan_id | string | yes | – |
| url | string | yes | – |
| what_happens_next | array | yes | – |
No examples provided.
send_message Send Matt a message ~176
Send a message to Matt Turley (Continuum) on the user's behalf, like the contact form on uxcontinuum.com. Use it when the user wants to ask Matt something or describe a project but not book a call yet. Only send what the user asked to send, with their real name and email. Matt reads it and replies personally by email; no automated reply is sent. For a time to talk, use get_availability and book_call instead.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company or project name. |
| string | yes | The user's own email, for Matt to reply to. | |
| message | string | yes | The message, 10 to 4000 characters. |
| name | string | yes | The user's name. |
| topic | string | – | Short subject, e.g. "rescue a Lovable app". |
No output schema declared.
No examples provided.
ship_check Ship Check: scan a deployed app ~459
Before shipping, or right after deploying, an app built with Lovable, Bolt, Cursor, v0, Replit, Claude Code or similar, run ship_check on the live URL. It scans the deployed app from the outside, the way a visitor or attacker sees it, and returns a launch-readiness report where every finding has a status and a concrete fix. Checks: (1) secret keys exposed in the HTML and the same-origin JS bundles it ships (Stripe live secret and restricted keys, AWS access keys, OpenAI and Anthropic API keys, Supabase secret and service_role keys, hardcoded bearer tokens and passwords); (2) open database access: if the page ships a Supabase URL and public anon or publishable key, whether the common tables profiles and users return rows to that key without login (a missing Row Level Security policy; count only, no row data is read); (3) missing security headers (Strict-Transport-Security, Content-Security-Policy, X-Frame-Options or frame-ancestors, X-Content-Type-Options, Referrer-Policy); (4) HTTPS, reachability and server errors; (5) broken internal links (spot-check of up to 6); (6) server response time; (7) whether login/signup and pricing/checkout are linked from the homepage; (8) whether AI search crawlers get real server-rendered content or an empty JavaScript shell. Read-only: plain GET/HEAD requests, never logs in, never submits forms, never writes. Not a code audit: it cannot see source code or test every table or route. Results are cached for 24 hours per URL; pass fresh=true to re-scan after deploying a fix. Only scan apps the user owns or is authorized to test. If the user wants a senior engineer to review the app by hand ($299), call request_human_review with the scan_id from this result.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Skip the 24h cache and scan again (use after deploying a fix). |
| url | string | yes | The live, publicly reachable URL of the deployed app, e.g. https://my-app.lovable.app. A bare domain gets https://. |
| Name | Type | Req | Description |
|---|---|---|---|
| cached | boolean | yes | – |
| counts | object | yes | – |
| findings | array | yes | – |
| human_review | object | yes | – |
| limitations | string | yes | – |
| overall_status | string | yes | – |
| report_url | string|null | yes | – |
| scan_id | string|null | yes | Pass to request_human_review. Null if the result could not be stored. |
| scanned_at | string | yes | – |
| score | number | yes | 0-100. Each red finding costs 30 points, each yellow 10. |
| summary | string | yes | – |
| url | string | yes | – |
| verdict | string | yes | – |
No examples provided.
swarm_run_cost_estimate Multi-agent swarm run cost ~113
Estimate the cost of a multi-agent orchestrator plus sub-agent swarm run.
| Name | Type | Req | Description |
|---|---|---|---|
| orchestratorInputTokens | number | yes | – |
| orchestratorModelId | string | yes | – |
| orchestratorOutputTokens | number | yes | – |
| retryRatePct | number | yes | – |
| runsPerDay | number | yes | – |
| subAgentCount | number | yes | – |
| subAgentInputTokens | number | yes | – |
| subAgentModelId | string | yes | – |
| subAgentOutputTokens | number | yes | – |
No output schema declared.
No examples provided.
How do I install the Ship Check MCP server?
Ship Check is a hosted endpoint at https://uxcontinuum.com/api/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 · uxcontinuum.com
claude mcp add --transport http com-uxcontinuum-ship-check 'https://uxcontinuum.com/api/mcp'
What is the Ship Check MCP server?
Ship Check is an MCP server listed in the public MCP registry as com.uxcontinuum/ship-check. Scan a deployed app URL for exposed keys, open Supabase tables and missing security headers. This page covers its hosted endpoint (https://uxcontinuum.com/api/mcp).
Is the Ship Check MCP server safe to use?
Ship Check scores 75 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 Ship Check MCP server expose?
Ship Check exposes 11 tools: ship_check, request_human_review, leak_check, cursor_auto_cost_estimate, swarm_run_cost_estimate, and 6 more. Their descriptions and schemas cost roughly 1,923 tokens of context every time the server is loaded.
Does the Ship Check MCP server require authentication?
No. We connected to Ship Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ship Check MCP server still maintained?
Ship Check 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.