Skip to content

PathToShip: production readiness for AI-built apps MCP server

com.pathtoship/pathtoshippathtoship.comstreamable-httpv0.1.1Scanned

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

8 tools: 1 can delete or cancel things, 3 change things and 4 only read.

Tools: 1 delete, 0 irreversible, 3 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the PathToShip: production readiness for AI-built apps MCP server can do

The PathToShip: production readiness for AI-built apps MCP server is published by pathtoship.com, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (1 tool: prr_interview) and create or change data (3 tools: start_scan, verify_fix and check_connection). 4 tools only read.

3 tools bring in text other people can write (start_scan, verify_fix and check_connection).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Nov 19, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Deletes or cancels 1Claude Code: deny
  • prr_interviewRecord 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Launch interview
    • readOnlyHint: false
    • openWorldHint: false
    • destructiveHint: true
    • idempotentHint: true
Changes things 3Claude Code: ask
  • check_connectionCheck 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 l…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Connection check
    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
    • idempotentHint: true
  • start_scanCheck whether this app is safe to launch for real users — finds the security, scalability, and production-readiness problems that break launches.Reads text others writeNo findings

    Why it is in this group

    • The name "start_scan" says "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Check app readiness
    • readOnlyHint: false
    • openWorldHint: true
    • destructiveHint: false
    • idempotentHint: false
  • verify_fixConfirm your fixes actually resolved the problems: re-checks the repository and reports resolved, still open, and newly introduced.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Verify fixes
    • readOnlyHint: false
    • openWorldHint: true
    • destructiveHint: false
    • idempotentHint: false
Only reads 4Show 4 read-only tools
  • get_finding_detailExplain one production risk and exactly how to fix it for this app's stack.No findings

    Why it is in this group

    • The name "get_finding_detail" says "get": a word for reading.
    Description, as the server wrote it
    Explain one production risk and exactly how to fix it for this app's stack.

    Annotations the server declares

    • title: Explain a finding
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_findingsList what would hurt this app in production, worst first.No findings

    Why it is in this group

    • The name "get_findings" says "get": a word for reading.
    Description, as the server wrote it
    List what would hurt this app in production, worst first. Compact — one line per problem; use get_finding_detail for how to fix one.

    Annotations the server declares

    • title: List findings
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_scan_statusCheck whether a readiness check has finished.No findings

    Why it is in this group

    • The name "get_scan_status" says "get": a word for reading.
    Description, as the server wrote it
    Check whether a readiness check has finished.

    Annotations the server declares

    • title: Scan status
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_scoreIs this app ready to ship?No findings

    Why it is in this group

    • The name "get_score" says "get": a word for reading.
    Description, as the server wrote it
    Is this app ready to ship? The readiness score, the ship bar, the weakest area, and what this stack will cost at 10x users.

    Annotations the server declares

    • title: Readiness score
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 19, 2026, 17:19 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://pathtoship.com/.well-known/oauth-protected-resource/api/mcp
RFC 9728 protected resource metadata
https://pathtoship.com/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://ouazvgtrwyexcicqskiv.supabase.co/auth/v1
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http pathtoship https://pathtoship.com/api/mcp
claude mcp add --transport http pathtoship https://pathtoship.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pathtoship__get_scan_status",
      "mcp__pathtoship__get_findings",
      "mcp__pathtoship__get_finding_detail",
      "mcp__pathtoship__get_score"
    ],
    "ask": [
      "mcp__pathtoship__start_scan",
      "mcp__pathtoship__verify_fix",
      "mcp__pathtoship__check_connection"
    ],
    "deny": [
      "mcp__pathtoship__prr_interview"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pathtoship. Review it before you use it.

Capability tags behind 3 rules
  • mcp__pathtoship__start_scan untrusted-input
  • mcp__pathtoship__verify_fix untrusted-input
  • mcp__pathtoship__check_connection untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.pathtoship/pathtoship/verify?hash=291c7248593b6f3558be3613b3b9f1bd8264b6018f8fb01aeee4db0248739f34" | jq -e '.changed == false'

Pinned hash 291c7248593b, from Nov 19, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.pathtoship/pathtoship/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.pathtoship/pathtoship
[![Anlyon Radar](https://radar.anlyon.com/badge/com.pathtoship/pathtoship.svg)](https://radar.anlyon.com/servers/com.pathtoship/pathtoship)

Source: MCP Registry · repository. Synced Nov 19, 2026, 21:17 UTC.

PathToShip: production readiness for AI-built apps MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PathToShip: production readiness for AI-built apps MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the PathToShip: production readiness for AI-built apps MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: prr_interview.

Can the PathToShip: production readiness for AI-built apps MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the PathToShip: production readiness for AI-built apps MCP server have?

8 tools: 1 destructive, 3 write, 4 read. prr_interview, start_scan, verify_fix, check_connection, get_scan_status, get_findings, get_finding_detail and get_score.

Does the PathToShip: production readiness for AI-built apps MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the PathToShip: production readiness for AI-built apps MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the PathToShip: production readiness for AI-built apps MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.