io.github.context-foundry/context-foundry

MCPcommunity
v2.2.1io.github.context-foundryUnknownUpdated 7mo agoGitHub

Recursive Claude spawning for autonomous project builds with self-healing test loops

Autonomous build loop that plans, builds, reviews, and learns. Foundry reads a task list and works through it using Claude Code agents in a TUI, committing each completed task. Several run modes control what happens next: run forever with discovery (Auto), stop when done (Sprint), pause for human review after each task (Review), or run unattended for the build service (Service). When to use the…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
7mo agoLast update
Package
Authorio.github.context-foundry
LicenseUnknown
Version2.2.1
Sourcemcp-registry
GitHubcontext-foundry/context-foundry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ 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>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
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✓ Cleanv2.5.4 · 19d 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

Autonomous build loop that plans, builds, reviews, and learns. Foundry reads a task list and works through it using Claude Code agents in a TUI, committing each completed task. Several run modes control what happens next: run forever with discovery (Auto), stop when done (Sprint), pause for human review after each task (Review), or run unattended for the build service (Service). When to use the pipeline: the harness is a multiplier for verifiable engineering work — tasks with references the…

Keywords
mcp