# typeship (remote · typeship.dev)

Generate a typed SDK, CLI, and MCP server from any OpenAPI or GraphQL spec, and keep them current.

- Trust score: 38/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `typeship.dev`: 74/100, [markdown](https://verifymcp.io/servers/dev-typeship-typeship/mcp-public.md), [page](https://verifymcp.io/servers/dev-typeship-typeship/mcp-public)
- remote · `typeship.dev`: 38/100, [markdown](https://verifymcp.io/servers/dev-typeship-typeship/mcp-readonly.md), [page](https://verifymcp.io/servers/dev-typeship-typeship/mcp-readonly)
- remote · `typeship.dev`: 38/100 (this document), [markdown](https://verifymcp.io/servers/dev-typeship-typeship/typeship.md), [page](https://verifymcp.io/servers/dev-typeship-typeship/typeship)
- npm · `@typeship-ax/mcp`: 90/100, [markdown](https://verifymcp.io/servers/dev-typeship-typeship/typeship-ax-mcp.md), [page](https://verifymcp.io/servers/dev-typeship-typeship/typeship-ax-mcp)

## Channel facts

- Endpoint: `https://typeship.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.10.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-09-20.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the typeship MCP server?

typeship is a hosted endpoint at https://typeship.dev/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 dev-typeship-typeship 'https://typeship.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-typeship-typeship": {
      "url": "https://typeship.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-typeship-typeship": {
      "type": "http",
      "url": "https://typeship.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-typeship-typeship]
url = "https://typeship.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-typeship-typeship": {
      "type": "remote",
      "url": "https://typeship.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-typeship-typeship --url 'https://typeship.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-typeship-typeship:
    url: "https://typeship.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-typeship-typeship": {
      "Transport": "http",
      "Url": "https://typeship.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-typeship-typeship -t streamable-http -u 'https://typeship.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-typeship-typeship": {
      "type": "http",
      "url": "https://typeship.dev/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-08-26 (score 38, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-25 (score 38, −26)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Transport: pass → unverified
- [security regression] Stability: fail → unverified
- [security improvement] Authorization: unverified → pass
- [security] First check of Authorization: partial
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified

### 2026-08-24 (score 64, 0)

- [cosmetic] “generate_run” reworded the description of “outputs”

### 2026-08-23 (score 64, 0)

- [security regression] Stability: 0.03 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [functional regression] “generate_run” added a required parameter “outputs”, so existing callers break
- [cosmetic] “generate_run” reworded the description of “spec”
- [cosmetic] “generate_run” reworded the description of “package_name”
- [cosmetic] “generate_run” dropped the optional parameter “language”
- [cosmetic] “generate_run” dropped the optional parameter “platforms”

### 2026-08-22 (score 64)

- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “generate_run” reworded the description of “config”
- [cosmetic] “generate_run” reworded the description of “platforms”

### 2026-08-21 (score 0)

First indexed and scored.

## MCP tools (5)

### `generate_run` (~218 tokens)

Generate a package from a spec

Generate a package from a spec. Stateless generation: nothing is stored. POST /generate Credential optional.

Input parameters:

- `config` (object): Everything typeship needs beyond the spec, in one object: generation customization (globals, retries, pagination) and how the generated tooling behaves (cli, mcp, package, docs_url). Plain configurat…
- `fields` (array): Result keys to keep, as dotted paths (e.g. ["id","name"]). Omit for the whole result. Keeps responses small.
- `outputs` (array, required): The one output package to generate. Linked projects can select any combination of outputs and keep each package current.
- `package_name` (string): Registry name for the selected delivery package: an npm package, Python distribution, or Go module path. Defaults to a name derived from the API title.
- `spec` (required): The specification for stateless generation, provided as exactly one URL or inline document.

Output parameters:

- `claim`: Anonymous, URL-sourced generations only. A link a signed-in person can open to turn this run into a project in their organization (same spec, outputs, and config). Lasts seven days. Null for inline s…
- `files` (array)
- `limits` (object): Present when the generation was capped: by the free plan, or because the call was anonymous. Absent on uncapped generations.
- `meta` (object)
- `warnings` (array)

### `search_docs` (~65 tokens)

Search this API's reference (operations, parameters) and, when a docs site is configured, its guides. Best matches first; page through with page.

Input parameters:

- `page` (integer): Page of reference matches (15 per page), default 1
- `query` (string, required)

### `read_docs` (~45 tokens)

Read a documentation page: an operation reference (a tool name, or dotted "resource.method") or a docs-site guide page by name or URL.

Input parameters:

- `page` (string, required)

### `query_docs` (~130 tokens)

Grep the typeship docs

Search every typeship docs page and both references with a regular expression (case-insensitive) and get matching lines with their page and a little context. Use when search_docs is too coarse or you need every occurrence of a term, flag, or error message. GET llms-full.txt

Input parameters:

- `context` (integer): Lines of context around each match (0 to 5). Default 1.
- `limit` (integer): Maximum matches to return (1 to 100). Default 30.
- `pattern` (string, required): A JavaScript regular expression, matched case-insensitively line by line.

### `submit_docs_feedback` (~83 tokens)

Report a docs problem

Tell the typeship team a docs page is wrong, missing, or unclear: the page (URL or title) and what you expected. Read by people; no reply comes back through this tool. POST docs feedback

Input parameters:

- `message` (string, required): What is wrong or missing, in one to five sentences.
- `page` (string, required): The page URL or title.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-typeship-typeship/typeship#diagnostics

## Score history

- 2026-09-20: 38
- 2026-09-19: 38
- 2026-09-18: 38
- 2026-09-17: 38
- 2026-09-16: 38
- 2026-09-15: 38
- 2026-09-14: 38
- 2026-09-13: 38
- 2026-09-12: 38
- 2026-09-11: 38
- 2026-09-10: 38
- 2026-09-09: 38
- 2026-09-08: 38
- 2026-09-07: 38
- 2026-09-06: 38
- 2026-09-05: 38
- 2026-09-04: 38
- 2026-09-03: 38
- 2026-09-02: 38
- 2026-09-01: 38
- 2026-08-31: 38
- 2026-08-30: 38
- 2026-08-29: 38
- 2026-08-28: 38
- 2026-08-27: 38
- 2026-08-26: 38
- 2026-08-25: 38
- 2026-08-24: 64
- 2026-08-23: 64
- 2026-08-22: 64

## Common questions

### What is the typeship MCP server?

typeship is an MCP server listed in the public MCP registry as dev.typeship/typeship. Generate a typed SDK, CLI, and MCP server from any OpenAPI or GraphQL spec, and keep them current. This page covers its hosted endpoint (https://typeship.dev/mcp).

### Is the typeship MCP server safe to use?

typeship scores 38 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 typeship MCP server expose?

typeship exposes 5 tools: generate_run, search_docs, read_docs, query_docs, submit_docs_feedback. Their descriptions and schemas cost roughly 541 tokens of context every time the server is loaded.

### Does the typeship MCP server require authentication?

Yes. typeship asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the typeship MCP server still maintained?

typeship is still listed as active in the MCP registry. We last reached this channel on 20 September 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://typeship.dev/mcp
- Repository: https://github.com/typeship-ax/mcp
- Website: https://typeship.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-typeship-typeship/typeship.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-typeship-typeship/typeship.json
- HTML version of this page: https://verifymcp.io/servers/dev-typeship-typeship/typeship