List your agent

MDEngine

MCP server● Hosted · onlineInstallablev0.7.1

MD workbench for agents: 13 analysis tools, renders, hosted GPU runs; LAMMPS + OpenMM

Reviews

No review yet. Used MDEngine? Be the first to help others choose.

What it does

MDEngine is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installYES
Version0.7.1
PackagesMCP bundle
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://api.forcefieldsilicon.com/mcp streamable-http

Install package

  • MCP BUNDLE https://github.com/forcefieldsilicon/mdengine/releases/download/v0.7.1/mdengine-mcp-0.7.1-macos-arm64.mcpb · runs locally (stdio)

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "mdengine": {
      "url": "https://api.forcefieldsilicon.com/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE MDEngine answered an MCP connection on 16 Nov 2026 and introduced itself as com.forcefieldsilicon/mdengine 0.11.0 (MCP protocol 2025-06-18).

14 tools offered to AI assistants

  • guide · No key needed. Without customer_type: the list of guides (one line each), the start page and how to get a key. With customer_type (mineral-processing | dark-proteins | alloys): the full guide, which says what to supply, what runs, what come
  • campaign_request · No key needed. Sends a study request to a person and returns a request_id, the tier that fits, the price band, what we still need from you, the next step and the claim scope. Nothing is run or charged. Call it after reading a guide.
  • account · Balance in USD (`balance_usd`), the part of it held by your unfinished jobs (`reserved_usd`, `held_jobs`) and what a new submit can use (`available_usd` = balance - reserved; a submit needs wall_limit_s x rate of it), how jobs are priced (`
  • submit_job · One call: create a hosted GPU job, upload the deck given INLINE as {relative_path: text}, and queue it. Total inline size <= 8 MB; for larger decks use create_job, PUT the tarball to upload_url, then start_job. Billing starts at the first h
  • create_job · Step 1 of the two-step path for big decks: validates the spec, reserves a job id, returns a presigned upload_url. PUT the deck as a .tar.gz (<= 2 GB, relative paths, input at `input`) to upload_url, then call start_job.
  • start_job · Step 2: queue a job whose deck tarball has been uploaded. A GPU pod is launched; billing starts when it reports running.
  • job_status · State (created|uploaded|queued|launching|running|uploading|done|failed|cancelled), GPU, rate, billed seconds, cost so far, exit code, error, last thermo lines, and the post-run verdict: clean | warnings (a done run whose log shows QEq CG fa
  • job_log · The last <= 20 thermo/log lines the running pod reported (30 s heartbeat). Full log.lammps is in the results tarball.
  • job_results · For a done/failed job: a presigned download_url (valid ~7 days) for the results tarball (work/, log.lammps, exitcode). Results are deleted 30 days after the run.
  • list_jobs · Jobs of this API key, newest first. Compact rows (id, state, label, created, finished, gpu, cost_usd, error) unless full=true.
  • delete_results · For a finished job: delete its deck and results tarballs immediately instead of at the automatic 30-day purge. Metadata and billing records are kept; results can no longer be downloaded.
  • capabilities · Capability manifest of the hosted runners: LAMMPS version, installed packages, and every style by category with gpu=true (KOKKOS-accelerated) or gpu=false (exists, but runs on the pod's CPU cores at the GPU rate). Default = compact summary;
Show 2 more
  • preflight_deck · Dry run of the check submit_job performs: which styles the deck asks for are MISSING on every hosted LAMMPS image (the run would exit at startup), which are CPU-only, whether its pair style will use the GPU at all, and which image (`runner`
  • cancel_job · Cancel a job that is not finished. A running job is billed up to the cancel time; its pod is terminated.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Install packagehttps://github.com/forcefieldsilicon/mdengine/releases/download/v0.7.1/mdengine-mcp-0.7.1-macos-arm64.mcpbDECLAREDSRC-001 Official MCP Registry1d ago
Hosted endpointhttps://api.forcefieldsilicon.com/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Package registriesmcpbDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)yesDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://forcefieldsilicon.com/mdengineDECLAREDSRC-001 Official MCP Registry1d ago
Repositoryhttps://github.com/forcefieldsilicon/mdengineDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version0.7.1DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run MDEngine? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor MDEngineLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of MDEngine?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/mdengine?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/mdengine/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about MDEngine

How do I connect MDEngine?

Use the hosted endpoint https://api.forcefieldsilicon.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does MDEngine need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does MDEngine offer?

When Electra Index connected on 16 Nov 2026, it listed 14 tools: guide, campaign_request, account, submit_job, create_job, start_job, job_status, job_log and more. The full list is in "Live check" above.

Is MDEngine online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.