Bitbybit CAD MCP
REMOTE · MCP.BITBYBIT.DEV · 2 COMPONENTS · SCANNED OCT 15
Bitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guide
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1321 tokens (~188/item across 7 items; 7 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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 Bitbybit CAD MCP server?
Bitbybit CAD MCP is a hosted endpoint at https://mcp.bitbybit.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 · mcp.bitbybit.dev
claude mcp add --transport http dev-bitbybit-cad 'https://mcp.bitbybit.dev/mcp'
{
"mcpServers": {
"dev-bitbybit-cad": {
"url": "https://mcp.bitbybit.dev/mcp"
}
}
} {
"servers": {
"dev-bitbybit-cad": {
"type": "http",
"url": "https://mcp.bitbybit.dev/mcp"
}
}
} [mcp_servers.dev-bitbybit-cad] url = "https://mcp.bitbybit.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-bitbybit-cad": {
"type": "remote",
"url": "https://mcp.bitbybit.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-bitbybit-cad --url 'https://mcp.bitbybit.dev/mcp' --transport streamable-http
mcp_servers:
dev-bitbybit-cad:
url: "https://mcp.bitbybit.dev/mcp" {
"McpServers": {
"dev-bitbybit-cad": {
"Transport": "http",
"Url": "https://mcp.bitbybit.dev/mcp"
}
}
} assistant mcp add dev-bitbybit-cad -t streamable-http -u 'https://mcp.bitbybit.dev/mcp'
{
"mcpServers": {
"dev-bitbybit-cad": {
"type": "http",
"url": "https://mcp.bitbybit.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.
- 15 Oct 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.
- 13 Oct 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.
- 12 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “describe” rewrote its description, which is the text the model reads security
- Tool “get_guide” rewrote its description, which is the text the model reads security
- Schema quality: 133 → 188 ▼ functional
- Server version: 1.4.1 → 1.5.0 functional
- “get_guide” reworded the description of “topic” cosmetic
- “describe” reworded the description of “path” cosmetic
- Tool “get_guide” changed its title: Read the integration guide → Read the guides cosmetic
- 10 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 47 to 67. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 0
- Server version: 1.4.0 → 1.4.1 functional
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 0
- Server version: 1.3.2 → 1.4.0 functional
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 15 Oct 2026 · Probed https://mcp.bitbybit.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bitbybit.dev | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3e49425a738dec280e4e9e6d8877d2ef |
| SANs: bitbybit.dev, mcp.bitbybit.dev, *.mcp.bitbybit.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.bitbybit.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| bitbybit.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 | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.bitbybit.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.bitbybit.dev/mcp | HTTPS enforced | 301 | https://mcp.bitbybit.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 →
describe Describe an API member ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | 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 | – | The API version to describe; omit for the version the server holds |
No output schema declared.
No examples provided.
fetch Fetch ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A dotted API path returned by search |
No output schema declared.
No examples provided.
get_examples Get code examples ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Prefer members published for this engine when searching by topic |
| limit | integer | – | How many examples, 5 by default |
| path | string | – | A member or namespace path, for example occt.shapes.solid.createBox or occt.fillets |
| topic | string | – | Keywords to find examples by, when no path is known |
| version | string | – | The API version; omit for the version the server holds |
No output schema declared.
No examples provided.
get_guide Read the guides ~255
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | 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… |
No output schema declared.
No examples provided.
list_namespace List a namespace ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | A namespace path such as occt or occt.shapes; omit for the top level |
| version | string | – | The API version to list; omit for the version the server holds |
No output schema declared.
No examples provided.
search Search ~47
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search terms |
No output schema declared.
No examples provided.
search_api Search the Bitbybit API ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Only members published for this engine, plus the cloud operations, which run on CAD Cloud rather than in an engine; omit for every engine |
| limit | integer | – | How many results, 10 by default |
| query | string | yes | Keywords, a phrase, or a partial dotted path |
| version | string | – | The API version to search; omit for the version the server holds |
No output schema declared.
No examples provided.
What is the Bitbybit CAD MCP server?
Bitbybit CAD MCP is listed in the public MCP registry as dev.bitbybit/cad. Bitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guide. This page covers its hosted endpoint (https://mcp.bitbybit.dev/mcp).
Is the Bitbybit CAD MCP server safe to use?
Bitbybit CAD MCP scores 82 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 Bitbybit CAD MCP server expose?
Bitbybit CAD MCP exposes 7 tools: search_api, describe, list_namespace, get_examples, get_guide, and 2 more. Their descriptions and schemas cost roughly 961 tokens of context every time the server is loaded.
Does the Bitbybit CAD MCP server require authentication?
No. We connected to Bitbybit CAD MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bitbybit CAD MCP server still maintained?
Bitbybit CAD MCP is still listed as active in the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.