io.github.dgenio/chainweaver

MCPcommunity
v0.12.1io.github.dgenioUnknownUpdated 2mo agoGitHub

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…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
Authorio.github.dgenio
LicenseUnknown
Version0.12.1
Sourcemcp-registry
GitHubdgenio/ChainWeaver
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ Cleanv0.12.1 · 2mo ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

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…

Keywords
mcp