MDEngine

Name: MDEngine
Author: com.forcefieldsilicon

MCP serverMCP

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

by com.forcefieldsiliconrepository ↗homepage ↗v0.7.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mdengine","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability110/110 checks ok

when	check	result	http	latency	detail
1 h ago	mcp initialize	ok	200	39 ms	server com.forcefieldsilicon/mdengine 0.10.0 · protocol 2025-06-18 · 14 tools
8 h ago	mcp initialize	ok	200	44 ms	server com.forcefieldsilicon/mdengine 0.10.0 · protocol 2025-06-18 · 14 tools
14 h ago	mcp initialize	ok	200	32 ms	server com.forcefieldsilicon/mdengine 0.10.0 · protocol 2025-06-18 · 14 tools
21 h ago	mcp initialize	ok	200	32 ms	server com.forcefieldsilicon/mdengine 0.10.0 · protocol 2025-06-18 · 14 tools
28 h ago	mcp initialize	ok	200	31 ms	server com.forcefieldsilicon/mdengine 0.10.0 · protocol 2025-06-18 · 14 tools
34 h ago	mcp initialize	ok	200	34 ms	server com.forcefieldsilicon/mdengine 0.10.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	35 ms	server com.forcefieldsilicon/mdengine 0.10.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	38 ms	server com.forcefieldsilicon/mdengine 0.8.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	65 ms	server com.forcefieldsilicon/mdengine 0.6.0 · protocol 2025-06-18 · 12 tools
3 d ago	mcp initialize	ok	200	43 ms	server com.forcefieldsilicon/mdengine 0.6.0 · protocol 2025-06-18 · 12 tools

Tools observed via MCP handshake

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-pro
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 th
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` = balan
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_j
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 p
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,
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 ca
capabilities — Capability manifest of the hosted runners: LAMMPS version, installed packages, and every style by category with gpu=true (KOKKOS-accelerated) or gpu=false (exis
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
cancel_job — Cancel a job that is not finished. A running job is billed up to the cancel time; its pod is terminated.

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.forcefieldsilicon/mdengine

first seen 1 mo ago · fetched 23 h agoopen ↗

Field history (11 recent events)

26 d ago · declared · version → "0.7.1"
29 d ago · declared · summary → "MD workbench for agents: 13 analysis tools, renders, hosted GPU runs; LAMMPS + OpenMM."
29 d ago · declared · description → "MD workbench for agents: 13 analysis tools, renders, hosted GPU runs; LAMMPS + OpenMM."
29 d ago · declared · version → "0.7.0"
1 mo ago · declared · repoUrl → "https://github.com/forcefieldsilicon/mdengine"
1 mo ago · declared · summary → "MD workbench for agents: inspect/render trajectories, depth profiles, detached LAMMPS jobs."
1 mo ago · declared · protocols → ["mcp"]
1 mo ago · declared · version → "0.6.3"
1 mo ago · declared · description → "MD workbench for agents: inspect/render trajectories, depth profiles, detached LAMMPS jobs."
1 mo ago · declared · publisherName → "com.forcefieldsilicon"
1 mo ago · declared · homepageUrl → "https://forcefieldsilicon.com/mdengine"

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from