Typeship
REMOTE · TYPESHIP.DEV · 4 COMPONENTS
Generate a typed SDK, CLI, and MCP server from any OpenAPI or GraphQL spec, and keep them current.
Last scanned (2 hours ago)
Scores higher than 78% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Developer Tools
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1196 tokens (~199/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
- Structured output schemas are declared (17% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 27 Oct 26 +4
- Stability: fail → pass ▲ security
- 24 Oct 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 67.
- 30 Sept 26 0
- Tool “read_docs” rewrote its description, which is the text the model reads security
- “read_docs” added an optional parameter “path” cosmetic
- 28 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “query_docs” rewrote its description, which is the text the model reads security
- Tool “submit_docs_feedback” rewrote its description, which is the text the model reads security
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Tool “query_docs” changed its title: Grep the typeship docs → Grep the Typeship docs cosmetic
- 27 Sept 26 0
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “generate_run” was removed ▼ security
- Tool “generate_download_package” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “read_docs” rewrote its description, which is the text the model reads security
- Tool coverage: 89% → 95% ▲ functional
- New tool “packages_generate” functional
- New tool “packages_download” functional
- “read_docs” added an optional parameter “schema” cosmetic
- “read_docs” added an optional parameter “offset” cosmetic
- “search_docs” reworded the description of “page” cosmetic
- “search_docs” reworded the description of “query” cosmetic
- 26 Sept 26 0
- “generate_run” reworded the description of “go_sdk” cosmetic
- “generate_run” reworded the description of “module_path” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 25 Sept 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
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 6 Nov 2026 · Probed https://typeship.dev/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=typeship.dev | CN=YR1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | RSA 2048 | SHA256-RSA | 648f366321429856e3b3eba6cc1854e19c5 |
| SANs: typeship.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of typeship.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| typeship.dev. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'none' |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://typeship.dev/mcp/public | Verified | 200 | |
| http (plaintext) | http://typeship.dev/mcp/public | HTTPS enforced | 308 | https://typeship.dev/mcp/public |
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 →
packages_download Download a generated package ~88
Download a generated package. Download the complete ZIP referenced by `packages_generate`'s `download.url`. GET /generate/download No credential needed.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Result keys to keep, as dotted paths (e.g. ["id","name"]). Omit for the whole result. Keeps responses small. |
| token | string | yes | Private download token from download.url in the generation result. |
No output schema declared.
No examples provided.
packages_generate Generate a package ~328
Generate a package. Returns one generated package without creating a Project. POST /generate Credential optional.
| Name | Type | Req | Description |
|---|---|---|---|
| Idempotency-Key | string | – | Identifies one logical write for 24 hours. The key is scoped to the authenticated organization and operation; generation without an organization uses a hashed network identity. Retrying the same meth… |
| config | object | – | Everything Typeship needs beyond the Spec, in one object: generation customization (globals, retries, pagination, readme) and how the generated tooling behaves (cli, mcp, package, docs_url). Plain co… |
| fields | array | – | Result keys to keep, as dotted paths (e.g. ["id","name"]). Omit for the whole result. Keeps responses small. |
| module_path | string | – | Go module path override for the generated artifact's own module. Valid only for the Go SDK and CLI Targets. Projects derive this from the Go destination repository by default. |
| package_name | string | – | npm package or Python distribution override. Valid only for the TypeScript and Python SDK targets. |
| spec | – | yes | A Spec for one-shot generation, provided as exactly one URL or inline entrypoint. |
| target | object | yes | One-shot generator descriptor; no persisted Target is created. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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, Target, and config). Lasts seven days. Null for inline Sp… |
| coverage | object | – | – |
| download | object | – | Complete package ZIP from this exact result. Present on requests with Idempotency-Key, including automatic CLI, MCP, and SDK keys. Download before expires_at, verify sha256, and extract into an empty… |
| files | array | – | – |
| object | string | – | One generated package. It has no ID: download it with download.url before download.expires_at. |
| request_id | string | – | Server-generated identifier used to correlate this response with Typeship logs. |
| warnings | array | – | – |
No examples provided.
query_docs Grep the Typeship docs ~130
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
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | A JavaScript regular expression, matched case-insensitively line by line. |
No output schema declared.
No examples provided.
read_docs ~149
Read a documentation page: an operation reference (a tool name, or dotted "resource.method"), a named input type such as a filter, or a docs-site guide page by name or URL. Long pages come in parts; pass the offset a part ends with to continue.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | Character offset to continue a long page from, default 0 |
| page | string | yes | – |
| path | string | – | A dotted argument path within the operation or type, e.g. "filter.team.key": that field's type, with its named type's fields or values |
| schema | boolean | – | Also return the operation's complete input and output JSON Schemas, default false |
No output schema declared.
No examples provided.
search_docs ~83
Search this API's reference (operations, parameters) and, when a docs site is configured, its guides. Best matches first; page through with page.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page of reference matches (10 per page), default 1 |
| query | string | yes | The task in a few words, e.g. "assign issue" or "list calls" |
No output schema declared.
No examples provided.
submit_docs_feedback Report a docs problem ~83
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
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | What is wrong or missing, in one to five sentences. |
| page | string | yes | The page URL or title. |
No output schema declared.
No examples provided.
How do I install the Typeship MCP server?
Typeship is a hosted endpoint at https://typeship.dev/mcp/public, 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 · typeship.dev
claude mcp add --transport http dev-typeship-typeship 'https://typeship.dev/mcp/public'
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/public).
Is the Typeship MCP server safe to use?
Typeship scores 79 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 6 tools: packages_generate, packages_download, search_docs, read_docs, query_docs, submit_docs_feedback. Their descriptions and schemas cost roughly 861 tokens of context every time the server is loaded.
Does the Typeship MCP server require authentication?
No. We connected to Typeship without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Typeship MCP server still maintained?
Typeship is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Typeship MCP server?
VerifyMCP ran 12 checks on Typeship, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Typeship: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.