tidy3d-research
Related Servers
Alternatives to tidy3d-research
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides secure filesystem operations, HTTP fetching with SSRF protection, JSON validation, artifact logging, and optional Redis key-value storage through both stdio and HTTP transports. Features production-ready security controls including sandbox enforcement, allowlist validation, and comprehensive input validation.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run declarative agents and DAG workflows as plain tools, with parallel nodes, review loops, and per-run least-privilege sandboxing.13 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables evaluating AI applications, inspecting reliability evidence, and gating releases from development and CI workflows.27Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to safely run bounded, sandboxed tasks on remote machines with persistent state and reviewable artifacts.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables deterministic, resumable workflow automation through DAG step graphs, boolean gate branching, automatic parallel execution, and in-step agent loops with sandboxed file and command tools.7 npm1MIT

polyflowofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to run model-checked workflows durably, receiving one work order at a time with guarantees on admission.13 npmApache 2.0
TDQS
Scored across 8 tools
Each tool maps to a distinct stage in the Tidy3D simulation workflow—cost estimation, validation, upload, start, status, download, local normalization, and artifact reading. Even the result-handling tools are separated clearly by source and purpose.
All tool names follow a consistent snake_case verb_noun pattern with unambiguous verbs (estimate, validate, upload, start, get, download, normalize, read). The naming is uniform and predictable.
Eight tools is well-scoped for a Tidy3D research workflow, covering the full simulation lifecycle without unnecessary redundancy or bloat. Each tool earns its place in the pipeline.
The core lifecycle is covered end-to-end: validate, upload, start, monitor, download, normalize, and read. Cancel/delete operations for tasks are absent, but these are not critical for the apparent research workflow.