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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
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. Claim this server and supply a read-only token to verify it and lift the score.
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.
remote · typeship.dev
claude mcp add --transport http dev-typeship-typeship 'https://typeship.dev/mcp'
{
"mcpServers": {
"dev-typeship-typeship": {
"url": "https://typeship.dev/mcp"
}
}
} {
"servers": {
"dev-typeship-typeship": {
"type": "http",
"url": "https://typeship.dev/mcp"
}
}
} [mcp_servers.dev-typeship-typeship] url = "https://typeship.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-typeship-typeship": {
"type": "remote",
"url": "https://typeship.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-typeship-typeship --url 'https://typeship.dev/mcp' --transport streamable-http
mcp_servers:
dev-typeship-typeship:
url: "https://typeship.dev/mcp" {
"McpServers": {
"dev-typeship-typeship": {
"Transport": "http",
"Url": "https://typeship.dev/mcp"
}
}
} assistant mcp add dev-typeship-typeship -t streamable-http -u 'https://typeship.dev/mcp'
{
"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.
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.
- 26 Aug 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
- 25 Aug 26 −26
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Stability: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 24 Aug 26 0
- “generate_run” reworded the description of “outputs” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 23 Aug 26 0
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- “generate_run” added a required parameter “outputs”, so existing callers break ▼ functional
- “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” cosmetic
- 22 Aug 26 64
- Stability: unverified → 0.03 ▲ functional
- “generate_run” reworded the description of “config” cosmetic
- “generate_run” reworded the description of “platforms” cosmetic
- 21 Aug 26 0
First indexed and scored.
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
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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer scope="user:org:read typeship:read typeship:generate typeship:write", resource_metadata="https://typeship.dev/.well-known/oauth-protected-resource"
Bearer scope="user:org:read typeship:read typeship:generate typeship:write", resource_metadata="https://typeship.dev/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| www-authenticate | Bearer scope="user:org:read typeship:read typeship:generate typeship:write", resource_metadata="https://typeship.dev/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://typeship.dev/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://typeship.dev/mcp |
| Authorisation server | https://clerk.typeship.dev |
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 | Auth required | 401 | |
| http (plaintext) | http://typeship.dev/mcp | HTTPS enforced | 308 | https://typeship.dev/mcp |
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 a package from a spec ~218
Generate a package from a spec. Stateless generation: nothing is stored. POST /generate Credential optional.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | yes | The specification for stateless generation, provided as exactly one URL or inline document. |
| 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, 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 | – | – |
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).
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.