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

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

Available components

−4 this week 88 Trust /100

Last scanned (18 hours ago)

Scores higher than 91% of PyPI servers

Category Health and Science

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 build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to haoming-luo/agentfem-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 50 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 Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 −5
    • Stability: pass → 0.63 functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
  • 27 Oct 26 0
    • Stability: pass → 0.97 functional
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 20 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.83 → pass security
  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

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

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo haoming-luo/agentfem-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/haoming-luo/agentfem-mcp/.github/workflows/publish.yml@refs/tags/v0.1.0
Rekor log index 2833576827
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:95aecfe5d784aa96c690047c34f99c1d2064eda8d05d5f85315dc8b4af2ab4f1

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 28 packages
Packages resolved 28
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.

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
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 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 4 November 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 AgentFEM MCP server under?

AgentFEM declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.