# MIDAS Gen NX / Civil NX (mcpb · midas-nx-mcp-0.3.2.mcpb) Read and carefully change the model open in MIDAS Gen NX or Civil NX on this PC. - Trust score: 41/100 (low) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - mcpb · `midas-nx-mcp-0.3.2.mcpb`: 41/100 (this document), [markdown](https://verifymcp.io/servers/dennis5882-midas-nx-mcp/midas-nx-mcp.md), [page](https://verifymcp.io/servers/dennis5882-midas-nx-mcp/midas-nx-mcp) - pypi · `midas-nx-mcp`: 78/100, [markdown](https://verifymcp.io/servers/dennis5882-midas-nx-mcp/midas-nx-mcp-2.md), [page](https://verifymcp.io/servers/dennis5882-midas-nx-mcp/midas-nx-mcp-2) ## Channel facts - Registry: `mcpb` - Package: `https://github.com/Dennis5882/midas-nx-mcp/releases/download/v0.3.2/midas-nx-mcp-0.3.2.mcpb` - Transport: `stdio` - SHA-256: `b8842ee5c55f2e7262b180fb4153b6d9f8baa35e91b03dabe0b5a3746d843faf` ## 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-05. - **Supply Chain Security**: 12/100 - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package. - Known CVEs were checked across the 34 of 34 dependencies we could resolve, so this covers what we could see, not the whole tree. - Install-script risk not yet assessed. - 1 of 34 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 0 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 72/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 2725 tokens (~170/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 0/100 - Stability not yet verified: two runs of the same published version returned different tool surfaces, so we cannot tell a change in the package from a difference in our own sandbox run. - **Tool Coverage**: 71/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 0% of tool parameters carry a description. - Structured output schemas are declared (6% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). **Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the MIDAS Gen NX / Civil NX MCP server? MIDAS Gen NX / Civil NX ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, b8842ee5c55f2e7262b180fb4153b6d9f8baa35e91b03dabe0b5a3746d843faf; the commands to do that are on this page. If it does not match, do not open it. - Download bundle: `https://github.com/Dennis5882/midas-nx-mcp/releases/download/v0.3.2/midas-nx-mcp-0.3.2.mcpb` - SHA-256: `b8842ee5c55f2e7262b180fb4153b6d9f8baa35e91b03dabe0b5a3746d843faf` ### Verify on macOS / Linux ```bash echo "b8842ee5c55f2e7262b180fb4153b6d9f8baa35e91b03dabe0b5a3746d843faf midas-nx-mcp-0.3.2.mcpb" | shasum -a 256 -c ``` ### Verify on Windows (PowerShell) ```powershell (Get-FileHash -Algorithm SHA256 .\midas-nx-mcp-0.3.2.mcpb).Hash -eq "b8842ee5c55f2e7262b180fb4153b6d9f8baa35e91b03dabe0b5a3746d843faf" ``` ## 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-05 (score 41, 0) - [functional regression] Schema quality: 2449 → 2725 ### 2026-11-04 (score 41, +1) - [security] Stability: Stability not yet verified: two runs of the same published version returned different tool surfaces, so we cannot tell a change in the package from a difference in our own sandbox run. - [functional regression] Schema quality: 121 → 163 - [functional regression] Schema quality: 121 → 158 - [functional regression] Tool coverage: 15% → 7% - [functional] First check of Schema quality: 100 ### 2026-11-03 (score 40) First indexed and scored. ## MCP tools (16) ### `check_connection` (~61 tokens) Check whether the given MIDAS NX product is reachable through the Open API. Returns the connection status and the program name. A blocked NX session (an open dialog) can still report "connected"; a later read then times out. Input parameters: - `product` (string, required) ### `list_tables` (~107 tokens) List the tables this server can read: /db model data (e.g. "NODE") and /DESIGN design parameters (e.g. "DESIGN/STEEL/DSTL", the steel design code). product: keep only tables that product supports. search: case-insensitive text matched against the table name and title, e.g. "load", "section", "design". No NX call is made. Input parameters: - `product` - `search` (string) Output parameters: - `result` (array) ### `describe_table` (~55 tokens) The NX server's own field schema for one /db table (GET /info/db/). Call this before read_table to learn what each field means. Input parameters: - `product` (string, required) - `table` (string, required) ### `read_table` (~112 tokens) Records of one table in the open model, e.g. table="NODE" or "DESIGN/STEEL/DSTL". ids: return only these record ids. limit: at most this many records (capped by the server's MIDAS_MAX_ROWS). The reply says how many records the table holds in all, so a truncated answer is never mistaken for the whole table. Input parameters: - `ids` - `limit` - `product` (string, required) - `table` (string, required) ### `model_summary` (~62 tokens) Record counts of the main tables (nodes, elements, materials, sections, thicknesses, static load cases), plus the model's unit system. A table that fails to read is reported with its error, the rest still count. Input parameters: - `product` (string, required) ### `read_model_info` (~115 tokens) Model-wide information NX computes, not stored in a table. what: "project_status" (counts of model and load data), "section_properties" (computed area, inertia, ... per section id), "story_check_parameter" and "story_irregularity_parameter" (Gen only), or "selection" (what the user has selected in the NX window now). Entries keyed by id are capped like read_table. Input parameters: - `limit` - `product` (string, required) - `what` (string, required) ### `list_result_tables` (~147 tokens) List the result/report table types result_table accepts, by category. Categories: "model" (mass, weights, loads, sections, supports; no analysis needed), "analysis" (reactions, displacements, member forces, stresses, modes), "story" (Gen: story drift, displacement, shear, stability, irregularity checks), "design" (design member forces). Each category says what NX needs before its tables have data. search: case-insensitive text matched against the type and its name, e.g. "reaction", "beam", "drift". No NX call is made. Input parameters: - `category` - `search` (string) ### `result_table` (~287 tokens) One result table from the open model (POST /post/TABLE, nothing exported). table_type: from list_result_tables. Common ones: "REACTIONG" (support reactions), "DISPLACEMENTG" (nodal displacements), "BEAMFORCE" (beam/column member forces), "PLATEFORCEL" (plate forces), "EIGENVALUEMODE" (periods and modes), "STORY_MASS" / "STORYWEIGHT" (story mass and weight, no analysis needed), "STORY_DRIFT_X" / "STORY_DRIFT_Y" and "STORY_SHEAR_FOR_RS" (Gen story checks), "BEAMDESIGNFORCES" / "COLUMNDESIGNFORCES" (design forces). load_cases: names with a type suffix, e.g. ["DL(ST)", "COMB1(CB)"]; the model's load cases are in read_table("STLD"). components: column names to keep. keys: node or element ids to restrict to. Rows beyond limit (capped by MIDAS_MAX_ROWS) are counted, not returned. Input parameters: - `components` - `keys` - `limit` - `load_cases` - `product` (string, required) - `table_type` (string, required) ### `capture_view` (~96 tokens) A PNG of the model window as NX shows it now (POST /view/CAPTURE). Shows the current view: viewpoint, active elements and result display are whatever the user has set in NX; this tool does not change them. width and height are in pixels (each at most 2000); leave them out for the window size. Input parameters: - `height` - `product` (string, required) - `width` ### `show_result` (~341 tokens) Show an analysis result in the NX window and return it as a PNG. Like picking a result under Results in NX (POST /view/RESULTGRAPHIC, then /view/CAPTURE): the window keeps showing it afterwards. The model and its results are not changed. Needs the analysis run in NX. result and its components (default first): "reactions" FZ, FX, FY, MX, MY, MZ (values are always shown) "displacement" DXYZ, DX, DY, DZ (contour) "deformed_shape" DXYZ, DX, DY, DZ (deformed over undeformed) "beam_diagram" My, Mz, Fx (axial), Fy, Fz (shear), Mx (torsion) "plate_forces" Mxx, Myy, Mxy, Fxx, Fyy, Fxy load_case: a name from read_table("STLD"), e.g. "DL"; a combination with its type suffix as result_table takes it, e.g. "gLCB1(CB)", "cLCB1(CBC)". show_values writes the numbers on the picture; deform_scale scales the deformed shape (NX's own scale when left out). width/height: pixels, at most 2000 each. Input parameters: - `component` - `deform_scale` - `height` - `load_case` (string, required) - `product` (string, required) - `result` (string, required) - `show_values` (boolean) - `width` ### `run_analysis` (~118 tokens) Run the analysis in NX (POST /doc/ANAL). Two steps: preview, then apply. NX saves the open document over its file before analysing (leaving a .bak), unsaved changes included, even when it then refuses the analysis. So this needs a document that has been saved before, seen in the NX window title on this PC; a new, never-saved document would raise a Save As dialog that blocks NX, and is refused here. Input parameters: - `confirm_token` - `product` (string, required) ### `save_copy` (~136 tokens) Save the model as a new file in the output folder (POST /doc/SAVEAS). Two steps: preview, then apply. Like Save As in NX: from then on NX works on the copy, so the window, later saves and run_analysis use it, and the original file stays as it was last saved. The name is generated (mcp-save--