typeship
REMOTE · TYPESHIP.DEV · 4 COMPONENTS · SCANNED SEP 20
Generate a typed SDK, CLI, and MCP server from any OpenAPI or GraphQL spec, and keep them current.
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 2 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 943 tokens (~188/item across 5 items; 5 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 Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
- Structured output schemas are declared (20% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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'
{
"mcpServers": {
"dev-typeship-typeship": {
"url": "https://typeship.dev/mcp/public"
}
}
} {
"servers": {
"dev-typeship-typeship": {
"type": "http",
"url": "https://typeship.dev/mcp/public"
}
}
} [mcp_servers.dev-typeship-typeship] url = "https://typeship.dev/mcp/public"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-typeship-typeship": {
"type": "remote",
"url": "https://typeship.dev/mcp/public",
"enabled": true
}
}
} openclaw mcp add dev-typeship-typeship --url 'https://typeship.dev/mcp/public' --transport streamable-http
mcp_servers:
dev-typeship-typeship:
url: "https://typeship.dev/mcp/public" {
"McpServers": {
"dev-typeship-typeship": {
"Transport": "http",
"Url": "https://typeship.dev/mcp/public"
}
}
} assistant mcp add dev-typeship-typeship -t streamable-http -u 'https://typeship.dev/mcp/public'
{
"mcpServers": {
"dev-typeship-typeship": {
"type": "http",
"url": "https://typeship.dev/mcp/public"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 0
- Tool “generate_run” rewrote its description, which is the text the model reads security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 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=YR2,O=Let's Encrypt,C=US | 18 Aug 2026 | 16 Nov 2026 | RSA 2048 | SHA256-RSA | 67039a5d9e80a11d453f380bb851b85537b |
| SANs: *.typeship.dev, typeship.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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. | present | 60074 | 8 | Verified |
| typeship.dev. | absent | 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 | 400 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
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 →
generate_run Generate one Target from a Definition ~321
Generate one Target from a Definition. Returns one generated package without saving a Project or retaining source files or generated files. 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 account and operation; account-less generation uses a hashed network identity. Retrying the same method, path, query,… |
| config | object | – | Everything Typeship needs beyond the Definition, in one object: generation customization (globals, retries, pagination, readme) and how the generated tooling behaves (cli, mcp, package, docs_url). Pl… |
| definition | – | yes | A Definition for stateless generation, provided as exactly one URL or inline entrypoint. |
| 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. Valid only for the Go SDK. Linked 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. |
| target | object | yes | Stateless generator descriptor; no persisted Target is created. |
| Name | Type | Req | Description |
|---|---|---|---|
| claim | – | – | Anonymous, URL-sourced generations only. |
| files | array | – | – |
| limits | object | – | Present when the generation was capped: by the free plan, or because the call was anonymous. |
| meta | object | – | – |
| 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 ~45
Read a documentation page: an operation reference (a tool name, or dotted "resource.method") or a docs-site guide page by name or URL.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | – |
No output schema declared.
No examples provided.
search_docs ~65
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 (15 per page), default 1 |
| query | string | yes | – |
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.
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 74 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 644 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.