# Ship Check (remote · uxcontinuum.com)

Scan a deployed app URL for exposed keys, open Supabase tables and missing security headers.

- Trust score: 75/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `uxcontinuum.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-uxcontinuum-ship-check/api-mcp.md), [page](https://verifymcp.io/servers/com-uxcontinuum-ship-check/api-mcp)

## Channel facts

- Endpoint: `https://uxcontinuum.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
  - Structured output schemas are declared (27% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-uxcontinuum-ship-check 'https://uxcontinuum.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-uxcontinuum-ship-check": {
      "url": "https://uxcontinuum.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-uxcontinuum-ship-check": {
      "type": "http",
      "url": "https://uxcontinuum.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-uxcontinuum-ship-check]
url = "https://uxcontinuum.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-uxcontinuum-ship-check": {
      "type": "remote",
      "url": "https://uxcontinuum.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-uxcontinuum-ship-check --url 'https://uxcontinuum.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-uxcontinuum-ship-check:
    url: "https://uxcontinuum.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-uxcontinuum-ship-check": {
      "Transport": "http",
      "Url": "https://uxcontinuum.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-uxcontinuum-ship-check -t streamable-http -u 'https://uxcontinuum.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-uxcontinuum-ship-check": {
      "type": "http",
      "url": "https://uxcontinuum.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 75, +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.

### 2026-10-15 (score 74, +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.

### 2026-10-14 (score 73, 0)

- [security] Tool “ship_check” rewrote its description, which is the text the model reads

### 2026-10-13 (score 73, +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.

### 2026-10-12 (score 72, +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.

### 2026-10-10 (score 71, +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.

### 2026-10-07 (score 70)

First indexed and scored.

## MCP tools (11)

### `ship_check` (~459 tokens)

Ship Check: scan a deployed app

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.

Input parameters:

- `fresh` (boolean): Skip the 24h cache and scan again (use after deploying a fix).
- `url` (string, required): The live, publicly reachable URL of the deployed app, e.g. https://my-app.lovable.app. A bare domain gets https://.

Output parameters:

- `cached` (boolean)
- `counts` (object)
- `findings` (array)
- `human_review` (object)
- `limitations` (string)
- `overall_status` (string)
- `report_url` (string|null)
- `scan_id` (string|null): Pass to request_human_review. Null if the result could not be stored.
- `scanned_at` (string)
- `score` (number): 0-100. Each red finding costs 30 points, each yellow 10.
- `summary` (string)
- `url` (string)
- `verdict` (string)

### `request_human_review` (~153 tokens)

Request a human review ($299)

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.

Input parameters:

- `email` (string, required): The user's email, for the checkout and for Matt to reply to.
- `scan_id` (string, required): The scan_id returned by ship_check.

Output parameters:

- `booking_url` (string): Book a 30-minute call with Matt instead of, or before, paying.
- `checkout_url` (string|null): Stripe Checkout for the human review. The user opens and pays it themselves.
- `price` (string)
- `report_url` (string|null)
- `scan_id` (string)
- `url` (string)
- `what_happens_next` (array)

### `leak_check` (~89 tokens)

Leak Check (older name for ship_check)

Older name for ship_check, kept for existing callers. Same scan, same input, same result. Prefer ship_check.

Input parameters:

- `fresh` (boolean): Skip the 24h cache and scan again (use after deploying a fix).
- `url` (string, required): The live, publicly reachable URL of the deployed app, e.g. https://my-app.lovable.app. A bare domain gets https://.

Output parameters:

- `cached` (boolean)
- `counts` (object)
- `findings` (array)
- `human_review` (object)
- `limitations` (string)
- `overall_status` (string)
- `report_url` (string|null)
- `scan_id` (string|null): Pass to request_human_review. Null if the result could not be stored.
- `scanned_at` (string)
- `score` (number): 0-100. Each red finding costs 30 points, each yellow 10.
- `summary` (string)
- `url` (string)
- `verdict` (string)

### `cursor_auto_cost_estimate` (~90 tokens)

Cursor Auto vs pinned model cost

Estimate Cursor Auto blended cost versus pinning a single model.

Input parameters:

- `autoModelMix` (object, required): Map of model id to weight, must sum to 1
- `avgInputTokens` (number, required)
- `avgOutputTokens` (number, required)
- `pinnedModelId` (string, required)
- `requestsPerDay` (number, required)
- `workDaysPerMonth` (number, required)

### `swarm_run_cost_estimate` (~113 tokens)

Multi-agent swarm run cost

Estimate the cost of a multi-agent orchestrator plus sub-agent swarm run.

Input parameters:

- `orchestratorInputTokens` (number, required)
- `orchestratorModelId` (string, required)
- `orchestratorOutputTokens` (number, required)
- `retryRatePct` (number, required)
- `runsPerDay` (number, required)
- `subAgentCount` (number, required)
- `subAgentInputTokens` (number, required)
- `subAgentModelId` (string, required)
- `subAgentOutputTokens` (number, required)

### `agent_cost_estimate` (~80 tokens)

Agent cost per shipped task

Estimate blended cost per shipped task for a month of agent runs, given a retry rate.

Input parameters:

- `avgCostPerTask` (number, required)
- `modelId` (string): Model id to scale avgCostPerTask by, defaults to sonnet-5
- `retryRatePct` (number, required)
- `runsPerMonth` (number, required)

### `list_services` (~68 tokens)

Continuum services and prices

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.

### `get_availability` (~205 tokens)

Get open call times with Matt

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.

Input parameters:

- `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.

### `book_call` (~244 tokens)

Book a call with Matt

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.

Input parameters:

- `email` (string, required): The user's own email; the invite goes there.
- `event` (string)
- `name` (string, required): The user's name.
- `notes` (string): What the user wants to discuss, up to 1000 characters.
- `start` (string, required): Slot start from get_availability, ISO 8601 with Z or an offset, e.g. 2026-10-05T15:00:00Z.
- `timezone` (string, required): The user's IANA time zone, e.g. America/New_York.

### `send_message` (~176 tokens)

Send Matt a message

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.

Input parameters:

- `company` (string): Company or project name.
- `email` (string, required): The user's own email, for Matt to reply to.
- `message` (string, required): The message, 10 to 4000 characters.
- `name` (string, required): The user's name.
- `topic` (string): Short subject, e.g. "rescue a Lovable app".

### `request_estimate` (~246 tokens)

Request a project estimate

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.

Input parameters:

- `budget` (string)
- `email` (string, required): The user's own email, for Matt's quote.
- `name` (string, required): The user's name.
- `project_description` (string, required): 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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-uxcontinuum-ship-check/api-mcp#diagnostics

## Score history

- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 73
- 2026-10-13: 73
- 2026-10-12: 72
- 2026-10-10: 71
- 2026-10-07: 70

## Common questions

### 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.

## Links

- Remote endpoint: https://uxcontinuum.com/api/mcp
- Website: https://uxcontinuum.com/ship-check
- Changelog RSS feed: https://verifymcp.io/servers/com-uxcontinuum-ship-check/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-uxcontinuum-ship-check/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-uxcontinuum-ship-check/api-mcp