dev.typeship/typeship

Est-ce que dev.typeship/typeship est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.typeship/typeship » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 6 outils

• packages_download≈ 224 tokens

  Download a generated package. Download the complete ZIP referenced by `packages_generate`'s `download.url`. GET /generate/download No credential needed.

  Paramètres, retour & exemple (2)

  Paramètres

  • token · string · requis
    Private download token from download.url in the generation result.
  • fields · array · optionnel
    Result keys to keep, as dotted paths (e.g. ["id","name"]). Omit for the whole result. Keeps responses small.

  Exemple d'appel

  {"name": "packages_download", "arguments": {"token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• packages_generate≈ 6158 tokens

  Generate a package. Returns one generated package without creating a Project. POST /generate Credential optional.

  Paramètres, retour & exemple (7)

  Paramètres

  • spec · ? · requis
    A Spec for one-shot generation, provided as exactly one URL or inline entrypoint.
  • config · object · optionnel
    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 configuration. Typeship never requires vendor extensions inside the Spec itself. One-shot generation also accepts GraphQL settings here; stored projects keep those settings on their Spec.
  • fields · array · optionnel
    Result keys to keep, as dotted paths (e.g. ["id","name"]). Omit for the whole result. Keeps responses small.
  • target · object · requis
    One-shot generator descriptor; no persisted Target is created.
  • module_path · string · optionnel
    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 · optionnel
    npm package or Python distribution override. Valid only for the TypeScript and Python SDK targets.
  • Idempotency-Key · string · optionnel
    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 method, path, query, If-Match header, and JSON body replays the original response. Reusing the key with changed intent returns 409. After expiry the key starts a new write.

  Exemple d'appel

  {"name": "packages_generate", "arguments": {"spec": "texte", "target": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"claim": "texte", "files": [], "object": "texte", "coverage": {}, "download": {}, "warnings": [], "request_id": "texte"}}

• query_docs≈ 224 tokens

  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

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "query_docs", "arguments": {"pattern": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• read_docs≈ 234 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • page · string · requis
  • path · string · optionnel
    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
  • offset · integer · optionnel
    Character offset to continue a long page from, default 0
  • schema · boolean · optionnel
    Also return the operation's complete input and output JSON Schemas, default false

  Exemple d'appel

  {"name": "read_docs", "arguments": {"page": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_docs≈ 150 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • page · integer · optionnel
    Page of reference matches (10 per page), default 1
  • query · string · requis
    The task in a few words, e.g. "assign issue" or "list calls"

  Exemple d'appel

  {"name": "search_docs", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submit_docs_feedback≈ 154 tokens

  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

  Paramètres, retour & exemple (2)

  Paramètres

  • page · string · requis
    The page URL or title.
  • message · string · requis
    What is wrong or missing, in one to five sentences.

  Exemple d'appel

  {"name": "submit_docs_feedback", "arguments": {"page": "texte", "message": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://typeship.dev/mcp/public