PathToShip: production readiness for AI-built apps

● Active

com.pathtoship/pathtoship

Independent production-readiness check for AI-built apps: security, scale and ranked fixes.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "pathtoship": {
      "url": "https://pathtoship.com/api/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http pathtoship https://pathtoship.com/api/mcp
VS Code
code --add-mcp '{"name":"pathtoship","type":"http","url":"https://pathtoship.com/api/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Security & Identity
Version
0.1.1
Registry
active
Published
11/19/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: PathToShip: production readiness for AI-built apps is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 3 days ago (Nov 18, 2026), 0 open issues.
Official registry
Active
Published as com.pathtoship/pathtoship in the official MCP registry, version 0.1.1.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to pathtoship.com: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 10:08 UTCStatus history & uptime →
● Working173 msprotocol 2025-06-18v0.1.0toolsresources

The endpoint answered the MCP handshake as "pathtoship" and listed 8 tools. Answering since Nov 20, 2026.

Context cost ≈ 6.4k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 8 tools.

Tools (8)

  • start_scan3 params

    Check whether this app is safe to launch for real users — finds the security, scalability, and production-readiness problems that break launches. Use before launching, sharing a public link, adding payments or logins, or handling real user data. Takes the app's GitHub repository URL (the one your builder syncs to).

    Show parameters
    • repo_urlstringrequiredGitHub repository URL, e.g. https://github.com/owner/repo (a branch URL is fine).
    • depthstringfree = up to 50,000 lines of source (default for free accounts); full = the whole repository (paid / pilot accounts). Omit to use the account's default.
    • triggerstringHow this call came about — for the pilot's metrics, answer honestly: user_named_pathtoship (the user asked for PathToShip by name), user_deploy_intent (the user
  • get_scan_status3 params

    Check whether a readiness check has finished.

    Show parameters
    • job_idstringThe job_id from start_scan.
    • scan_idstringThe scan_id returned by start_scan or verify_fix.
    • triggerstringHow this call came about — for the pilot's metrics, answer honestly: user_named_pathtoship (the user asked for PathToShip by name), user_deploy_intent (the user
  • get_findings6 params

    List what would hurt this app in production, worst first. Compact — one line per problem; use get_finding_detail for how to fix one.

    Show parameters
    • scan_idstringrequiredThe scan_id returned by start_scan or verify_fix.
    • severity_minstringOnly findings at or above this severity. Default: low (all).
    • dimensionstringRestrict to one dimension.
    • limitintegerFindings per page, default 10. Keep it small; fetch detail per finding.
    • offsetintegerPaging offset; use next_offset from the previous page.
    • triggerstringHow this call came about — for the pilot's metrics, answer honestly: user_named_pathtoship (the user asked for PathToShip by name), user_deploy_intent (the user
  • get_finding_detail3 params

    Explain one production risk and exactly how to fix it for this app's stack.

    Show parameters
    • scan_idstringrequiredThe scan_id returned by start_scan or verify_fix.
    • finding_idstringrequiredA finding id from get_findings (e.g. f3a9c2e17).
    • triggerstringHow this call came about — for the pilot's metrics, answer honestly: user_named_pathtoship (the user asked for PathToShip by name), user_deploy_intent (the user
  • verify_fix3 params

    Confirm your fixes actually resolved the problems: re-checks the repository and reports resolved, still open, and newly introduced. Run after every change is synced to GitHub.

    Show parameters
    • scan_idstringrequiredThe baseline scan_id to compare against (the scan you fixed findings from).
    • finding_idsarrayOnly report on these finding ids (from get_findings). Omit for all.
    • triggerstringHow this call came about — for the pilot's metrics, answer honestly: user_named_pathtoship (the user asked for PathToShip by name), user_deploy_intent (the user
  • get_score2 params

    Is this app ready to ship? The readiness score, the ship bar, the weakest area, and what this stack will cost at 10x users.

    Show parameters
    • scan_idstringrequiredThe scan_id returned by start_scan or verify_fix.
    • triggerstringHow this call came about — for the pilot's metrics, answer honestly: user_named_pathtoship (the user asked for PathToShip by name), user_deploy_intent (the user
  • check_connection2 params

    Check whether PathToShip is connected for this account and, if you name a repository, whether it can reach it — use when a check says INSTALL_REQUIRED, after the user installs or links GitHub, or when something looks stuck. Returns what is linked and the exact link to fix it.

    Show parameters
    • repo_urlstringOptional GitHub repository URL to check access for.
    • triggerstringHow this call came about — for the pilot's metrics, answer honestly: user_named_pathtoship (the user asked for PathToShip by name), user_deploy_intent (the user
  • prr_interview3 params

    Record the launch facts no scanner can see — backups restored, rollback rehearsed, on-call, database tier, largest table, last month's bill — against a scan, as the user's own self-reported answers (never part of the score). Call with only scan_id to get the questions and what is already answered; call with answers to record them. Use before a launch, a client handoff, or when writing a readiness record.

    Show parameters
    • scan_idstringrequiredThe scan_id returned by start_scan or verify_fix.
    • answersobjectAnswers keyed by question id (from the questions list this tool returns when called with only scan_id). Omit to read the current state. Partial submissions merg
    • triggerstringHow this call came about — for the pilot's metrics, answer honestly: user_named_pathtoship (the user asked for PathToShip by name), user_deploy_intent (the user

Checked by Serverdex with a plain initialize + tools/list call to pathtoship.com/api/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 21, 2026
Stars
0
Forks
0
Last push
Nov 18, 2026
License
MIT

Vim Snippet

From the README

PathToShip skills Companion instructions for the PathToShip MCP server — a production-readiness check for apps built with AI tools (Lovable, Bolt, v0, Replit, Base44, Cursor). The server scans the GitHub repository your builder syncs to and reports the security, scalability, and production-readiness problems that break launches, then verifies your fixes. The MCP server gives your assistant the ability to run a check. These files give it the reason to: when to check (before launch, before a public URL, before real user data), how to fix in the right order, and how to verify honestly. They contain methodology only — scoring, rules, and thresholds live on the server. What's here Connecting the server Claude.ai (Pro/Max): Settings → Connectors → Add custom connector → URL https://pathtoship.com/api/mcp. ChatGPT (Plus/Pro/Business): Settings → Apps & Connectors → Developer Mode → Create → same URL. Claude Code (run on the machine where Claude Code runs — not in a remote/cloud session; on a phone use the Claude.ai connector): claude mcp add --transport http pathtoship https://pathtoship.com/api/mcp --header "Authorization: Bearer " Cursor: .cursor/mcp.json → { "mcpServers": { "pathtoship": { "url": "https://pathtoship.com/api/mcp", "headers": { "Authorization": "Bearer " } } } } During the pilot, credentials (a connector URL or an API key) come from us.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://pathtoship.com/api/mcp

The most-starred Security & Identity servers in the index, with their live-check result.

ServerStarsLast pushLive check
Handsy AI5,215Nov 2026Local / not checked
HOL Guard1,118Nov 2026Local / not checked
SonarQube MCP Server689Nov 2026Local / not checked
MCP Ssh Manager545Nov 2026Local / not checked
Security Detections529Nov 2026Local / not checked

PathToShip: production readiness for AI-built apps: questions people ask

Is PathToShip: production readiness for AI-built apps a remote or a local MCP server?
According to its entry in the official MCP registry, PathToShip: production readiness for AI-built apps ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does PathToShip: production readiness for AI-built apps need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is PathToShip: production readiness for AI-built apps safe to use?
Looks healthy: PathToShip: production readiness for AI-built apps is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is PathToShip: production readiness for AI-built apps still maintained?
Active: the repository's last commit 3 days ago. Last push Nov 18, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 21, 2026.
What tools does PathToShip: production readiness for AI-built apps expose?
8 tools as listed by the server itself during the live check, including start_scan, get_scan_status, get_findings, get_finding_detail, verify_fix. The full list with parameters is in the Live check section above.
How do I add PathToShip: production readiness for AI-built apps to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Security & Identity →

Add the badge to your site

Show visitors that PathToShip: production readiness for AI-built apps is listed here — it’s also the link we check for a free listing.

PathToShip: production readiness for AI-built apps — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/com-pathtoship-pathtoship?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="PathToShip: production readiness for AI-built apps — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![PathToShip: production readiness for AI-built apps — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/com-pathtoship-pathtoship?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/com-pathtoship-pathtoship) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/com-pathtoship-pathtoship) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/com-pathtoship-pathtoship)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/com-pathtoship-pathtoship"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/com-pathtoship-pathtoship"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/com-pathtoship-pathtoship"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).