amesim-mcp (SometingGBBB/Simcenter-Amesim-MCP) is an MCP server listed on the M8ven Trust Index. It scores 41 out of 100, grade D. It declares 25 tools. No publisher has claimed this listing.

D
Warning
41/100

amesim-mcp

MCP server that exposes Siemens Simcenter Amesim's Circuit API as tools, enabling circuit creation, wiring, parameter setting, simulation, and result retrieval via natural language.

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

SometingGBBB

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Reads files from sensitive locations
Touches: ~/.ssh/config
// tools this server exposes25 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

execute_python

Execute Python code in the live Amesim worker process (persistent namespace).

connect

Connect to Simcenter Amesim. Starts a background worker process if none is running. Each worker serves exactly one session — calling connect() again while already connected is a no-op; call disconnect() first to switch versions or restart.

disconnect

Release the Amesim license token and stop the background worker process.

status

Check connection status and the Circuit API version.

create_circuit

Create a new, empty Amesim circuit (.ame file) and make it active.

open_ame_file

Open an existing .ame circuit file and make it active.

save_circuit

Save the active circuit.

close_circuit

Close the active circuit.

add_component

Add a component to the sketch of the active circuit.

move_component

Move a component to a new position. Connected lines are not moved with it.

rotate_component

Rotate a component's icon by -90 degrees, one or more times.

flip_component

Flip a component (mirror it) in the sketch.

remove_component

Remove a component from the active circuit.

connect_two_ports

Connect a port of one component/line to a port of another with a line.

remove_line

Remove a connection line from the active circuit.

create_supercomponent

Group components into a supercomponent (a reusable sub-circuit block).

change_submodel

Assign a submodel to a component or line.

get_parameter_value

Get the current value (and unit) of a parameter or state variable.

set_parameter_value

Set the value of a parameter or the initial value of a state.

get_parameter_infos

Get the type, title and unit of a parameter.

generate_code

Compile the active circuit. Required before running a simulation, and after any structural change (components, connections, submodels).

set_run_parameter

Set a run/simulation parameter of the active circuit.

run_simulation

Run a (temporal) simulation of the active circuit. Compile with generate_code() first, and again after any structural change, to make sure the run uses up-to-date code.

get_variable_values

Get the time-series values of a saved variable from the last simulation run. Returns a JSON array of [time, value] pairs.

get_variable_infos

Get metadata (type, title, unit) about a variable.

// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configADODBAPI_VERBOSE
configPROCESSOR_ARCHITECTURE
configPROXY_PORT
configPROXY_HOST
configLINES
configCOLUMNS
configFORCE_COLOR
configTERM
configtemp
configwindir
configcomspec
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

25/25 tools missing one or more hints — execute_python (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); connect (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); disconnect (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +22 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 2/25 tools referenced in tests (8%)

Write tests that reference each tool by name so every tool has at least one test.

No access to sensitive paths

Reads sensitive paths: ~/.ssh/config

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/sometinggbbb/simcenter-amesim-mcp?variant=verified)](https://m8ven.ai/mcp/sometinggbbb/simcenter-amesim-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: dc463726f3622633b6733d3ac8ddf31a82b60051
code hash: 9d00fff1db90e8aef3b9ec8af89d7c42f2d0fd4d6ce8d17a592620fc48b1f6a1
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client