dev.bitbybit/cad

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

Au dernier audit MCP Hub, le serveur MCP « dev.bitbybit/cad » 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 7 outils

• describe≈ 309 tokens

  The exact contract of one member by dotted path, for example occt.shapes.solid.createBox: signature, every parameter with its type, default and range, the return type, the documentation, examples and where it runs. Answers are for the API version the server holds. It also describes the types a member returns or takes by their name, for example Inputs.IFC.SpaceInfoDto, field by field, and a member's answer lists those types. An unknown path is reported as not found together with the nearest existing paths; nothing is guessed.

  Paramètres, retour & exemple (2)

  Paramètres

  • path · string · requis
    The dotted path of the member, for example occt.shapes.solid.createBox, or the name of a type a member returns or takes, for example Inputs.IFC.SpaceInfoDto
  • version · string · optionnel
    The API version to describe; omit for the version the server holds

  Exemple d'appel

  {"name": "describe", "arguments": {"path": "texte"}}

  Exemple de retour

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

• fetch≈ 143 tokens

  Fetches the full documentation of one Bitbybit API member by id (a dotted path returned by search) as text, with its title, url and metadata.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    A dotted API path returned by search

  Exemple d'appel

  {"name": "fetch", "arguments": {"id": "texte"}}

  Exemple de retour

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

• get_examples≈ 299 tokens

  Working TypeScript examples for a member path, for a namespace, or for a topic given as keywords. Each example names the member it belongs to and links its reference page. Examples are written for the API version the server holds.

  Paramètres, retour & exemple (5)

  Paramètres

  • path · string · optionnel
    A member or namespace path, for example occt.shapes.solid.createBox or occt.fillets
  • limit · integer · optionnel
    How many examples, 5 by default
  • topic · string · optionnel
    Keywords to find examples by, when no path is known
  • engine · string · optionnel · babylonjs | threejs | playcanvas
    Prefer members published for this engine when searching by topic
  • version · string · optionnel
    The API version; omit for the version the server holds

  Exemple d'appel

  {"name": "get_examples", "arguments": {"path": "texte", "limit": 1, "topic": "texte", "engine": "babylonjs", "version": "texte"}}

  Exemple de retour

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

• get_guide≈ 374 tokens

  Sections of the public guides: building with Bitbybit (what runs in the browser, on a server, on a lightweight backend, and what needs CAD Cloud), writing geometry with the kernels (which kernel to use, the order to build a part in, choosing edges, checking and exporting shapes), writing design documents (parametric models as JSON: parameters, sketches, features, references, parts and assemblies), and writing IFC building models (storeys, walls and their joins, doors, windows, slabs, roofs, rooms, properties and quantities). Without a topic it lists the sections. Read "integrate" before recommending where geometry should run: the npm packages are the default, and CAD Cloud is for algorithms that exist only there or compute the caller cannot provide. Read "geometry" before writing geometry code, "design" before writing a design document, and "ifc" before writing an IFC model.

  Paramètres, retour & exemple (1)

  Paramètres

  • topic · string · optionnel
    A section id or a short name such as integrate, browser, backend, server-side, pro, start, geometry, part-order, geometry-mistakes, design, references, assembly, ifc, ifc-order, ifc-mistakes; omit to list the sections

  Exemple d'appel

  {"name": "get_guide", "arguments": {"topic": "texte"}}

  Exemple de retour

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

• list_namespace≈ 194 tokens

  The members one level below a namespace path, for example occt.shapes, each with its kind and summary. Without a path, the top-level namespaces. Use it to discover what exists before searching for details.

  Paramètres, retour & exemple (2)

  Paramètres

  • path · string · optionnel
    A namespace path such as occt or occt.shapes; omit for the top level
  • version · string · optionnel
    The API version to list; omit for the version the server holds

  Exemple d'appel

  {"name": "list_namespace", "arguments": {"path": "texte", "version": "texte"}}

  Exemple de retour

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

• search≈ 139 tokens

  Searches the Bitbybit API documentation and returns a list of results with id, title and url. Each id is a dotted API path that fetch accepts.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis
    Search terms

  Exemple d'appel

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

  Exemple de retour

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

• search_api≈ 324 tokens

  Find Bitbybit API members (methods, namespaces, cloud operations) by keywords, for example "box solid" or "fillet edges". Returns dotted paths with a one-line summary, the tier (oss on npm, platform-pro only at bitbybit.dev, cloud-pro only on CAD Cloud) and the engines each is published for. Call describe with a path before writing code that uses it.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    How many results, 10 by default
  • query · string · requis
    Keywords, a phrase, or a partial dotted path
  • engine · string · optionnel · babylonjs | threejs | playcanvas
    Only members published for this engine, plus the cloud operations, which run on CAD Cloud rather than in an engine; omit for every engine
  • version · string · optionnel
    The API version to search; omit for the version the server holds

  Exemple d'appel

  {"name": "search_api", "arguments": {"query": "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://mcp.bitbybit.dev/mcp