_ registry / mcp streamable-http · checked 6h ago

com.forcefieldsilicon/mdengine

https://api.forcefieldsilicon.com

Registry code: 9b665457e9936f44

api record

MDEngine runs molecular dynamics on hosted GPUs for people who have a Claude, in three groups: semiconductor process materials, drug discovery and delivery, and mineral processing and critical metals, with a fourth guide for alloy wear and hardness studies (customer_type alloys). Call guide first, then capabilities and preflight_deck; all three work without a key, and after reading a guide, call campaign_request to start a study. To submit runs, buy a credit pack at https://forcefieldsilicon.com/mdengine and paste the key once on the sign-in page, never in chat.

endpoint
https://api.forcefieldsilicon.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is com.forcefieldsilicon/mdengine live?
Yes — it answered the hub's last check (checked 6h ago). It answered 99% of checks over the last 30 days.
Is com.forcefieldsilicon/mdengine free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does com.forcefieldsilicon/mdengine have?
14 tools: campaign_request, submit_job, create_job, start_job, delete_results, preflight_deck, cancel_job, capabilities, ….
Is com.forcefieldsilicon/mdengine safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99%

90 days 99.4%· all time 99.4%

latency
212ms

last good check

priced tools
0

of 14 tools

_ answered our checks, 90 days 358 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
health & science science & engineering
used for
  • run molecular dynamics on hosted gpu
  • check simulation job status
  • download job results
