HTTP + SSE bridge for YADE MCP server - runs inside YADE Python environment
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"yade-mcp-bridge","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# yade-mcp-bridge [](https://pypi.org/project/yade-mcp-bridge/) HTTP + SSE bridge that runs inside a YADE process and enables execution tools for [yade-mcp](https://pypi.org/project/yade-mcp/). ## Features - **Async tasks with progress polling.** Submit a long simulation script (`execute_task`) and poll its status and paginated log while it runs (`check_task_status`). - **Live code during a run.** Send `execute_code` at any time to inspect state or tune parameters mid-cycle — no need to bake probes into the script up front. It shares the simulation's `__main__` namespace. - **Graceful interrupt.** Stop a long cycling task on request (`interrupt_task`) without killing the YADE process. - **Unified output capture.** Python `print` and YADE console output are interleaved in execution order in the task log. - **Zero third-party dependencies.** Pure stdlib HTTP + SSE. ## Architecture YADE's Qt GUI objects are main-thread-only, so the bridge keeps `execute_code` on the main thread while running each task on its own thread — a long `O.run()` then never blocks the server or live code. ```mermaid flowchart TD C[MCP client] -->|POST /command| S[HTTP + SSE server<br/>background thread] C -.->|GET /events| S S -->|execute_code → queue| Q[CodeExecutor<br/>one at a time] Q -->|Qt timer GUI / daemon console| P[pump thread] S -->|execute_task| T[ScriptRunner<br/>one thread per task] T -->|O.run| Y[YADE C++ sim loop] Y -.->|PyRunner callback| I[interrupt check] S -.->|doorbells| C ``` - **HTTP + SSE server (background thread).** A threaded HTTP server takes `POST /<command>` request/response calls and serves one long-lived `GET /events` SSE stream. It hands work off rather than touching YADE directly, so lightweight calls (status, interrupt) stay responsive even while a long task runs. - **execute_code pump.** `execute_code` submissions are serialized through a queue …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.