# AIBIMTool (npm · aibimtool-mcp)

Design buildings as IFC4 BIM models from a brief: an AI architect that plans, builds and edits.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `aibimtool.com`: 38/100, [markdown](https://verifymcp.io/servers/meltflexdevs-aibimtool/aibimtool.md), [page](https://verifymcp.io/servers/meltflexdevs-aibimtool/aibimtool)
- npm · `aibimtool-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/meltflexdevs-aibimtool/aibimtool-mcp.md), [page](https://verifymcp.io/servers/meltflexdevs-aibimtool/aibimtool-mcp)

## Channel facts

- Registry: `npm`
- Package: `aibimtool-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 23 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 872 tokens (~87/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the AIBIMTool MCP server?

AIBIMTool runs locally as an npm package, launched with npx -y aibimtool-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add meltflexdevs-aibimtool -- npx -y aibimtool-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "meltflexdevs-aibimtool": {
      "command": "npx",
      "args": [
        "-y",
        "aibimtool-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "meltflexdevs-aibimtool": {
      "command": "npx",
      "args": [
        "-y",
        "aibimtool-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add meltflexdevs-aibimtool -- npx -y aibimtool-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "meltflexdevs-aibimtool": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "aibimtool-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add meltflexdevs-aibimtool --command npx --arg -y --arg aibimtool-mcp
```

### Hermes

```yaml
mcp_servers:
  meltflexdevs-aibimtool:
    command: "npx"
    args: ["-y", "aibimtool-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "meltflexdevs-aibimtool": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "aibimtool-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add meltflexdevs-aibimtool -t stdio -c npx -a -y aibimtool-mcp
```

### Other

```json
{
  "mcpServers": {
    "meltflexdevs-aibimtool": {
      "command": "npx",
      "args": [
        "-y",
        "aibimtool-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 68, +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.

### 2026-11-17 (score 67, +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.

### 2026-11-14 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 62)

First indexed and scored.

## MCP tools (10)

### `create_building` (~97 tokens)

Design a building

Start designing a new building from a brief; the agent may ask questions or propose a plan, then builds an IFC4 model. Returns a project_id at once. Spends credits (metered, failed runs refunded).

Input parameters:

- `brief` (string, required): The design brief in the user's words.
- `level` (string): easy is quickest and cheapest, high the most careful (paid plans). Default medium.
- `title` (string)

### `send_message` (~84 tokens)

Message the architect

The next message to a project's agent: answers to its questions, a change, or a follow-up. Spends credits.

Input parameters:

- `level` (string): easy is quickest and cheapest, high the most careful (paid plans). Default medium.
- `message` (string, required)
- `project_id` (string, required): The project's id, as create_building or list_projects returned it.

### `approve_plan` (~53 tokens)

Approve the plan

The go-ahead for the agent's plan (state needs_approval), once the user agreed. Spends credits.

Input parameters:

- `project_id` (string, required): The project's id, as create_building or list_projects returned it.

### `continue_building` (~49 tokens)

Continue building

Go on after a run stopped at its time limit (state needs_continue). Spends credits.

Input parameters:

- `project_id` (string, required): The project's id, as create_building or list_projects returned it.

### `get_project_status` (~77 tokens)

Project status

State, the agent's reply, questions, plan and element count. Waits up to wait_seconds while the agent runs; call it in a loop until state is not running.

Input parameters:

- `project_id` (string, required): The project's id, as create_building or list_projects returned it.
- `wait_seconds` (integer): Default 30.

### `list_projects` (~16 tokens)

List projects

The account's projects, newest first.

### `get_model_image` (~152 tokens)

Look at the model

A PNG of the model, iso (3D) or plan (rooms named and measured), written to disk and shown. For a building with several storeys pass `storey` with a plan, or every storey is drawn over the others. Free; up to a minute when the model is not loaded.

Input parameters:

- `output_path` (string): A file or folder to write to. Default ./aibimtool-output/.
- `project_id` (string, required): The project's id, as create_building or list_projects returned it.
- `storey`: With view plan: the storey's name ("Level 2") or its number from the ground floor (0).
- `view` (string)

### `get_ifc_download` (~88 tokens)

Download the IFC

Write the model as an IFC4 file (Revit, ArchiCAD, BlenderBIM, Tekla, Navisworks) and return its path. Free.

Input parameters:

- `output_path` (string): A file or folder to write to. Default ./aibimtool-output/.
- `project_id` (string, required): The project's id, as create_building or list_projects returned it.

### `stop_building` (~46 tokens)

Stop the agent

Stop a running agent after its current step. The steps it took are charged.

Input parameters:

- `project_id` (string, required): The project's id, as create_building or list_projects returned it.

### `check_credits` (~20 tokens)

Credits

Plan and credits left, and how messages are charged.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/meltflexdevs-aibimtool/aibimtool-mcp#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 66
- 2026-11-15: 66
- 2026-11-14: 66
- 2026-11-13: 65
- 2026-11-12: 65
- 2026-11-11: 64
- 2026-11-10: 64
- 2026-11-09: 63
- 2026-11-08: 63
- 2026-11-07: 62
- 2026-11-06: 62

## Common questions

### What is the AIBIMTool MCP server?

AIBIMTool is an MCP server listed in the public MCP registry as io.github.MeltFlexDevs/aibimtool. Design buildings as IFC4 BIM models from a brief: an AI architect that plans, builds and edits. This page covers its npm package (aibimtool-mcp).

### Is the AIBIMTool MCP server safe to use?

AIBIMTool scores 69 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 AIBIMTool MCP server expose?

AIBIMTool exposes 10 tools: create_building, send_message, approve_plan, continue_building, get_project_status, and 5 more. Their descriptions and schemas cost roughly 682 tokens of context every time the server is loaded.

### Is the AIBIMTool MCP server still maintained?

AIBIMTool is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the AIBIMTool MCP server under?

AIBIMTool declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the AIBIMTool MCP server?

VerifyMCP ran 16 checks on AIBIMTool, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/aibimtool-mcp
- Socket report: https://socket.dev/npm/package/aibimtool-mcp
- Repository: https://github.com/MeltFlexDevs/aibimtool-skills
- Website: https://aibimtool.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/meltflexdevs-aibimtool/aibimtool-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/meltflexdevs-aibimtool/aibimtool-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/meltflexdevs-aibimtool/aibimtool-mcp.json
- HTML version of this page: https://verifymcp.io/servers/meltflexdevs-aibimtool/aibimtool-mcp
