PhySpace-Forge
Related Servers
Alternatives to PhySpace-Forge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceExposes a zero-dependency MCP server that ingests depth-sensor, joint-encoder, and tactile-array telemetry to deliver real-time spatial intelligence, trajectory generation, and safety-guarded control vectors for autonomous robots. It tracks shear-to-normal force ratios, detects micro-vibration slip onset, and adapts grasp force dynamically so agents can prevent object slip during manipulation.MIT
- AlicenseNot gradedqualityDmaintenanceExposes MuJoCo physics simulation to AI assistants via 65 MCP tools, enabling natural language control of robotics simulation, trajectory optimization, contact analysis, and video export.9MIT
- AlicenseNot gradedqualityBmaintenanceEnables real-time spatial intelligence, trajectory generation, and tactile control for autonomous robotic systems via MCP, including Coulomb friction cone checking, contact normal alignment, and grasp wrench quality evaluation.7MIT
- AlicenseAqualityBmaintenanceEnables an LLM to design parametric 3D parts in pure NumPy and verify they are actually printable before exporting them. Provides topology checks (watertightness, genus, shell count, wall thickness), self-rendered views, and gated STL/OBJ export that refuses broken solids.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables conversational creation and editing of STEP CAD models through MCP clients like Codex, Claude, or Cursor, with real-time 3D browser preview and tools for primitives, booleans, mounting holes, flanges, and gripper bases.1MIT
- AlicenseAqualityBmaintenanceProvides a local offline physics/chemistry simulation bench covering 12 domains, where plain-language intents are converted into simulation blueprints, solved with deterministic proof metrics, and exported to STL/OBJ — no cloud, API key, or LLM required.477 npm1Apache 2.0
TDQS
Scored across 5 tools
Each tool has a distinct primary action: inspect queries parameters, simulate runs a full trajectory check, compile exports assets, generate synthesizes scenes, and step performs a real-time shield update. The main potential confusion is between simulate_grasp_trajectory and step_realtime_safety_shield, since both verify grasp safety, but their descriptions clearly separate offline simulation from single-step real-time filtering.
All tools share the physpace_ prefix followed by a consistent verb_noun pattern: inspect_object, simulate_trajectory, compile_asset, generate_scene, step_shield. No deviations in casing or verb style, making the naming highly predictable.
Five tools is within the well-scoped 3-15 range, and each tool is clearly substantive, not filler. The count is slightly lean for a full physics/grasp pipeline, but every tool earns its place without redundancy.
The toolset covers a coherent pipeline: inspect parameters, simulate grasps, compile assets to multiple formats, generate scenes, and run real-time safety filtering. Minor gaps exist, such as no explicit catalog/list or update mechanism for registered objects, but agents can work around this.