typeship
NPM · @TYPESHIP-AX/MCP · 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 from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to typeship-ax/mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 472 tokens (~157/item across 3 items; 3 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 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 runs locally as an npm package, launched with npx -y @typeship-ax/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @typeship-ax/mcp
claude mcp add dev-typeship-typeship -- npx -y @typeship-ax/mcp
{
"mcpServers": {
"dev-typeship-typeship": {
"command": "npx",
"args": [
"-y",
"@typeship-ax/mcp"
]
}
}
} {
"servers": {
"dev-typeship-typeship": {
"command": "npx",
"args": [
"-y",
"@typeship-ax/mcp"
]
}
}
} codex mcp add dev-typeship-typeship -- npx -y @typeship-ax/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-typeship-typeship": {
"type": "local",
"command": [
"npx",
"-y",
"@typeship-ax/mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-typeship-typeship --command npx --arg -y --arg @typeship-ax/mcp
mcp_servers:
dev-typeship-typeship:
command: "npx"
args: ["-y", "@typeship-ax/mcp"] {
"McpServers": {
"dev-typeship-typeship": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@typeship-ax/mcp"
]
}
}
} assistant mcp add dev-typeship-typeship -t stdio -c npx -a -y @typeship-ax/mcp
{
"mcpServers": {
"dev-typeship-typeship": {
"command": "npx",
"args": [
"-y",
"@typeship-ax/mcp"
]
}
}
} 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −16
- Tool safety: pass → unverified ▼ security
- Stability: 0.57 → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Schema quality: 139 → 157 ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.8.0 → 0.10.0 functional
- Package version: 0.8.0 → 0.9.1 functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 · Analysed npm/@typeship-ax/mcp@0.10.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | typeship-ax/mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/typeship-ax/mcp/.github/workflows/publish.yml@refs/tags/v0.10.0 |
| Rekor log index | 2798484877 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c014b026efb7ea1044ab155a773d43dddd860fa31d22b9ec01412007af0d3b870bf78f5387eada31a909b919fb7c2edb96f9959e121990d73f305bd2f |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
execute ~95
Execute an API operation by name. Discover it with search_docs, then read_docs <operation> for its full schema, example, and safety classification. Destructive operations require confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | Operation arguments keyed by parameter name |
| confirm | boolean | – | Required and must be true for destructive operations. Omit for reads and ordinary writes. |
| operation | string | yes | Operation tool name returned by search_docs |
No output schema declared.
No examples provided.
read_docs ~43
Read an operation's full reference (arguments, schemas, authentication, safety and example) by tool name, or a docs-site guide page.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | – |
No output schema declared.
No examples provided.
search_docs ~63
Search this API's 34 generated operations and, when a docs site is configured, its guides. Start here to find the operation you need.
| 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.
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 npm package (@typeship-ax/mcp).
Is the typeship MCP server safe to use?
typeship scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 3 tools: search_docs, read_docs, execute. Their descriptions and schemas cost roughly 201 tokens of context every time the server is loaded.
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.
What licence is the typeship MCP server under?
typeship declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.