io.github.RAEN-DT/pynet-mcp-bridge
PYPI · PYNET-MCP-BRIDGE
MCP implementation to connect AI agents with the PyNet Platform for BIM/Engineering automation.
Available components
Last scanned (13 hours ago)
Scores higher than 59% of PyPI servers
Category Developer Tools
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1428 tokens (~59/item across 24 items; 24 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 24 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
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.
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.
- 23 Oct 26 51
First indexed and scored.
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 23 Oct 2026 · Analysed pypi/pynet-mcp-bridge@1.7.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| 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 →
check_plugin_status ~27
Handshake ping to verify the plugin listener is responsive.
| Name | Type | Req | Description |
|---|---|---|---|
| pid | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
configure_output_window ~36
Toggles the visibility of the PyNet log/output window.
| Name | Type | Req | Description |
|---|---|---|---|
| is_available | boolean | yes | – |
| pid | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_pynet_module ~37
Creates a new custom Tab (ButtonsModule) in the Ribbon.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| pid | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_pynet_module ~35
Permanently deletes a module and all its contents.
| Name | Type | Req | Description |
|---|---|---|---|
| module_id | string | yes | – |
| pid | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_script_button ~44
Permanently removes a ScriptButton from a module by Id.
| Name | Type | Req | Description |
|---|---|---|---|
| button_id | string | yes | – |
| module_id | string | yes | – |
| pid | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
deploy_script_button ~73
Installs a new ScriptButton into a specific module (Name, Script, Icon, Tooltip).
| Name | Type | Req | Description |
|---|---|---|---|
| icon_name | string | – | – |
| module_id | string | yes | – |
| name | string | yes | – |
| pid | integer | yes | – |
| script_Path | string | yes | – |
| tooltip | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_buttons_data ~34
Lists all script buttons for a specific module ID.
| Name | Type | Req | Description |
|---|---|---|---|
| module_id | string | yes | – |
| pid | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_output_window_status ~28
Checks if the output window is currently available/visible.
| Name | Type | Req | Description |
|---|---|---|---|
| pid | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_pynet_ui_layout ~31
Fetches the full UI structure (ButtonsModules and ScriptButtons).
| Name | Type | Req | Description |
|---|---|---|---|
| pid | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_active_instances ~40
Scans the system for running host processes (Autodesk, Rhino, PyNET for Tekla/Presto) with an active PyNet IPC pipe.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
send_command ~54
Direct script execution in the PyNet engine (Target PID, Script Name, Content).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| pid | integer | yes | – |
| script_name | string | yes | – |
| timeout | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
send_command_by_path ~58
Executes a script file directly by path in the PyNet engine, without sending content inline.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | – |
| pid | integer | yes | – |
| script_name | string | yes | – |
| timeout | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_script_button ~85
Updates metadata for an existing ScriptButton or moves it to another module.
| Name | Type | Req | Description |
|---|---|---|---|
| button_id | string | yes | – |
| dest_module_id | string | – | – |
| icon_name | string | yes | – |
| module_id | string | yes | – |
| name | string | yes | – |
| pid | integer | yes | – |
| script_Path | string | yes | – |
| tooltip | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viewer_clear ~18
Clears highlights and ghosting in the open viewer.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viewer_fit ~19
Fits the camera to all models in the open viewer.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viewer_get_properties ~236
Reads element properties (name, model, psets) from the loaded package's properties.json. Pass one or more pnt_ids to get their full properties (including psets) directly. Called with no pnt_ids, returns a paginated lightweight index (pnt_id, name, model) instead of every element — narrow it with `model` (exact model/discipline name, e.g. "Snowdon Towers Sample HVAC") and/or `search` (case-insensitive substring of the element name), and page through with `limit`/`offset` (default 200 per page, capped at 500). On a federated model the unfiltered index can have tens of thousands of entries — always pass `model` or `search` when you can, and use `offset` to page through the rest. The data source is the .pnt's properties.json, NOT the viewer or IFC.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| model | string | – | – |
| offset | integer | – | – |
| pnt_ids | array | – | – |
| search | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viewer_get_state ~82
Reads the viewer's last reported state: loaded models and the pnt_id of whatever the user currently has selected (click in the 3D view or the tree panel — null if nothing is selected). Use the returned pnt_id with viewer_get_properties for its details, or feed it into a clashes.json lookup to find what it clashes with.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viewer_highlight_clash ~91
Highlights a clash (element(s) A red, element(s) B green) and isolates the rest away. Usually one pnt_id per side (a single clash pair), but either side accepts a list — e.g. one element (A) against every counterpart it clashes with (B), all shown at once.
| Name | Type | Req | Description |
|---|---|---|---|
| pnt_id_a | – | – | – |
| pnt_id_b | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viewer_isolate ~37
Isolates (hides everything except) the given pnt_ids in the open viewer.
| Name | Type | Req | Description |
|---|---|---|---|
| pnt_ids | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viewer_isolate_models ~102
Shows only the given model(s)/discipline(s) (by exact name, e.g. "Snowdon Towers Sample HVAC"), hiding every other loaded model. Cheaper than viewer_isolate for "just show me this discipline" requests — no need to resolve every element's pnt_id first. Get the exact model names from viewer_get_state's "models" list. Undo with viewer_clear.
| Name | Type | Req | Description |
|---|---|---|---|
| models | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viewer_list_clashes ~43
Reads the loaded package's clashes.json — the data source, NOT the viewer/IFC. Returns each clash with the pnt_id identifiers needed to highlight it.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viewer_load_package ~36
Loads a .pnt into the open viewer and returns a summary read from clashes.json.
| Name | Type | Req | Description |
|---|---|---|---|
| pnt_path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viewer_select ~154
Highlights a set of elements in the open viewer by pnt_id, in neutral colours (yellow / blue) with nothing else hidden — a plain "look at these" pointer. Pass a list of pnt_ids in `pnt_ids` (group A). Optionally pass a second list in `pnt_ids_b` to highlight a second group in a distinct colour. Replaces any previous selection. Use viewer_list_clashes / viewer_get_properties to obtain pnt_ids. For a clash pair (red/green, with the rest of the model isolated away), use viewer_highlight_clash instead.
| Name | Type | Req | Description |
|---|---|---|---|
| pnt_ids | array | – | – |
| pnt_ids_b | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
viewer_status ~28
Reports whether a PyNet BIM Viewer is open in VS Code (port, package, data dir).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.RAEN-DT/pynet-mcp-bridge server?
io.github.RAEN-DT/pynet-mcp-bridge runs locally as a PyPI package, launched with uvx pynet-mcp-bridge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · pynet-mcp-bridge
claude mcp add raen-dt-pynet-mcp-bridge -- uvx pynet-mcp-bridge
What is the io.github.RAEN-DT/pynet-mcp-bridge server?
io.github.RAEN-DT/pynet-mcp-bridge is listed in the public MCP registry as io.github.RAEN-DT/pynet-mcp-bridge. MCP implementation to connect AI agents with the PyNet Platform for BIM/Engineering automation. This page covers its PyPI package (pynet-mcp-bridge).
Is the io.github.RAEN-DT/pynet-mcp-bridge server safe to use?
io.github.RAEN-DT/pynet-mcp-bridge scores 51 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. 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 io.github.RAEN-DT/pynet-mcp-bridge server expose?
io.github.RAEN-DT/pynet-mcp-bridge exposes 24 tools: list_active_instances, check_plugin_status, send_command, send_command_by_path, get_output_window_status, and 19 more. Their descriptions and schemas cost roughly 1,428 tokens of context every time the server is loaded.
Is the io.github.RAEN-DT/pynet-mcp-bridge server still maintained?
io.github.RAEN-DT/pynet-mcp-bridge is still listed as active in the MCP registry. We last reached this channel on 23 October 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 io.github.RAEN-DT/pynet-mcp-bridge server under?
io.github.RAEN-DT/pynet-mcp-bridge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.