takes → gives
text, data → data, documents
tools
7 reads5 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 14 tools
2 open5 auth-required 7 never probed 7 of 14 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • capabilities reads open 31h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "full": {
      "type": "boolean",
      "description": "Include the full style table (large)"
    },
    "runner": {
      "type": "string",
      "description": "lammps | openmm; omit for all"
    }
  }
}
    arguments 13 lines
  • guide open 15h ago

    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 comes back and what it costs. With template (openmm-stability): the script text of that template, ready to save and submit.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "template": {
      "type": "string",
      "description": "openmm-stability (dark-proteins stage 1 OpenMM script); returns the script text"
    },
    "customer_type": {
      "type": "string",
      "description": "mineral-processing | dark-proteins | alloys; omit for the list"
    }
  }
}
    arguments 13 lines
  • job_status reads auth-required 6h ago

    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 failures, lost atoms, a fix halt, or no end_marker line; counts in `warnings`).

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Job id, e.g. MDJOB-20260907-3F200C"
    }
  }
}
    arguments 12 lines
  • job_log reads auth-required 6h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Job id, e.g. MDJOB-20260907-3F200C"
    }
  }
}
    arguments 12 lines
  • list_jobs reads auth-required 15h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "full": {
      "type": "boolean",
      "description": "Return the complete status object per job (default false)"
    },
    "limit": {
      "type": "integer",
      "description": "1..200, default 20"
    }
  }
}
    arguments 13 lines
  • job_results reads auth-required 6h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Job id, e.g. MDJOB-20260907-3F200C"
    }
  }
}
    arguments 12 lines
  • account reads auth-required 15h ago

    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 (`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, the key id of the API key in use, and `packs` (when the endpoint sells credit): [{id, name, usd, gpu_h, url}] to top up THIS key by appending ?client_reference_id=<key_id> to the pack url.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • campaign_request unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "customer_type",
    "question",
    "contact_email"
  ],
  "properties": {
    "grid": {
      "type": "string",
      "description": "Free text: compositions x temperatures, or ligands x pockets (e.g. 3 ligands x 1 receptor)"
    },
    "question": {
      "type": "string",
      "maxLength": 4000,
      "minLength": 20,
      "description": "One paragraph: the decision the study feeds"
    },
    "data_rules": {
      "type": "string",
      "description": "How the data and results may be used, kept or shared"
    },
    "organization": {
      "type": "string",
      "description": "Optional"
    },
    "contact_email": {
      "type": "string",
      "description": "Where the reply goes"
    },
    "customer_type": {
      "enum": [
        "mineral-processing",
        "dark-proteins",
        "alloys",
        "semiconductor",
        "other"
      ],
      "type": "string",
      "description": "mineral-processing | dark-proteins | alloys | semiconductor | other"
    },
    "inputs_available": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "What you can supply now, e.g. bath range, AlphaFold model, ligand list, alloy composition range"
    }
  }
}
    arguments 50 lines
  • submit_job changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "input",
    "files"
  ],
  "properties": {
    "gpu": {
      "type": "string",
      "description": "GPU class; call account for the offered classes and how jobs are priced. Default any = cheapest available"
    },
    "files": {
      "type": "object",
      "description": "Deck contents: {\"in.lmp\": \"...\", \"data.al\": \"...\"}; paths relative, no '..'; must include `input`",
      "additionalProperties": {
        "type": "string"
      }
    },
    "input": {
      "type": "string",
      "description": "Relative path of the LAMMPS (or runner) input script inside the deck, e.g. in.lmp"
    },
    "label": {
      "type": "string",
      "description": "Free text <= 120 chars shown in job lists"
    },
    "launch": {
      "type": "string",
      "description": "Launch template; omit for the default KOKKOS/CUDA LAMMPS command line"
    },
    "runner": {
      "type": "string",
      "description": "Runner flavour: lammps (default) or openmm (beta)"
    },
    "end_marker": {
      "type": "string",
      "description": "Optional line your deck prints when it truly finished (e.g. a `print DONE` at the end); a done job whose log lacks a line starting with it gets verdict=warnings, end_marker_missing=true"
    },
    "estimate_s": {
      "type": "integer",
      "description": "Your runtime guess in seconds; informational only; the pre-check uses wall_limit_s net of credit held by your unfinished jobs"
    },
    "wall_limit_s": {
      "type": "integer",
      "description": "Hard cap in seconds (default 14400, max 86400); the job fails at the cap and is billed to it"
    }
  }
}
    arguments 48 lines
  • create_job changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "input"
  ],
  "properties": {
    "gpu": {
      "type": "string",
      "description": "GPU class; call account for the offered classes and how jobs are priced. Default any = cheapest available"
    },
    "input": {
      "type": "string",
      "description": "Relative path of the LAMMPS (or runner) input script inside the deck, e.g. in.lmp"
    },
    "label": {
      "type": "string",
      "description": "Free text <= 120 chars shown in job lists"
    },
    "launch": {
      "type": "string",
      "description": "Launch template; omit for the default KOKKOS/CUDA LAMMPS command line"
    },
    "runner": {
      "type": "string",
      "description": "Runner flavour: lammps (default) or openmm (beta)"
    },
    "end_marker": {
      "type": "string",
      "description": "Optional line your deck prints when it truly finished (e.g. a `print DONE` at the end); a done job whose log lacks a line starting with it gets verdict=warnings, end_marker_missing=true"
    },
    "estimate_s": {
      "type": "integer",
      "description": "Your runtime guess in seconds; informational only; the pre-check uses wall_limit_s net of credit held by your unfinished jobs"
    },
    "wall_limit_s": {
      "type": "integer",
      "description": "Hard cap in seconds (default 14400, max 86400); the job fails at the cap and is billed to it"
    }
  }
}
    arguments 40 lines
  • start_job changes data unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Job id, e.g. MDJOB-20260907-3F200C"
    }
  }
}
    arguments 12 lines
  • delete_results changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Job id, e.g. MDJOB-20260907-3F200C"
    }
  }
}
    arguments 12 lines
  • preflight_deck reads unknown 31h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "input",
    "files"
  ],
  "properties": {
    "files": {
      "type": "object",
      "description": "Deck contents {path: text}, must include `input`",
      "additionalProperties": {
        "type": "string"
      }
    },
    "input": {
      "type": "string",
      "description": "Relative path of the LAMMPS (or runner) input script inside the deck, e.g. in.lmp"
    }
  }
}
    arguments 20 lines
  • cancel_job changes data unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Job id, e.g. MDJOB-20260907-3F200C"
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9b665457e9936f44.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9b665457e9936f44/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9b665457e9936f44/badge.svg)](https://brick.blue/agent/9b665457e9936f44?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.