https://api.forcefieldsilicon.com/mcp ↗
MD workbench for agents: 13 analysis tools, renders, hosted GPU runs; LAMMPS + OpenMM.
MDEngine is a remote MCP server published at api.forcefieldsilicon.com. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 191 ms, placing it among the faster endpoints. It offers a narrow, focused set of 12 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
account — Name is too generic, doesn't indicate balance or API key management purposecapabilities — Description doesn't clarify when to use it for runner selectionpreflight_deck — Parameter 'files' lacks format specification in descriptionsubmit_job — Multiple parameters (gpu, runner) lack explicit value examplesRisk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
accountBalance 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_jobOne 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.
inputstringrequiredlabelstringgpustringwall_limit_sintegerestimate_sintegerrunnerstringlaunchstringfilesobjectrequiredcreate_jobStep 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.
inputstringrequiredlabelstringgpustringwall_limit_sintegerestimate_sintegerrunnerstringlaunchstringstart_jobStep 2: queue a job whose deck tarball has been uploaded. A GPU pod is launched; billing starts when it reports running.
idstringrequiredjob_statusState (created|uploaded|queued|launching|running|uploading|done|failed|cancelled), GPU, rate, billed seconds, cost so far, exit code, error, last thermo lines.
idstringrequiredjob_logThe last <= 20 thermo/log lines the running pod reported (30 s heartbeat). Full log.lammps is in the results tarball.
idstringrequiredjob_resultsFor 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.
idstringrequiredlist_jobsJobs of this API key, newest first. Compact rows (id, state, label, created, finished, gpu, cost_usd, error) unless full=true.
limitintegerfullbooleandelete_resultsFor 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.
idstringrequiredcapabilitiesCapability 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.
runnerstringfullbooleanpreflight_deckDry 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.
inputstringrequiredfilesobjectrequiredcancel_jobCancel a job that is not finished. A running job is billed up to the cancel time; its pod is terminated.
idstringrequiredDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/com-forcefieldsilicon-mdengine)<a href="https://mcpmetrics.io/servers/com-forcefieldsilicon-mdengine"><img src="https://mcpmetrics.io/badge/com.forcefieldsilicon/mdengine/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
130+ QA & dev tools for AI agents: prompt injection, RAG testing, VLM eval, guardrails. Free.
Decision Layer for AI Agents — 58+ tools, Advisor, MCP. Free key: POST /v1/register {}.
Base mainnet analysis: contract audits, transfer simulation, token pricing. Paid via x402.
Make AI phone calls from any AI assistant. BubblyPhone's MCP server lets you manage AI-powered phone agents — book reservations, schedule appointments, set up customer support lines, or have your AI agent call anyone on your behalf. ## Features - **Make AI phone calls** — Initiate outbound calls with AI agents (Gemini, GPT) that handle the conversation - **Manage phone numbers** — Search, purchase, and configure numbers in 30+ countries - **Configure AI agents** — Set system prompts, choose AI models, select voices - **Monitor calls** — View call events, transcripts, and recordings - **Track billing** — Check balance, usage, and transaction history - **Mid-call control** — Inject context, transfer calls, or hang up ## 20 Tools `make_call` · `list_calls` · `get_call` · `hangup_call` · `transfer_call` · `inject_context` · `get_call_transcript` · `get_call_events` · `search_phone_numbers` · `list_phone_numbers` · `buy_phone_number` · `get_phone_number` · `update_phone_number` · `get_b
A collection of validation and utility tools for Latin American markets. Covers Brazil (CPF, CNPJ, PIX key validation, national holidays), Mexico (RFC validation, national holidays), and Chile (RUT validation, national holidays). Designed for agents and applications handling tax forms, invoices, payments, e-commerce, and compliance workflows across Latin America.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 01:33:33 | Legacy | 200 | 193 | 200 | 191 | 2025-11-25 |
| 2026-09-12 23:31:36 | Legacy | 200 | 409 | 200 | 408 | 2025-11-25 |
| 2026-09-12 21:29:15 | Legacy | 200 | 74 | 200 | 77 | 2025-11-25 |
| 2026-09-12 19:27:29 | Legacy | 200 | 191 | 200 | 190 | 2025-11-25 |
| 2026-09-12 17:24:09 | Legacy | 200 | 172 | 200 | 172 | 2025-11-25 |
| 2026-09-12 15:21:42 | Legacy | 200 | 334 | 200 | 334 | 2025-11-25 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Open bounty protocol for AI agents. 22 tools: token safety scans + paid missions. 0.5% fee.
Comments
Sign in to write a comment
No comments yet. Be the first.