IFC MCP
NPM · IFC-MCP · SCANNED SEP 20
Local IFC/BIM MCP server with IfcOpenShell Python in Pyodide and an IFC viewer.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 40 of 115 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to flinker-app/ifc-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1044 tokens (~208/item across 5 items; 5 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 Management87
- Stability observed for 26 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run-python" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the IFC MCP server?
IFC MCP runs locally as an npm package, launched with npx -y ifc-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ifc-mcp
claude mcp add flinker-app-ifc-mcp -- npx -y ifc-mcp
{
"mcpServers": {
"flinker-app-ifc-mcp": {
"command": "npx",
"args": [
"-y",
"ifc-mcp"
]
}
}
} {
"servers": {
"flinker-app-ifc-mcp": {
"command": "npx",
"args": [
"-y",
"ifc-mcp"
]
}
}
} codex mcp add flinker-app-ifc-mcp -- npx -y ifc-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"flinker-app-ifc-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"ifc-mcp"
],
"enabled": true
}
}
} openclaw mcp add flinker-app-ifc-mcp --command npx --arg -y --arg ifc-mcp
mcp_servers:
flinker-app-ifc-mcp:
command: "npx"
args: ["-y", "ifc-mcp"] {
"McpServers": {
"flinker-app-ifc-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"ifc-mcp"
]
}
}
} assistant mcp add flinker-app-ifc-mcp -t stdio -c npx -a -y ifc-mcp
{
"mcpServers": {
"flinker-app-ifc-mcp": {
"command": "npx",
"args": [
"-y",
"ifc-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 −1
- Stability: pass → 0.97 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 20 Sept 2026 · Analysed npm/ifc-mcp@0.1.17
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | flinker-app/ifc-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/flinker-app/ifc-mcp/.github/workflows/publish-npm.yml@refs/heads/main |
| Rekor log index | 2418493981 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:51b5d6b2759c12a7ed1dd1605b25b8cac49ed2561dbbe5ba6d585ddf645012eaf6940574bbbbc6dbdd1e14b72f3c79fa63ca1f4fd6ee50919253daeea |
Background: How many MCP packages publish verified provenance →
Dependencies 115 packages
| Packages resolved | 115 |
|---|---|
| Stale | 40 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
clear-ifc-viewer clear IFC viewer ~59
Clear the already-open local IFC viewer by removing all loaded IFC files and BCF viewpoint state. This keeps the same stable viewer URL and does not close the browser tab. Use show-ifc-file after this to load a fresh IFC model.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
open-ifc-viewer open IFC viewer ~119
Open or show the local IFC viewer and return its stable viewer URL. This tool does not load IFC files and does not change selection/isolation state. After this tool returns, use the returned URL as the viewer address. If the client can open links, open that local URL; otherwise tell the user to open the URL in a browser or webview. Use show-ifc-file to show IFC files. Use set-bcf-view to apply a BCF viewpoint file. Do not use browser automation to click or select elements in the viewer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run-python run Python ~330
Execute LLM-created Python in the SDK Node/Pyodide IFC runtime. Use this tool for IFC inspection, validation, reports, exports, and creating new IFC files. Runtime context: Pyodide uses the bundled Pyodide 0.28.2 runtime. The package set includes micropip, ifcopenshell, numpy, pandas, matplotlib, shapely, and typing-extensions. The Python code is passed directly to the SDK. File inputs: pass IFC/IFCXML/IFCZIP file paths in the files array. In the desktop Node server these are local filesystem paths; in a browser host they are browser-defined paths resolved by that host. Generated Python can open those files by name, e.g. ifcopenshell.open("model.ifc") or open("model.ifc", "rb"). Return contract: this tool exposes stdout, stderr, saved_files, uploaded_files, and any result returned by the raw SDK. Generated files are returned as temporary localhost download URLs in saved_files. Do not assume files were written to the user's working directory.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Raw Python code to execute through the SDK. Files passed through files can be opened by name, e.g. ifcopenshell.open("model.ifc") or open("model.ifc", "rb"). |
| files | array | – | Optional array of IFC/IFCXML/IFCZIP file paths. Desktop hosts use local filesystem paths; browser hosts use browser-defined paths. |
| timeout_seconds | integer | – | Timeout in seconds. |
No output schema declared.
No examples provided.
set-bcf-view set BCF view ~385
Set the view state in the already-open local IFC viewer by applying a BCF/BCFZIP viewpoint file. Pass either a local BCF/BCFZIP file path or a generated BCF download URL from run Python saved_files. This tool does not show/load IFC files; use show-ifc-file for that. It should not open a new browser tab and should not use browser automation. To generate a BCFZIP with run-python, write a .bcfzip file, then call set-bcf-view with saved_files[0].url: ```python from uuid import uuid4 import ifcopenshell from bcf.v3 import model as mdl from bcf.v3.bcfxml import BcfXml from bcf.v3.visinfo import VisualizationInfoHandler model = ifcopenshell.open("sample.ifc") gid = model.by_type("IfcWall")[0].GlobalId component = mdl.Component(ifc_guid=gid) visinfo = mdl.VisualizationInfo( guid=str(uuid4()), components=mdl.Components( selection=mdl.ComponentSelection(component=[component]), visibility=mdl.ComponentVisibility( default_visibility=False, exceptions=mdl.ComponentVisibilityExceptions(component=[component]), ), ), ) bcf = BcfXml.create_new(project_name="IFC MCP") topic = bcf.add_topic("Review wall", "Review wall", "ifc-mcp", topic_type="Issue", topic_status="Open") topic.add_visinfo_handler(VisualizationInfoHandler(visinfo)) bcf_path = "view.bcfzip" bcf.save(bcf_path) print(str(bcf_path)) ```
| Name | Type | Req | Description |
|---|---|---|---|
| bcf_path | string | yes | Local BCF/BCFZIP file path, or a generated BCF download URL from run Python saved_files, to apply in the viewer. |
No output schema declared.
No examples provided.
show-ifc-file show IFC file ~151
Show one IFC file in the already-open local IFC viewer. Pass either a local IFC/IFCXML/IFCZIP file path or a generated IFC download URL from run Python saved_files. Use this for IFC model display only. Repeated calls add multiple IFC files to the same viewer. Returns the same stable viewer URL; after this tool returns, use that URL as the viewer address. Use open-ifc-viewer to open the viewer and set-bcf-view to apply a BCF viewpoint file.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Local IFC/IFCXML/IFCZIP file path, or a generated IFC localhost download URL from run Python saved_files, to load into the viewer. |
No output schema declared.
No examples provided.
What is the IFC MCP server?
IFC MCP is listed in the public MCP registry as io.github.flinker-app/ifc-mcp. Local IFC/BIM MCP server with IfcOpenShell Python in Pyodide and an IFC viewer. This page covers its npm package (ifc-mcp).
Is the IFC MCP server safe to use?
IFC MCP scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 IFC MCP server expose?
IFC MCP exposes 5 tools: run-python, open-ifc-viewer, show-ifc-file, clear-ifc-viewer, set-bcf-view. Their descriptions and schemas cost roughly 1,044 tokens of context every time the server is loaded.
Is the IFC MCP server still maintained?
IFC MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 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 IFC MCP server under?
IFC MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.