# MDEngine (remote · api.forcefieldsilicon.com)

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

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.forcefieldsilicon.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-forcefieldsilicon-mdengine/api.md), [page](https://verifymcp.io/servers/com-forcefieldsilicon-mdengine/api)
- mcpb · `osx-arm64`: 10/100, [markdown](https://verifymcp.io/servers/com-forcefieldsilicon-mdengine/https-github-com-forcefieldsilicon-mdengine-releases-download-v0-7-1-mdengine-mc.md), [page](https://verifymcp.io/servers/com-forcefieldsilicon-mdengine/https-github-com-forcefieldsilicon-mdengine-releases-download-v0-7-1-mdengine-mc)

## Channel facts

- Endpoint: `https://api.forcefieldsilicon.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.7.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_results).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1449 tokens (~120/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MDEngine MCP server?

MDEngine is a hosted endpoint at https://api.forcefieldsilicon.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-forcefieldsilicon-mdengine 'https://api.forcefieldsilicon.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-forcefieldsilicon-mdengine": {
      "url": "https://api.forcefieldsilicon.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-forcefieldsilicon-mdengine": {
      "type": "http",
      "url": "https://api.forcefieldsilicon.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-forcefieldsilicon-mdengine]
url = "https://api.forcefieldsilicon.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-forcefieldsilicon-mdengine": {
      "type": "remote",
      "url": "https://api.forcefieldsilicon.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-forcefieldsilicon-mdengine --url 'https://api.forcefieldsilicon.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-forcefieldsilicon-mdengine:
    url: "https://api.forcefieldsilicon.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-forcefieldsilicon-mdengine": {
      "Transport": "http",
      "Url": "https://api.forcefieldsilicon.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-forcefieldsilicon-mdengine -t streamable-http -u 'https://api.forcefieldsilicon.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-forcefieldsilicon-mdengine": {
      "type": "http",
      "url": "https://api.forcefieldsilicon.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 73, +1)

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

### 2026-09-17 (score 72, +1)

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

### 2026-09-15 (score 71, +1)

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

### 2026-09-13 (score 70, +1)

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

### 2026-09-11 (score 69, 0)

- [security] Tool “account” rewrote its description, which is the text the model reads
- [cosmetic] “create_job” reworded the description of “gpu”
- [cosmetic] “submit_job” reworded the description of “gpu”
- [cosmetic] Tool “account” changed its title: Account balance and rates → Account balance and pricing

### 2026-09-10 (score 69, +1)

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

### 2026-09-09 (score 68, 0)

- [functional] Server version: 0.5.0 → 0.6.0

### 2026-09-08 (score 68, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “delete_results”, which the server declares destructive
- [security] Tool “list_jobs” rewrote its description, which is the text the model reads
- [security] Tool “submit_job” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 1038 → 1410
- [functional improvement] Stability: unverified → 0.03
- [functional] Destructive annotations: pass → 100
- [functional] Server version: 0.2.0 → 0.5.0
- [functional] New tool “capabilities”
- [functional] New tool “preflight_deck”
- [cosmetic] “list_jobs” added an optional parameter “full”
- [cosmetic] “create_job” reworded the description of “gpu”
- [cosmetic] “create_job” reworded the description of “runner”
- [cosmetic] “list_jobs” reworded the description of “limit”
- [cosmetic] “submit_job” reworded the description of “gpu”
- [cosmetic] “submit_job” reworded the description of “runner”

## MCP tools (12)

### `account` (~67 tokens)

Account balance and pricing

Balance in USD, how jobs are priced (`pricing.mode` job = the deck's own work in atom-steps at per-class prices, capped at wall_limit_s x rate; metered = per second of pod time), the rate table, and the key id of the API key in use.

### `submit_job` (~313 tokens)

Submit a deck (inline files) and start it

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 heartbeat (state running) and stops at done/failed/cancelled. The deck is executed as a program on an isolated GPU pod.

Input parameters:

- `estimate_s` (integer): Your runtime guess in seconds; only used for the balance pre-check (min 900 s at the rate)
- `files` (object, required): Deck contents: {"in.lmp": "...", "data.al": "..."}; paths relative, no '..'; must include `input`
- `gpu` (string): GPU class; call account for the offered classes and how jobs are priced. Default any = cheapest available
- `input` (string, required): Relative path of the LAMMPS (or runner) input script inside the deck, e.g. in.lmp
- `label` (string): Free text <= 120 chars shown in job lists
- `launch` (string): Launch template; omit for the default KOKKOS/CUDA LAMMPS command line
- `runner` (string): Runner flavour: lammps (default) or openmm (beta)
- `wall_limit_s` (integer): Hard cap in seconds (default 14400, max 86400); the job fails at the cap and is billed to it

### `create_job` (~253 tokens)

Create a job (returns upload URL)

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.

Input parameters:

- `estimate_s` (integer): Your runtime guess in seconds; only used for the balance pre-check (min 900 s at the rate)
- `gpu` (string): GPU class; call account for the offered classes and how jobs are priced. Default any = cheapest available
- `input` (string, required): Relative path of the LAMMPS (or runner) input script inside the deck, e.g. in.lmp
- `label` (string): Free text <= 120 chars shown in job lists
- `launch` (string): Launch template; omit for the default KOKKOS/CUDA LAMMPS command line
- `runner` (string): Runner flavour: lammps (default) or openmm (beta)
- `wall_limit_s` (integer): Hard cap in seconds (default 14400, max 86400); the job fails at the cap and is billed to it

### `start_job` (~60 tokens)

Start an uploaded job

Step 2: queue a job whose deck tarball has been uploaded. A GPU pod is launched; billing starts when it reports running.

Input parameters:

- `id` (string, required): Job id, e.g. MDJOB-20260907-3F200C

### `job_status` (~75 tokens)

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.

Input parameters:

- `id` (string, required): Job id, e.g. MDJOB-20260907-3F200C

### `job_log` (~61 tokens)

Job log tail

The last <= 20 thermo/log lines the running pod reported (30 s heartbeat). Full log.lammps is in the results tarball.

Input parameters:

- `id` (string, required): Job id, e.g. MDJOB-20260907-3F200C

### `job_results` (~76 tokens)

Results download URL

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.

Input parameters:

- `id` (string, required): Job id, e.g. MDJOB-20260907-3F200C

### `list_jobs` (~74 tokens)

List jobs

Jobs of this API key, newest first. Compact rows (id, state, label, created, finished, gpu, cost_usd, error) unless full=true.

Input parameters:

- `full` (boolean): Return the complete status object per job (default false)
- `limit` (integer): 1..200, default 20

### `delete_results` (~69 tokens)

Delete a job's files now

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.

Input parameters:

- `id` (string, required): Job id, e.g. MDJOB-20260907-3F200C

### `capabilities` (~119 tokens)

What the runner can do

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; runner=lammps&full=true returns the whole style table. Use preflight_deck to check a specific deck.

Input parameters:

- `full` (boolean): Include the full style table (large)
- `runner` (string): lammps | openmm; omit for all

### `preflight_deck` (~144 tokens)

Check a deck before spending

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`) the job will be routed to — decks needing packages beyond the fast default image run on lammps-full automatically. Nothing is created or billed.

Input parameters:

- `files` (object, required): Deck contents {path: text}, must include `input`
- `input` (string, required): Relative path of the LAMMPS (or runner) input script inside the deck, e.g. in.lmp

### `cancel_job` (~56 tokens)

Cancel job

Cancel a job that is not finished. A running job is billed up to the cancel time; its pod is terminated.

Input parameters:

- `id` (string, required): Job id, e.g. MDJOB-20260907-3F200C

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-forcefieldsilicon-mdengine/api#diagnostics

## Score history

- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72
- 2026-09-17: 72
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 69
- 2026-09-09: 68
- 2026-09-08: 68
- 2026-09-07: 68

## Common questions

### What is the MDEngine MCP server?

MDEngine is an MCP server listed in the public MCP registry as com.forcefieldsilicon/mdengine. MD workbench for agents: 13 analysis tools, renders, hosted GPU runs; LAMMPS + OpenMM. This page covers its hosted endpoint (https://api.forcefieldsilicon.com/mcp).

### Is the MDEngine MCP server safe to use?

MDEngine scores 73 out of 100 on VerifyMCP. 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 MDEngine MCP server expose?

MDEngine exposes 12 tools: account, submit_job, create_job, start_job, job_status, and 7 more. Their descriptions and schemas cost roughly 1,367 tokens of context every time the server is loaded.

### Does the MDEngine MCP server require authentication?

No. We connected to MDEngine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MDEngine MCP server still maintained?

MDEngine 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.

## Links

- Remote endpoint: https://api.forcefieldsilicon.com/mcp
- Authorisation metadata: https://api.forcefieldsilicon.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/forcefieldsilicon/mdengine
- Website: https://forcefieldsilicon.com/mdengine
- Changelog RSS feed: https://verifymcp.io/servers/com-forcefieldsilicon-mdengine/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-forcefieldsilicon-mdengine/api.json
- HTML version of this page: https://verifymcp.io/servers/com-forcefieldsilicon-mdengine/api