Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory

Future Micro Mold Lab

MCP server · www.futuremicromoldllc.com · found in a public list · checked since 2026-11-16

Live, handshake completed · latest check

As JSON

Calculates injection-moulding settings: cavity balance, cooling time, viscosity, gate seal.

Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/7). What this means

Placed in Engineering and construction calculations: Electrical, mechanical, RF and HVAC engineering calculations, simulations and building quantities and costs.

https://www.futuremicromoldllc.com/api/mcp MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person.

Our checks

An unpaid request daily, from eastern North America

Last 1 checks, oldest to newest; room for 29 more

1 passed, 0 failed, 29 not run.

Passed, 30 daysshort history1 of 1 run
Checks missed0in 30 days
Response, latest557 mswhole handshake
Scheduledailyset by usage; rule below
Checked since2026-11-16under 1 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hourssince 2026-11-1610——————
7 dayssince 2026-11-1610——————
30 dayssince 2026-11-1610——————

Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Tools listed by the server

cavity_balancecooling_timecosmetic_windowgage_rrgate_sealget_study_protocolopen_study_sheetplan_process_developmentpressure_dropprocess_capabilityviscosity_curve

Tools
11
This list since
2026-11-16
First listed to us
2026-11-16
List changes, 90 days
0

Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions

Access

Our latest check
Nothing asked
Stated
not stated
Payment model
not known
Currency
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Interface it declares

Protocol
MCP 2025-06-18
Capabilities
resourcestools
Transports
streamable-http

As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions

Calls it declares

  • viscosity_curve points intensificationRatio machineMaxPressure context study_code
  • cavity_balance levels context study_code
  • pressure_drop stages machineMaxPressure intensificationRatio context study_code
  • cosmetic_window xAxis yAxis points context study_code
  • gate_seal points context study_code
  • cooling_time points dimensionName dimensionTolerance context study_code
  • process_capability samples usl lsl target subgroupSize withinMethod study_code
  • gage_rr operators tolerance context study_code
  • get_study_protocol study*
  • plan_process_development completed setpoints
  • open_study_sheet study* setpoints

From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.

Listing

In the capability tree: Calculate and convert / Calculators, maths and science / Engineering and construction calculations (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/7, tree/3) on 2026-11-16. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:EWR
Live, handshake completed HTTP 200 557 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
  • Limited evidence: monitored for under 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_2e7e496cf4d93fbc