Other · Remote MCP server
FEA (finite element analysis)
Real FEA on CAD parts: validated setups, stress, safety factor, natural frequencies.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.TheRoboMaster123/mcp-fea- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-31
- Updated
- 2026-07-31
- Publisher
- TheRoboMaster123 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/TheRoboMaster123) · how
- Repository
- github.com/TheRoboMaster123/mcp-fea
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://therobomaster123--mcp-fea-mcp-endpoint.modal.run/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect FEA (finite element analysis)
FEA (finite element analysis) is a remote MCP server: there is nothing to install. Its endpoint is https://therobomaster123--mcp-fea-mcp-endpoint.modal.run/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Fcc RegulationsFCC Regulations MCP - US Federal Communications Commission rules (47 CFR). | Remote · HTTPLive check: ✓ handshake |
| fccdbExplore FCC ULS licenses, ASR antenna structures, and microwave path elevation profiles. | Remote · HTTPLive check: ✓ handshake |
| FcopFCoP Core adapter with 25 canonical tools and 6 read-only resources for durable agent work. | Local · stdio |
| FdicFDIC MCP - FDIC BankFind Suite API (free, no auth) | Remote · HTTPLive check: ✓ handshake |
| Feason ContextChristian source evidence for AI agents, with provenance, tradition coverage, and citation checks. | Remote · HTTPLive check: sign-in required |
| FeatureflipManage Featureflip feature flags, targeting and rollouts from AI agents and editors. | Local · stdio |
| Fed NicFederal Reserve National Information Center (NIC, ffiec.gov/npw) | Remote · HTTPLive check: ✓ handshake |
| Fed-SpendFederal contract intelligence: $7T+ awards, SAM.gov opps, pWin verdicts, recompetes, protests. | Remote · HTTPLive check: sign-in required |