@shipstatic/mcp 1.0.0-beta.9 → 1.0.0

package/dist/bin.js

@@ -15,6 +15,7 @@
 import { createRequire } from 'node:module';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
 import Ship from '@shipstatic/ship';
+import { SHIP_ENV } from '@shipstatic/types';
 import { createServer } from './server.js';
 // The executable knows its own manifest; the library it drives does not have
 // to. `createServer` takes the version as an argument precisely so no module
@@ -28,7 +29,7 @@ async function main() {
     // is (`ship-` API key, `deploy-` deploy token, anything else an opaque
     // bearer) and the server classifies it. MCP never has to know which kind it
     // holds.
-    const ship = new Ship({ token: process.env.SHIP_TOKEN });
+    const ship = new Ship({ token: process.env[SHIP_ENV.TOKEN] });
     // No `via` — this executable IS the `mcp` origin, which is the default.
     const server = createServer(ship, { version });
     const transport = new StdioServerTransport();

package/dist/call.d.ts

@@ -1,15 +1,4 @@
 import type { CallToolResult } from '@modelcontextprotocol/sdk/types.js';
-/**
- * The two error arms that earn a hint. Everything else relays verbatim — a
- * hint on any other type sends the agent chasing a credential that is not the
- * problem.
- *
- * They are ARGUMENTS rather than constants because they are the one part of
- * the mapping that legitimately differs per transport: stdio can name the
- * environment variable it owns, and the hosted endpoint deliberately cannot
- * (it has no configuration of its own, and naming another package's variable
- * is how this pair silently desynchronised once already).
- */
 export interface ErrorHints {
     /** Appended after `Hint: ` when the SDK rejects the credential. */
     authentication: string;
@@ -37,6 +26,56 @@ export interface CallOptions {
      * failure has exactly one published shape, and no schema to keep in step.
      */
     structuredContent?: boolean;
+    /**
+     * Called when the API refuses on CREDENTIAL grounds — and only then.
+     *
+     * An HTTP transport has an obligation stdio does not: a client learns it
+     * must authenticate from a real `401` with a `WWW-Authenticate` header, and
+     * ignores that header entirely on a `200`. So a tool error saying "please
+     * authenticate" is, on that transport, a dead end — the caller is told
+     * something it has no way to act on.
+     *
+     * This is the seam that lets the transport answer properly, and the
+     * decision of WHAT counts as a credential failure stays here, beside the
+     * hints, rather than being made a second time by each consumer:
+     *
+     * - **Authentication** always reports. The credential was absent, malformed,
+     *   unknown, or expired — the transport cannot tell which, and does not
+     *   need to.
+     * - **Forbidden reports only when it carries `requiredScope`.** That field
+     *   is the API's own signal that a valid grant simply lacks a permission,
+     *   which re-consent can fix. Every other refusal on that arm — plan limits,
+     *   a terminated account, an action no scope can authorize — is a genuine
+     *   answer to the question asked, and stays an ordinary in-band tool error.
+     *
+     * The result is unchanged either way: the agent still receives the full
+     * text envelope, hints included. This is a notification, not a substitution.
+     *
+     * Why an observer at all, rather than the transport inspecting the request:
+     * peeking at a JSON-RPC body to guess whether a call needs a credential
+     * means parsing it twice — on the deploy path, that is tens of megabytes of
+     * base64 re-parsed before the size caps run — and it can only ever guess at
+     * PRESENCE, so an EXPIRED token would answer in-band and a connected client
+     * would never refresh. Reporting what the API actually answered costs
+     * nothing and is correct for both.
+     */
+    onAuthFailure?: (failure: AuthFailure) => void;
+}
+/**
+ * What a credential refusal was, in the only two shapes a transport acts on
+ * differently.
+ *
+ * Deliberately not an HTTP status or an RFC 6750 error code: those are the
+ * consuming transport's vocabulary, and stdio — which also builds a `call` —
+ * has neither. The presence of `requiredScope` is the whole discriminator, so
+ * there is no second field restating it.
+ */
+export interface AuthFailure {
+    /**
+     * The scope the grant is missing, from the API's `details.requiredScope`.
+     * Absent when the credential itself was refused rather than its permissions.
+     */
+    requiredScope?: string;
 }
 /**
  * Builds the `call()` wrapper both transports use: SDK promise in, MCP

package/dist/call.js

@@ -1,4 +1,33 @@
 import { ErrorType, isShipError } from '@shipstatic/ship';
+/**
+ * The two CREDENTIAL arms that earn a per-transport hint. Everything else
+ * relays verbatim — a credential hint on any other type sends the agent
+ * chasing a problem it does not have.
+ *
+ * They are ARGUMENTS rather than constants because they are the one part of
+ * the mapping that legitimately differs per transport: stdio can name the
+ * environment variable it owns, and the hosted endpoint deliberately cannot
+ * (it has no configuration of its own, and naming another package's variable
+ * is how this pair silently desynchronised once already).
+ *
+ * A third arm — maintenance — is hinted too, but it is NOT a member here: a
+ * closed platform is closed identically on every transport, so its text is a
+ * module constant (`MAINTENANCE_HINT`) rather than a per-transport argument.
+ * The membership test for this interface is "does the text differ per
+ * transport?", not "does the arm get a hint?".
+ */
+/**
+ * The maintenance hint — a CONSTANT, for the reason stated on `ErrorHints`:
+ * this text does not differ per transport, so making it an argument would ask
+ * two callers to agree on one sentence forever.
+ *
+ * The instruction to an agent matters more here than on any other arm. A tool
+ * failure normally invites a retry, and retrying is exactly wrong against a
+ * platform that is closed on purpose: the loop cannot succeed, and it spends
+ * the caller's budget discovering that. So the hint leads with the refusal to
+ * retry and closes with the reassurance the agent should relay to its user.
+ */
+const MAINTENANCE_HINT = 'The platform is temporarily closed for scheduled maintenance. Do not retry in a loop — wait and try again later. Deployed sites are unaffected and stay online.';
 /**
  * Builds the `call()` wrapper both transports use: SDK promise in, MCP
  * `CallToolResult` out.
@@ -9,7 +38,7 @@ import { ErrorType, isShipError } from '@shipstatic/ship';
  * kept equal by review.
  */
 export function createCall(options) {
-    const { hints, structuredContent = false } = options;
+    const { hints, structuredContent = false, onAuthFailure } = options;
     return async function call(fn) {
         try {
             const result = await fn();
@@ -28,10 +57,23 @@ export function createCall(options) {
             };
         }
         catch (error) {
-            return toErrorResult(error, hints);
+            return toErrorResult(error, hints, onAuthFailure);
         }
     };
 }
+/**
+ * Read the API's `details.requiredScope`, if this refusal carries one.
+ *
+ * `details` is `unknown` on the wire by design — every arm shapes it
+ * differently — so the read is a narrowing rather than a cast, and anything
+ * that is not a non-empty string means "no scope was named".
+ */
+function requiredScopeOf(details) {
+    if (!details || typeof details !== 'object')
+        return undefined;
+    const scope = details.requiredScope;
+    return typeof scope === 'string' && scope ? scope : undefined;
+}
 function isPlainObject(value) {
     return typeof value === 'object' && value !== null && !Array.isArray(value);
 }
@@ -63,14 +105,27 @@ function isPlainObject(value) {
  * governs success shapes, where the schema-twin objection lives. A failure has
  * one published shape on every transport.
  */
-function toErrorResult(error, hints) {
+function toErrorResult(error, hints, onAuthFailure) {
     if (isShipError(error)) {
         let message = error.message;
+        // First, because it is the one arm that is not about this caller at all:
+        // the platform is closed, nothing the agent sends can succeed, and the
+        // useful instruction is to stop rather than to fix something.
+        if (error.isType(ErrorType.Maintenance)) {
+            message += `\n\nHint: ${MAINTENANCE_HINT}`;
+        }
         if (error.isType(ErrorType.Authentication)) {
             message += `\n\nHint: ${hints.authentication}`;
+            onAuthFailure?.({});
         }
         if (error.isType(ErrorType.Forbidden)) {
             message += `\n\nHint: ${hints.forbidden}`;
+            // Only a MISSING SCOPE is a credential problem. The same arm carries
+            // plan limits and terminated accounts, which re-consenting cannot fix
+            // and which the caller should read as the answer it is.
+            const requiredScope = requiredScopeOf(error.details);
+            if (requiredScope)
+                onAuthFailure?.({ requiredScope });
         }
         if (error.isType(ErrorType.Validation) && error.details) {
             message += `\n\nDetails: ${safeStringify(error.details)}`;

package/dist/index.d.ts

@@ -20,7 +20,9 @@
  * Every name below answers a question a consumer must otherwise answer for
  * itself, and each admission was a restatement deleted, not a convenience
  * added: `SERVER_NAME` and `UPLOAD_TOOL_NAME` were literals in two repos (the
- * first also correlates the Apps-SDK widget to the connector), `PUBLIC_EXPIRY`
+ * first also correlates the Apps-SDK widget to the connector; the third,
+ * `UPLOAD_TOOL_TITLE`, is the same shape — one operation, one English name for
+ * it, authored per transport only because upload itself is), `PUBLIC_EXPIRY`
  * was the same duration written out eight times, `DESCRIPTION_BLOCKS` the
  * fragments two tool descriptions genuinely share, `ACCOUNT_TOOL_NAMES` is
  * what lets the hosted catalogue fence name the fourteen without counting them
@@ -58,7 +60,7 @@
  * extra — because adding an export is the quiet failure: everything published
  * becomes a breaking change to remove.
  */
-export { type CallFn, type CallOptions, createCall, type ErrorHints } from './call.js';
+export { type AuthFailure, type CallFn, type CallOptions, createCall, type ErrorHints, } from './call.js';
 export { createServer } from './server.js';
 export { ACCOUNT_TOOL_NAMES, registerAccountTools } from './tools.js';
-export { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, UPLOAD_TOOL_NAME, } from './vocabulary.js';
+export { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';

package/dist/index.js

@@ -20,7 +20,9 @@
  * Every name below answers a question a consumer must otherwise answer for
  * itself, and each admission was a restatement deleted, not a convenience
  * added: `SERVER_NAME` and `UPLOAD_TOOL_NAME` were literals in two repos (the
- * first also correlates the Apps-SDK widget to the connector), `PUBLIC_EXPIRY`
+ * first also correlates the Apps-SDK widget to the connector; the third,
+ * `UPLOAD_TOOL_TITLE`, is the same shape — one operation, one English name for
+ * it, authored per transport only because upload itself is), `PUBLIC_EXPIRY`
  * was the same duration written out eight times, `DESCRIPTION_BLOCKS` the
  * fragments two tool descriptions genuinely share, `ACCOUNT_TOOL_NAMES` is
  * what lets the hosted catalogue fence name the fourteen without counting them
@@ -58,7 +60,7 @@
  * extra — because adding an export is the quiet failure: everything published
  * becomes a breaking change to remove.
  */
-export { createCall } from './call.js';
+export { createCall, } from './call.js';
 export { createServer } from './server.js';
 export { ACCOUNT_TOOL_NAMES, registerAccountTools } from './tools.js';
-export { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, UPLOAD_TOOL_NAME, } from './vocabulary.js';
+export { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';

package/dist/server.js

@@ -3,7 +3,7 @@ import { DeploymentVia } from '@shipstatic/types';
 import { z } from 'zod';
 import { call } from './call.js';
 import { registerAccountTools } from './tools.js';
-import { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, UPLOAD_TOOL_NAME, } from './vocabulary.js';
+import { ANNOTATIONS, DESCRIPTION_BLOCKS, INSTRUCTION_BLOCKS, PARAM_DESCRIPTIONS, PUBLIC_EXPIRY, SERVER_NAME, UPLOAD_TOOL_NAME, UPLOAD_TOOL_TITLE, } from './vocabulary.js';
 // Destructured so the fifteen registrations below read as they always have.
 // The definitions live in `vocabulary.ts` because the hosted transport speaks
 // the same ones — that file records what is shared, what is not, and why.
@@ -40,6 +40,7 @@ export function createServer(ship, options) {
     });
     // Deployments
     server.registerTool(UPLOAD_TOOL_NAME, {
+        title: UPLOAD_TOOL_TITLE,
         description: `Deploy a static site instantly — ${D.free}. Returns the live URL, file count, and size. Without SHIP_TOKEN, the response includes a claim URL (site expires in ${PUBLIC_EXPIRY}) — always show both the deployment URL and claim URL to the user. ${D.password}`,
         annotations: CREATE,
         inputSchema: {

package/dist/tools.d.ts

@@ -26,6 +26,15 @@
  * on *this* transport (the hint is `createCall`'s one per-transport argument).
  * A tool list that changes shape under the caller would be a second, dynamic
  * contract for an agent to track, and MCP clients cache the catalogue.
+ *
+ * **Every tool carries a `title`, and it is a gate rather than a nicety.** The
+ * Claude connectors directory refuses submission for a tool that lacks one, so
+ * a titleless tool is not a shabby tool — it is an unlistable product. The
+ * style is short Title Case verb phrases naming what the USER gets ("List
+ * Deployments", "Connect Custom Domain"); the name obeys `resource_action` for
+ * the agent, the title reads as English for the human, and the description
+ * carries every precision neither can. Both catalogue pins assert a title on
+ * every tool, so the next one cannot be added without one.
  */
 import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import type Ship from '@shipstatic/ship';

package/dist/tools.js

@@ -26,6 +26,15 @@
  * on *this* transport (the hint is `createCall`'s one per-transport argument).
  * A tool list that changes shape under the caller would be a second, dynamic
  * contract for an agent to track, and MCP clients cache the catalogue.
+ *
+ * **Every tool carries a `title`, and it is a gate rather than a nicety.** The
+ * Claude connectors directory refuses submission for a tool that lacks one, so
+ * a titleless tool is not a shabby tool — it is an unlistable product. The
+ * style is short Title Case verb phrases naming what the USER gets ("List
+ * Deployments", "Connect Custom Domain"); the name obeys `resource_action` for
+ * the agent, the title reads as English for the human, and the description
+ * carries every precision neither can. Both catalogue pins assert a title on
+ * every tool, so the next one cannot be added without one.
  */
 import { z } from 'zod';
 import { ANNOTATIONS } from './vocabulary.js';
@@ -95,11 +104,13 @@ const DEPLOYMENT_EXAMPLE = 'happy-cat-abc1234.shipstatic.com';
 export function registerAccountTools(server, ship, call) {
     // Deployments
     server.registerTool('deployments_list', {
+        title: 'List Deployments',
         description: `List all deployments with their URLs, status, labels, and password protection state.${PAGING_NOTE}`,
         annotations: READ,
         inputSchema: PAGINATION_INPUT,
     }, ({ limit, cursor }) => call(() => ship.deployments.list({ limit, cursor })));
     server.registerTool('deployments_get', {
+        title: 'Get Deployment',
         description: 'Get deployment details including URL, status, file count, size, labels, and password protection state.',
         annotations: READ,
         inputSchema: {
@@ -109,6 +120,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ deployment }) => call(() => ship.deployments.get(deployment)));
     server.registerTool('deployments_set', {
+        title: 'Update Deployment Labels',
         description: 'Update deployment labels. Replaces all existing labels.',
         annotations: WRITE,
         inputSchema: {
@@ -121,6 +133,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ deployment, labels }) => call(() => ship.deployments.set(deployment, { labels })));
     server.registerTool('deployments_delete', {
+        title: 'Delete Deployment',
         description: 'Permanently delete a deployment and its files. You MUST confirm with the user before calling this tool, referencing the deployment.',
         annotations: DESTRUCTIVE,
         inputSchema: {
@@ -131,6 +144,7 @@ export function registerAccountTools(server, ship, call) {
     }, ({ deployment }) => call(() => ship.deployments.delete(deployment)));
     // Domains
     server.registerTool('domains_set', {
+        title: 'Connect Custom Domain',
         description: 'Create or update a custom domain. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. After creating, call domains_records and show the DNS records to the user.',
         annotations: WRITE,
         inputSchema: {
@@ -146,11 +160,13 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain, deployment, labels }) => call(() => ship.domains.set(domain, { deployment, labels })));
     server.registerTool('domains_list', {
+        title: 'List Domains',
         description: `List all domains with their URLs, linked deployment, and verification status.${PAGING_NOTE}`,
         annotations: READ,
         inputSchema: PAGINATION_INPUT,
     }, ({ limit, cursor }) => call(() => ship.domains.list({ limit, cursor })));
     server.registerTool('domains_get', {
+        title: 'Get Domain',
         description: 'Get domain details including URL, linked deployment, verification status, and labels.',
         annotations: READ,
         inputSchema: {
@@ -160,6 +176,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.get(domain)));
     server.registerTool('domains_records', {
+        title: 'Get DNS Records',
         description: 'Get the DNS records the user needs to configure at their DNS provider. Call after domains_set. You MUST show the returned records to the user.',
         annotations: READ,
         inputSchema: {
@@ -169,6 +186,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.records(domain)));
     server.registerTool('domains_dns', {
+        title: 'Look Up DNS Provider',
         description: 'Look up the DNS provider for a domain (e.g. Cloudflare, Namecheap). Helps the user know where to configure their DNS records.',
         annotations: READ,
         inputSchema: {
@@ -178,6 +196,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.dns(domain)));
     server.registerTool('domains_share', {
+        title: 'Share DNS Setup',
         description: 'Get a shareable DNS setup hash for a domain. The hash can be shared with the user so they can view the required DNS records without needing an API key.',
         annotations: READ,
         inputSchema: {
@@ -187,6 +206,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.share(domain)));
     server.registerTool('domains_validate', {
+        title: 'Check Domain Availability',
         description: 'Check if a domain name is valid and available before creating it. Returns the normalized form and availability.',
         annotations: READ,
         inputSchema: {
@@ -196,6 +216,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.validate(domain)));
     server.registerTool('domains_verify', {
+        title: 'Verify Domain DNS',
         description: 'Trigger DNS verification for a custom domain. Call after the user has configured DNS records from domains_records. Verification is asynchronous — the domain status updates once DNS propagates.',
         annotations: WRITE,
         inputSchema: {
@@ -205,6 +226,7 @@ export function registerAccountTools(server, ship, call) {
         },
     }, ({ domain }) => call(() => ship.domains.verify(domain)));
     server.registerTool('domains_delete', {
+        title: 'Delete Domain',
         description: 'Permanently delete a domain. You MUST confirm with the user before calling this tool, referencing the domain name.',
         annotations: DESTRUCTIVE,
         inputSchema: {
@@ -213,6 +235,7 @@ export function registerAccountTools(server, ship, call) {
     }, ({ domain }) => call(() => ship.domains.delete(domain)));
     // Account
     server.registerTool('whoami', {
+        title: 'Show Account',
         description: 'Show authenticated account details including email, plan, and usage.',
         annotations: READ,
     }, () => call(() => ship.whoami()));

package/dist/vocabulary.d.ts

@@ -60,6 +60,26 @@ export declare const SERVER_NAME = "shipstatic";
  * `[UPLOAD_TOOL_NAME, ...ACCOUNT_TOOL_NAMES]` rather than counting to fifteen.
  */
 export declare const UPLOAD_TOOL_NAME = "deployments_upload";
+/**
+ * The upload tool's human-readable `title`, shared for the same reason the
+ * name is — and NOT for the reason the description is not.
+ *
+ * A title names the OPERATION, and the operation is identical on both doors:
+ * a user reading "Deploy Static Site" in a client's tool list learns nothing
+ * about how the bytes got there. The description is the opposite — hosted
+ * spends a paragraph telling an Apps-SDK caller not to base64-encode text, a
+ * hazard a filesystem path cannot have — which is why one is exported whole
+ * and the other only in fragments.
+ *
+ * The other fourteen titles live inline in `tools.ts`: one definition, both
+ * transports, nothing to keep in agreement. This one is authored per transport
+ * (upload is the tool each door writes for itself), so without an owner it
+ * would be two literals in two repos with nothing comparing them.
+ *
+ * Titles are not decoration here: the Claude connectors directory refuses
+ * submission for a tool that lacks one.
+ */
+export declare const UPLOAD_TOOL_TITLE = "Deploy Static Site";
 /**
  * How long an anonymous deployment lives, in the words an agent reads.
  *

package/dist/vocabulary.js

@@ -62,6 +62,26 @@ export const SERVER_NAME = 'shipstatic';
  * `[UPLOAD_TOOL_NAME, ...ACCOUNT_TOOL_NAMES]` rather than counting to fifteen.
  */
 export const UPLOAD_TOOL_NAME = 'deployments_upload';
+/**
+ * The upload tool's human-readable `title`, shared for the same reason the
+ * name is — and NOT for the reason the description is not.
+ *
+ * A title names the OPERATION, and the operation is identical on both doors:
+ * a user reading "Deploy Static Site" in a client's tool list learns nothing
+ * about how the bytes got there. The description is the opposite — hosted
+ * spends a paragraph telling an Apps-SDK caller not to base64-encode text, a
+ * hazard a filesystem path cannot have — which is why one is exported whole
+ * and the other only in fragments.
+ *
+ * The other fourteen titles live inline in `tools.ts`: one definition, both
+ * transports, nothing to keep in agreement. This one is authored per transport
+ * (upload is the tool each door writes for itself), so without an owner it
+ * would be two literals in two repos with nothing comparing them.
+ *
+ * Titles are not decoration here: the Claude connectors directory refuses
+ * submission for a tool that lacks one.
+ */
+export const UPLOAD_TOOL_TITLE = 'Deploy Static Site';
 /**
  * How long an anonymous deployment lives, in the words an agent reads.
  *

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@shipstatic/mcp",
-  "version": "1.0.0-beta.9",
+  "version": "1.0.0",
   "mcpName": "com.shipstatic/mcp",
-  "description": "ShipStatic MCP — deploy static websites from AI agents. Full toolset incl. custom domains. Free hosted endpoint at mcp.shipstatic.com — no install.",
+  "description": "ShipStatic MCP \u2014 deploy static websites from AI agents. Full toolset incl. custom domains. Free hosted endpoint at mcp.shipstatic.com \u2014 no install.",
   "type": "module",
   "main": "./dist/index.js",
   "sideEffects": [
@@ -21,6 +21,7 @@
   },
   "scripts": {
     "build": "tsc",
+    "prepack": "pnpm run build",
     "clean": "rm -rf dist",
     "prepare": "git config core.hooksPath scripts/githooks",
     "test": "vitest",
@@ -66,8 +67,8 @@
   "license": "MIT",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.30.0",
-    "@shipstatic/ship": "2.0.0-beta.15",
-    "@shipstatic/types": "2.5.0-beta.20",
+    "@shipstatic/ship": "2.0.0",
+    "@shipstatic/types": "2.5.0",
     "zod": "^4.4.3"
   },
   "devDependencies": {
@@ -78,5 +79,9 @@
     "typescript": "^6.0.3",
     "vitest": "4.1.10"
   },
-  "packageManager": "pnpm@10.12.4"
+  "packageManager": "pnpm@10.12.4",
+  "publishConfig": {
+    "access": "public",
+    "provenance": true
+  }
 }