ShipSwift
REMOTE · API.SHIPSWIFT.APP · SCANNED SEP 21
40+ production-ready SwiftUI recipes for building full-stack iOS apps via MCP.
Available components
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
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 4415 tokens (~46/item across 94 items; 3 tools + 91 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the ShipSwift MCP server?
ShipSwift is a hosted endpoint at https://api.shipswift.app/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 · api.shipswift.app
claude mcp add --transport http signerlabs-shipswift 'https://api.shipswift.app/mcp'
{
"mcpServers": {
"signerlabs-shipswift": {
"url": "https://api.shipswift.app/mcp"
}
}
} {
"servers": {
"signerlabs-shipswift": {
"type": "http",
"url": "https://api.shipswift.app/mcp"
}
}
} [mcp_servers.signerlabs-shipswift] url = "https://api.shipswift.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"signerlabs-shipswift": {
"type": "remote",
"url": "https://api.shipswift.app/mcp",
"enabled": true
}
}
} openclaw mcp add signerlabs-shipswift --url 'https://api.shipswift.app/mcp' --transport streamable-http
mcp_servers:
signerlabs-shipswift:
url: "https://api.shipswift.app/mcp" {
"McpServers": {
"signerlabs-shipswift": {
"Transport": "http",
"Url": "https://api.shipswift.app/mcp"
}
}
} assistant mcp add signerlabs-shipswift -t streamable-http -u 'https://api.shipswift.app/mcp'
{
"mcpServers": {
"signerlabs-shipswift": {
"type": "http",
"url": "https://api.shipswift.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 9 Sept 26 0
- Schema quality: excellent → good functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Schema quality: excellent → good functional
- New resource “In-App Subscription with RevenueCat (iOS + Server Gate)” functional
- 9 Aug 26 0
- New resource “TikTok Ad Attribution with RevenueCat (Dual-Channel)” functional
- 3 Aug 26 0
- New resource “Change Effects” functional
- New resource “Particle Transitions” functional
- New resource “View Transitions” functional
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 Sept 2026 · Probed https://api.shipswift.app/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.shipswift.app | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 14 Feb 2026 | 15 Mar 2027 | RSA 2048 | SHA256-RSA | c3fe5aa305472717df6200522cb7c9a |
| SANs: api.shipswift.app, dohlk3ajekx9zm99mekoulpcg0gp4o0.api.shipswift.app | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.shipswift.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| shipswift.app. | 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://api.shipswift.app/mcp | Verified | 200 | |
| http (plaintext) | http://api.shipswift.app/mcp | HTTPS enforced | 301 | https://api.shipswift.app:443/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 →
getRecipe ~72
Get a recipe by ID. Returns complete, copy-paste-ready Swift source code with architecture explanation and implementation steps. Module recipes may also include backend code (Hono/Node.js + AWS CDK).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Recipe ID, e.g. 'animation-shimmer' or 'auth-cognito' |
No output schema declared.
No examples provided.
listRecipes ~121
List production-ready SwiftUI code recipes. Each recipe is a complete, copy-paste-ready implementation — not a tutorial. Covers native iOS features (SwiftUI, Swift Charts, SpriteKit, Vision, AVFoundation, StoreKit 2, NavigationStack) and backend infrastructure (AWS CDK, Hono, Node.js, Cognito, DynamoDB). Categories: animations, charts, UI components, and full-stack modules including auth, camera, subscriptions, chat, and settings.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter recipes by category. Defaults to 'all'. |
No output schema declared.
No examples provided.
searchRecipes ~79
Search recipes by keyword across titles, descriptions, tags, and full source code. Use for any iOS, SwiftUI, or backend topic — e.g. subscription, authentication, camera, animation, chart, onboarding, paywall, infrastructure.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search keyword, e.g. 'shimmer', 'authentication', 'chart' |
No output schema declared.
No examples provided.
What is the ShipSwift MCP server?
ShipSwift is an MCP server listed in the public MCP registry as io.github.signerlabs/shipswift. 40+ production-ready SwiftUI recipes for building full-stack iOS apps via MCP. This page covers its hosted endpoint (https://api.shipswift.app/mcp).
Is the ShipSwift MCP server safe to use?
ShipSwift scores 87 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 ShipSwift MCP server expose?
ShipSwift exposes 3 tools: listRecipes, getRecipe, searchRecipes. Their descriptions and schemas cost roughly 272 tokens of context every time the server is loaded.
Does the ShipSwift MCP server require authentication?
No. We connected to ShipSwift without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ShipSwift MCP server still maintained?
ShipSwift is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.