io.github.flinker-app/ifc-mcp

Name: io.github.flinker-app/ifc-mcp
Rating: 60 (1 reviews)
Author: io.github.flinker-app

MCPcommunity

v0.1.6io.github.flinker-appUnknownUpdated 21d agonpm

Local IFC/BIM MCP server with IfcOpenShell Python in Pyodide and an IFC viewer.

IFC MCP lets your AI assistant inspect IFC/BIM files, create IFC files, create reports, open IFC models in a viewer, and apply BCF viewpoints. After installation, ask your AI client in normal language. You do not need to know the technical tool names. Good example prompts: When the viewer opens, IFC MCP returns a local viewer link. If your AI client does not open it automatically, open that link…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

21d agoLast update

Package

Authorio.github.flinker-app

LicenseUnknown

Version0.1.6

Sourcemcp-registry

npmifc-mcp

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ 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>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface5 tools · none privileged

Security scan✓ Cleanv0.1.6 · 20d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp