openPASO (alhermann/openPASO) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 77 tools. No publisher has claimed this listing.

Emerging

74/100

openPASO

Item: openPASO
Rating: 74
Author: M8ven

openPASO — open Platform for Agentic Simulation and Optimization. An AI agent that operates nine finite-element and multiphysics codes through one interface.

→ alhermann/openPASO · listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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 push why connect →

Who stands behind it

alhermann

Source: github_repo_search

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

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

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

🔐

You'll be asked for 1 credential: OPENROUTER_API_KEY

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// 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.

configOPENPASO_NO_FD_GUARD

configFOURC_ROOT

configOFA_DISABLE_PITFALLS

configOPENPASO_CELL_WORKDIR

configOPENPASO_CONFIG_JSON

configFOURC_BIN

configFOURC_LD

configFENICS_ROOT

configDEALII_ROOT

configNGSOLVE_ROOT

configSKFEM_ROOT

configKRATOS_ROOT

configDUNE_ROOT

configFOURC_BINARYAfterwards tell openPASO where they are: export =/path/to/4C and

configLD_LIBRARY_PATH

configOPENPASO_LEAN_PHYSICS

🔐 secretOPENROUTER_API_KEYThe .env file exists but the key line is blank. Paste your key after OPENROUTER_API_KEY=

configOPENPASO_MODELa different one, either change in .env, or add

configDEAL_II_DIR

configCMAKE_PREFIX_PATH

configCXX

configCC

configOPENPASO_DUNE_CACHE_BASELINE

configOPENPASO_PYTHON

configDEALII_DIR

configOPENPASO_KEY_PASSPHRASE

configSKFEM_PYTHON

configNGSOLVE_PYTHON

configDUNE_PYTHON. To see what openPASO itself finds, run python check_install.py — but

configKRATOS_PYTHON

configFENICS_PYTHON

configSPARTA_PYTHON

configFEBIO_PYTHON

configCOUPLING_PYTHON

configCONDA_PREFIX

configFOURC_PARAMS_DUMP

configFOURC_LD_LIBRARY_PATH

configOPENPASO_BLIND_KEYS

configT2_FIXTURES_DIR

configOFA_DISABLE_CRITIC

// 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

77/77 tools missing one or more hints — benchmark_problem (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); benchmark_poisson_cross_solver (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); knowledge (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +74 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.

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 2 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 Score](https://m8ven.ai/badge/mcp/alhermann/openpaso)](https://m8ven.ai/mcp/alhermann/openpaso)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: f857231310ffdb7148e87a9fdab579041ed43cff

code hash: 2b1da2e61ca038af73f5e510ad2cd1d355511fb42b9a5cb38386fa80853441e8

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