Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
IFC Viewer Online is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
IFC/BIM with a 3D viewer: validate IFC, check IDS, Health Score, drawings, digital twins.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user ifc-viewer-online-mcp '--' npx -y ifc-viewer-mcp
# 2 — ask your agent for something these tools do
# validate_ifc, list_validation_rules, check_ids and 7 more
IFC Viewer Online costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts IFC Viewer Online as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user ifc-viewer-online-mcp '--' npx -y ifc-viewer-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Check an IFC (BIM) model against the IFC Viewer Online rule set — schema, spatial structure, names, GlobalIds, ISO 19650, classification, MEP and more — and return its Health Score (0–100, higher is better), issue counts, the rules that cost the most points and the first issues with links to fix…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | Path to a local file (absolute, or relative to where the server runs) or a public http(s) URL. |
| maxIssues | integer | no | How many issues to list (the counts always cover all of them). |
| rules | array | no | Run only these rule ids (see list_validation_rules). Default: the viewer's default rules. |
List every rule validate_ifc can run: its id, category, severity and whether it is on by default. Use it to pick rules for validate_ifc or to explain what a rule checks.
No parameter schema on file.
Check an IFC model against an IDS file (buildingSMART Information Delivery Specification 1.0) and return, per specification, pass/fail, how many elements applied, passed and failed, and the first failures with the element and the reason. Runs locally; nothing is uploaded. Use it when the user has…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ifc | string | yes | The IFC model: local path or public http(s) URL. |
| ids | string | yes | The IDS: local path, public URL, or the IDS XML text itself. |
| maxFailures | integer | no | Failures to list per specification. |
Build a link that opens one or more public IFC files in the free IFC Viewer Online 3D viewer (runs in the browser: orbit, section, measure, properties, validation with Health Score badge). Optional: drop them on the city map, isolate a class, pick a camera view, open a floor plan in the drawings…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| models | array | yes | Public http(s) URLs of IFC files. Several URLs load together as one federated scene. Local paths do not work here: the browser has to download the file. |
| view | string | no | Camera view once the models load. |
| map | boolean | no | Place the models on the 3D city map at their own georeference. |
| isolate | string | no | Show only this IFC class, e.g. IfcWall, IfcDoor, IfcSpace. |
| ui | string | no | Interface preset: full (all panels), minimal, kiosk (no chrome), client (read-only for clients), article (for embedding in pages). |
| validate | boolean | no | Run validation after loading (default true). |
| scans | array | no | Public point-cloud URLs (LAS/LAZ/E57/PLY…) to load with the models. |
| lang | string | no | Interface language: en, es, ca, fr, de, it, pt, ja, zh or th. |
Build a link that opens IFC models with the drawings pane beside the 3D view and a floor plan already cut from the model. In that pane the user can also drop DXF or PDF drawings, place them over the model, calibrate the scale, compare plan against model, add dimensions and text, and export to DXF,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| models | array | yes | Public http(s) URLs of IFC files. Several URLs load together as one federated scene. Local paths do not work here: the browser has to download the file. |
| lang | string | no | Interface language: en, es, ca, fr, de, it, pt, ja, zh or th. |
Read a DXF drawing (ASCII, R12 to current) and summarise it: DXF version, units, layers with how many entities each, entity types, drawing extents and the text found on it (room names, labels, title block). Runs locally. Use it to tell what a drawing contains before placing it next to a model with…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | Path to a local file (absolute, or relative to where the server runs) or a public http(s) URL. |
| maxTexts | integer | no | How many text strings to return. |
Link to the 3D sketch studio: draw strokes in 3D space with a pen, finger or mouse — over a blank canvas or around a model — on a phone, tablet, foldable or desktop, and export to SVG, PSD, ORA or Blender. Free, in the browser, no account. Use it when the user wants to sketch an idea, mark up a…
No parameter schema on file.
List the ready-made city digital twins (Barcelona, Helsinki, Tokyo): georeferenced IFC models on terrain and the OpenStreetMap city, painted with live open data (bikes, EV chargers, traffic, air quality, trains). Each has a link and an embed link. Also returns the link to the twin builder, where…
No parameter schema on file.
Read entities from a FIWARE context broker (Orion, Orion-LD, Scorpio, Stellio) over NGSI-LD or NGSIv2 and return them as flat records (id, type, each attribute value with its unit, lat/lon, observedAt) — the same shape the viewer's twin panel binds to IFC elements. The request goes from this…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| broker | string | yes | Broker root, e.g. https://orion.example.com:1026 |
| api | string | no | ld = NGSI-LD, v2 = NGSIv2. |
| type | string | no | Entity type, e.g. AirQualityObserved, ParkingSpot. NGSI-LD needs one. |
| tenant | string | no | NGSILD-Tenant / Fiware-Service, if the broker uses one. |
| servicePath | string | no | Fiware-ServicePath (NGSIv2 only). |
| context | string | no | JSON-LD @context URL (NGSI-LD), for short attribute names. |
| limit | integer | no | How many entities to return. |
Search the Port de Barcelona BIM object library (cranes, bollards, fenders, signs, buildings… IFC, CC BY 4.0) by words and category. Each hit has its IFC download URL and a link that opens it in the 3D viewer. Use it when the user needs port or maritime infrastructure objects for a model or twin.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Words to look for in the object name, e.g. "grua", "bolardo", "crane". Empty lists everything. |
| category | string | no | Only this category (the answer lists them). |
| limit | integer | no | — |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install IFC Viewer Online or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish IFC Viewer Online can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.