app.scanbim/scanbim-mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor identity continuity, MCP tool inventory, permissions and adoption.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

BIM/AEC/Revit/Autodesk model analysis and file operations MCP

What we know

BIM/AEC/Revit/Autodesk model analysis and file operations MCP. Published by the owner of npm package @scanbim-labs/scanbim-mcp. AI Hub for AEC — 46 tools for Revit, Navisworks, ACC, XR via Autodesk Platform Services.

Maintenance / activity evidence

178 npm downloads, 2026-09-09 to 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high_for_identity_and_metrics_medium_for_verified_package_description.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required. Reported action classes: Upload and share BIM models; Create RFIs. Complete write authority is not verified.
Autodesk Platform Services credentials and scopes
Sensitive access: Service account information and data accessible by supplied credentials

AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 178 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @scanbim-labs/scanbim-mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T04:43:53Z.

All limitations / Review context

Has @scanbim-labs/scanbim-mcp changed publishing identity, permissions, install requirements, or risk exposure?

Published package documentation reviewed; public listing with prominently disclosed risks: AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required.

AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.
Autodesk Platform Services credentials and scopes
Reviewed write actions: Upload and share BIM models; Create RFIs
Sensitive access: Service account information and data accessible by supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Respect upstream entitlements, version constraints and least-privilege setup.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Original activity observations

178 npm downloads, 2026-09-09 to 2026-10-08

Technical identity

npm/@scanbim-labs/scanbim-mcp

Exact implementation source: https://www.npmjs.com/package/@scanbim-labs/scanbim-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@scanbim-labs/scanbim-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Registry source ↗
registry.modelcontextprotocol.io/v0/servers
Source material retained for this review.
Package registry ↗
@scanbim-labs/scanbim-mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Autodesk/ScanBIM ecosystem setup; separate Revit/ACC/Navi integrations depend on host environment.
Remote endpoint: register https://scanbim-mcp.itmartin24.workers.dev/mcp as Streamable HTTP in a compatible MCP client. Cloudflare self-deployment is separate; do not infer the five Autodesk workers are all running.
Configure / authenticate
MCP100 setup guide
Use publisher hosted Streamable HTTP ScanBIM endpoint https://scanbim-mcp.itmartin24.workers.dev/mcp; optional Cloudflare self-deployment is separate and requires APS_CLIENT_ID and APS_CLIENT_SECRET. One endpoint does not deploy all distinct Revit/ACC/Navisworks workers.
streamable_http: https://scanbim-mcp.itmartin24.workers.dev/mcp
Client registration: not independently verified
Check connection
Suggested check
Publisher: curl https://scanbim-mcp.itmartin24.workers.dev/health checks service/APS state, NOT authenticated MCP tool success.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Hosted access: no user-issued API key is required by the documented hosted entry. Self-hosted APS_CLIENT_ID / APS_CLIENT_SECRET rotation requires Autodesk APS account procedures, not verified here.

Official Documentation & Sources

What it does

BIM/AEC/Revit/Autodesk model analysis and file operations MCP. Published by the owner of npm package @scanbim-labs/scanbim-mcp. AI Hub for AEC — 46 tools for Revit, Navisworks, ACC, XR via Autodesk Platform Services.

Capability: Design & Creative
Resource type: MCP Server
Industry: Real Estate & Construction
Best fit: BIM/AEC/Revit/Autodesk model analysis and file operations MCP

Representative uses

BIM/AEC/Revit/Autodesk model analysis and file operations MCP

Limitations

AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Autodesk Platform Services credentials and scopes
Permissions: AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required.
Data handling: AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required.
Cost: Credit/subscription costs may apply; inspect provider docs
Risk and cautions: AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required.

Access scope and cautions

Write actions: Not verified Upload and share BIM models Create RFIs
Sensitive access: Service account information and data accessible by supplied credentials
Risk level: high
Security notes: AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required. Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T04:43:53Z. Watchlist tracking is not a recommendation or a security certification.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Do not infer shell entrypoint or automated credential setup if a command is not explicitly verified. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Autodesk Platform Services credentials and scopes

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Upload and share BIM models; Create RFIs. Recorded permission context: AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required.

What data-handling boundary should I consider?

AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required. Recorded sensitive-access context: Service account information and data accessible by supplied credentials.

What limitations and risks should I check before use?

AEC/Revit/BIM/Autodesk workflows may upload building model/IP data and create RFIs or share models; Autodesk entitlements and scopes required. Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes. Public exact-package npm downloads observed for recent 30-day window. Public listing suitability does not imply safe installation or entitlement to access third-party accounts. Respect upstream entitlements, version constraints and least-privilege setup.

What cost model is recorded?

The reviewed cost model is Credit/subscription costs may apply; inspect provider docs. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.