@bitbybit-dev/mcp

MCPattested
v1.3.2Bit By Bit DevelopersMITUpdated 1d agonpmGitHub

MCP server for the Bitbybit 3D CAD API: version-exact lookups of every function, its parameters, defaults and examples, for AI coding agents

Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
52Downloads/wk
203GitHub stars
23Forks
1d agoLast update
Package
AuthorBit By Bit Developers
LicenseMIT
Version1.3.2
Sourcenpm+mcp-registry
npm@bitbybit-dev/mcp
GitHubbitbybit-dev/bitbybit
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · e436c7b
Dependencies✓ 3 resolved · none vulnerable
Tool surface12 tools · none privileged
Security scan✓ Cleanv1.3.2 · 1d agoHow well does this scan work?
EvalsNone
IndexedSep 20, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · none privileged
Statically extracted from the published packagev1.3.2 · 1d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

describeNo description published

This tool published no description. Forge does not invent one.

fetchNo description published

This tool published no description. Forge does not invent one.

get_examplesNo description published

This tool published no description. Forge does not invent one.

get_guideNo description published

This tool published no description. Forge does not invent one.

list_namespaceNo description published

This tool published no description. Forge does not invent one.

search_apiNo description published

This tool published no description. Forge does not invent one.

searchNo description published

This tool published no description. Forge does not invent one.

echoRepeats the text

Repeats the text

No input schema was published for this tool.

browser_onlyAnswered by the client application

Answered by the client application

No input schema was published for this tool.

produceProduces a file

Produces a file

No input schema was published for this tool.

whoamiNames the caller

Names the caller

No input schema was published for this tool.

secretMembers only

Members only

No input schema was published for this tool.

5 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for the Bitbybit 3D CAD API: version-exact lookups of every function, its parameters, defaults and examples, for AI coding agents

Keywords
Bit By Bit DevelopersMCPModel Context ProtocolAIagentsClaudeCursorbitbybitbitbybit.devGeometryCAD3DJSCADOCCTOpenCascadeManifoldParametricModeling3D modelingOpenCascade Technology
Alternatives
Comparing tool surfaces…

Tools exposed

12 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-20 — observed resolution, not a publisher declaration.

3 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.