MCP.Market

FEA (finite element analysis) MCP server

online · 29% uptime
by TheRoboMaster123·io.github.TheRoboMaster123/mcp-fea·v1.0.0·1 stars
No reviews yet

Real FEA on CAD parts: validated setups, stress, safety factor, natural frequencies

B73/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B73/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed FEA (finite element analysis) yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

FEA (finite element analysis) tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 196ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (bearer)9/15
  • Maintenancelast push 93 days ago8/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How FEA (finite element analysis) compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 39% of 48,255 servers
Uptime
29%
of our recent checks; the typical remote server answers 100%
Response time
3,730 ms
faster than 3% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers

Install FEA (finite element analysis) in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp-fea https://therobomaster123--mcp-fea-mcp-endpoint.modal.run/mcp
Add to Cursor

What the publisher says

From the FEA (finite element analysis) repository's README, as published. We do not edit it. Read it on GitHub

mcp-fea

Real finite element analysis from a conversation. An AI assistant sends a STEP file and a plain-English question ("does this arm survive a 6 g maneuver with a 400 g motor?"); this MCP server maps the words onto geometry, rejects bad setups deterministically before any compute is spent, meshes and solves with CalculiX on Modal as an async MCP task, and returns a verdict backed by numbers — peak von Mises stress, factor of safety, deflection, natural frequencies — plus rendered stress plots and an interactive 3D viewer. Every study ends with a non-skippable reaction-balance check; every benchmark on the validation page is regenerated by CI on every commit.

Measured on the live deployment (2026-07-31): cold start 3.8 s · cantilever study submit→completed 9.3 s warm / 12.9 s with a cold solver container · ~$0.002 per study at Modal's posted rates.

Full table, mesh stats, and an explicit limitations section: docs/validation.md — regenerated by CI, never hand-edited.

Protocol: MCP 2026-07-28 (stateless core) with the io.modelcontextprotocol/tasks extension implemented per SEP-2663 (the official Python SDK v2 shipped without it — this repo also contains the client-side extension that teaches the official SDK to consume task-augmented servers) and an MCP Apps (SEP-1865) 3D viewer. See docs/decisions.md for every engineering call and why.

Deploy (3 commands)

uv sync
uv run modal secret create mcp-fea-token MCP_FEA_TOKEN=$(openssl rand -hex 24)
uv run modal deploy -m src.server.modal_app

Modal prints the endpoint URL (https://--mcp-fea-mcp-endpoint.modal.run). Connect any 2026-07-28 MCP client with Authorization: Bearer . First-time Modal users: uv run modal token new once. Then verify the live deployment end to end:

MCP_FEA_LIVE_URL=https://... MCP_FEA_TOKEN=... make verify-live

Tools

Task lifecycle: working (statusMessage walks validating → meshing → solving → postprocessing) → completed | failed | cancelled; tasks/cancel kills the running container. Tasks are retained 24 h.

Units policy

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-01restoreD → Bscore 73
  • 2026-10-15downgradeB → Dscore 45: Remote endpoint did not respond
  • 2026-10-01restoreD → Bscore 75

FEA (finite element analysis): common questions

Is FEA (finite element analysis) MCP server safe?
Mostly: it is graded B (73/100). Read the FEA (finite element analysis) safety report
How do I install FEA (finite element analysis)?
It runs remotely at therobomaster123--mcp-fea-mcp-endpoint.modal.run. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does FEA (finite element analysis) need an API key?
Yes. The registry entry asks for Authorization.
Is FEA (finite element analysis) maintained?
The last commit was 96 days ago (2026-07-31). The latest release is v1.0.0.
Is FEA (finite element analysis) up?
29% of our last 28 checks got an answer. We check remote servers about four times a day.
How does FEA (finite element analysis) compare with other MCP servers?
safety score 73/100 (higher than 39% of 48,255 servers); uptime 29% (of our recent checks; the typical remote server answers 100%); response time 3,730 ms (faster than 3% of 30,031 servers). Full comparison.