ModelsAtlas
Explore
Atlas / MCP servers / horizungroup / naviscoord-mcp

naviscoord-mcpCAUTION

mcp/horizungroup/naviscoord-mcp
MCP server by horizungroup · aec · ai · autodesk · Audited 2026-10-10
⚑ Report / re-scanSource ↗

Open-source MCP server for Autodesk Navisworks Manage 2024-2026: AI-assisted BIM clash detection, root-cause analysis, coordination plans and verified model workflows.

Verdict
CAUTION
Grade
B
Trust score
83 /100
Exposed tools
—
Transport
stdio
License
MIT
Stars
16
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

Your next coordination meeting starts with a decision, not 10,000 clash rows.

Connect Autodesk Navisworks to ChatGPT Desktop Work, Claude Desktop, Claude Code and Codex. Ask what matters, inspect the evidence, and build a coordination plan.

English · Español

[](https://github.com/HorizunGroup/naviscoord-mcp/actions/workflows/ci.yml) [](https://github.com/HorizunGroup/naviscoord-mcp/releases/latest) [](LICENSE) [](docs/INSTALL.md)

Get started · Release evidence · Report a problem

1.1.1 is public: stable download · official MCP Registry entry.

“Analyze the open model. Show the most important coordination issues, explain their priority, and prepare the work plan. Show me the proposed changes before applying them.”

NavisCoord pairs a native Navisworks add-in with an open-source MCP server. The engine runs on your Windows workstation. The desktop runtime includes its Python dependencies: no Python installation, API key or build tools are needed for the packaged local server. Your chosen AI client and Autodesk licence remain separate products.

What you can do

Read from source at commit 0ecfd2aaa487OBSERVED · 2026-10-10
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude-code
claude mcp add naviscoord --env SMITHERY_API_KEY=${SMITHERY_API_KEY} -- uvx naviscoord
claude-desktop
{
  "mcpServers": {
    "naviscoord": {
      "command": "uvx",
      "args": [
        "naviscoord"
      ],
      "env": {
        "SMITHERY_API_KEY": "${SMITHERY_API_KEY}"
      }
    }
  }
}
03

Trust audit

CAUTIONgrade B · trust 83/100 Install with care. The audit found things worth knowing before you trust its output.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeWARN
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (5 observation(s))
Network
declared (7 observation(s))
Shell
declared (2 observation(s))
Dependencies
pinned
Secrets in source
none-found

Findings (12)

MEDIUMCode injection · code.dynamic_import · CWE-78, CWE-94, CWE-95
scripts/plugin_launcher.py:225
__import__(module)
MEDIUMCode injection · code.dynamic_import · CWE-78, CWE-94, CWE-95
scripts/plugin_launcher.py:235
"        __import__(module)\n"
MEDIUMNetwork egress · net.raw_ip · CWE-200, CWE-319
addin/NavisCoord.Addin/HttpBridge.cs:114
listener.Prefixes.Add($"http://127.0.0.1:{candidate}/");
MEDIUMNetwork egress · net.raw_ip · CWE-200, CWE-319
server/naviscoord/sessions.py:80
return f"http://127.0.0.1:{self.port}"
LOWInventory / provenance · inv.hidden_file · CWE-1104
.mcp.json.example
.mcp.json.example
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
server/tests/test_bundle.py:222
for hostile in ("../../etc", "..", "", "Torre A", "20260819T143012-XYZXYZ"):
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
server/tests/test_bundle.py:225
assert not is_generation_id("../../etc")
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
server/tests/test_safety.py:202
sandbox.resolve_file("../../escapado.pdf")
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
docs/PRIVACY.md:42
`http://127.0.0.1` on a port between 8781 and 8788, authenticated with a
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
docs/SECURITY-MODEL.md:21
`http://127.0.0.1:8781` (o el siguiente libre hasta 8788).
LOWObfuscation / stealth · obf.decode_call · CWE-506, CWE-94
server/naviscoord/imaging.py:1017
return base64.b64decode(raw)
LOWInventory / provenance · mcp.no_tools_extracted · CWE-1104
server.json
Why it matters. the tool list is enumerated at runtime by tools/list, not declared in source
Fix. the page says so rather than showing an empty table

Gates applied: no_behavioural_pass.

Audited 2026-10-10 · audit v0.4.1 · source sha 0ecfd2aaa487full audit observations/trust-audit/mcp-server/horizungroup__naviscoord-mcp.json · Report an issue / request a re-scan
04

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-100ecfd2aaa487CAUTIONB83first audit
05

Questions

What is the naviscoord-mcp MCP server?

Open-source MCP server for Autodesk Navisworks Manage 2024-2026: AI-assisted BIM clash detection, root-cause analysis, coordination plans and verified model workflows.

Is naviscoord-mcp safe to connect to an agent?

With care. The audit graded it B (83/100) and found 12 things worth knowing before you trust this server, listed below with the exact line each was found on.

What credentials does naviscoord-mcp need?

It reads SMITHERY_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.

How does naviscoord-mcp run?

It speaks stdio, so it runs as a local process your client starts. It is published on PyPI as naviscoord.

How current is this page?

The grade is for one exact copy of the source (0ecfd2aaa487), read on 2026-10-10. The repository is watched and re-audited when it changes.

Advertisement