Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentFEM

PYPI · AGENTFEM-MCP · SCANNED SEP 20

Build, run, inspect, and verify finite-element simulations with AgentFEM.

Available components

65 Trust /100
Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
  • 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
  • License check failed: the license (Apache Software License) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 5 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 324 tokens (~46/item across 7 items; 7 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
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

Install

How do I install the AgentFEM MCP server?

AgentFEM runs locally as a PyPI package, launched with uvx agentfem-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · agentfem-mcp

# add to Claude Code
claude mcp add haoming-luo-agentfem -- uvx agentfem-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "haoming-luo-agentfem": {
      "command": "uvx",
      "args": [
        "agentfem-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "haoming-luo-agentfem": {
      "command": "uvx",
      "args": [
        "agentfem-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add haoming-luo-agentfem -- uvx agentfem-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "haoming-luo-agentfem": {
      "type": "local",
      "command": [
        "uvx",
        "agentfem-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add haoming-luo-agentfem --command uvx --arg agentfem-mcp
# ~/.hermes/config.yaml
mcp_servers:
  haoming-luo-agentfem:
    command: "uvx"
    args: ["agentfem-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "haoming-luo-agentfem": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "agentfem-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add haoming-luo-agentfem -t stdio -c uvx -a agentfem-mcp
// mcp.json
{
  "mcpServers": {
    "haoming-luo-agentfem": {
      "command": "uvx",
      "args": [
        "agentfem-mcp"
      ]
    }
  }
}
Changelog

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.

  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 50

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Analysed pypi/agentfem-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

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
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~282 tokens

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 →

Tool Tokens
create_project ~46

Create a new project from one version-matched official AgentFEM template inside an approved root.

NameTypeReqDescription
name
pathstringyes
templatestring

Structured output declared, but exposes no named fields.

No examples provided.

describe_system ~39

Inspect the installed AgentFEM runtime and approved roots. Use summary first; request full only when selecting an advanced capability.

NameTypeReqDescription
detailstring

Structured output declared, but exposes no named fields.

No examples provided.

get_result_summary ~49

Read the structured scientific result for a completed job or the project's latest run, including its trust state.

NameTypeReqDescription
detailstring
job_id
pathstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_run_status ~40

Read one submitted run's status and any AgentFEM execution evidence currently available.

NameTypeReqDescription
job_idstringyes
pathstringyes

Structured output declared, but exposes no named fields.

No examples provided.

inspect_project ~28

Read project validation and recent immutable run identities without modifying the project.

NameTypeReqDescription
pathstringyes

Structured output declared, but exposes no named fields.

No examples provided.

submit_run ~52

After preflight, start a finite-element run in a separate process and return a durable job identity immediately.

NameTypeReqDescription
mpi_ranksinteger
namestring
pathstringyes

Structured output declared, but exposes no named fields.

No examples provided.

validate_project ~28

Run fail-closed structural and compatibility checks without solving the project.

NameTypeReqDescription
pathstringyes

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the AgentFEM MCP server?

AgentFEM is an MCP server listed in the public MCP registry as io.github.haoming-luo/agentfem. Build, run, inspect, and verify finite-element simulations with AgentFEM. This page covers its PyPI package (agentfem-mcp).

Is the AgentFEM MCP server safe to use?

AgentFEM scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 AgentFEM MCP server expose?

AgentFEM exposes 7 tools: describe_system, create_project, validate_project, inspect_project, submit_run, and 2 more. Their descriptions and schemas cost roughly 282 tokens of context every time the server is loaded.

Is the AgentFEM MCP server still maintained?

AgentFEM is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.