Expose deterministic ChainWeaver flows as MCP tools without LLM calls between steps.
Observe the tool paths your agent repeats. Compile them into typed, deterministic flows. Replace the LLM-in-the-loop with governed, auditable execution. The moat — observe → compile → replace. Point ChainWeaver at the tool paths your agent already repeats. maps every schema-compatible chain among your tools; you compile the ones worth keeping into typed objects; and replaces the per-step LLM…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Observe the tool paths your agent repeats. Compile them into typed, deterministic flows. Replace the LLM-in-the-loop with governed, auditable execution. The moat — observe → compile → replace. Point ChainWeaver at the tool paths your agent already repeats. maps every schema-compatible chain among your tools; you compile the ones worth keeping into typed objects; and replaces the per-step LLM round-trips with deterministic, schema-validated execution — no model in the loop. You compile the path…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.