Stop your AI from reinventing infrastructure. Connect it to curated tools, real migration data, and verified combinations — one command.
Curated, not crawled
Every tool is reviewed by a human before listing. No abandoned projects, no spam, no enterprise products dressed up as indie. What your agent finds is actually maintained.
Migration data from 4,500+ repos
Not opinions — git history. We parsed real repos to find what developers are actually switching to. Your agent gets recommendations backed by 422 confirmed migration paths, not blog posts.
Verified tool combinations
93,000+ tool pairings observed in real projects. When your agent recommends Supabase + Prisma, it’s because they coexist in hundreds of repos — not because both have “database” in their description.
Built for agent workflows
21 purpose-built MCP tools: search by need, get integration docs, analyze dependency health, report outcomes. Agents get structured data, not HTML to parse.
claude mcp add indiestack -- uvx --from indiestack indiestack-mcp
Run this in your terminal. IndieStack will appear as a tool source in your next session.
Drop this in your project root. Your agent will check dependency health scores and search for existing tools before writing infrastructure from scratch.
# Dependency Health Rules ## Setup MCP: `claude mcp add indiestack -- uvx --from indiestack indiestack-mcp` ## CRITICAL: Package Validation Before installing ANY new package via npm, pip, yarn, or pnpm: 1. Call `validate_package(package, ecosystem)` to verify it exists and isn't a typosquat 2. If risk_level is "danger": DO NOT INSTALL. The package is hallucinated or a typosquat. 3. If risk_level is "caution": warn the user — package may be unmaintained 4. After successfully integrating any tool, call `report_outcome(slug, success=true)` ## Before Writing Infrastructure Before writing auth, payments, databases, email, monitoring, or any common infrastructure from scratch, call `find_tools(query)` first. Use an existing tool instead of generating code. 8,000+ tools indexed. ## Available Tools - `validate_package(package, ecosystem)` — PRE-FLIGHT CHECK before every install (catches hallucinations, typosquats) - `analyze_dependencies(manifest)` — 0-100 health score for your full manifest - `find_tools(query)` — search developer tools by need - `get_tool_details(slug)` — integration docs, API specs, install commands - `check_health(slugs)` — verify tools are still maintained - `get_migration_data(package)` — real migration paths from GitHub repos - `report_outcome(slug, success)` — report integration result
Download: CLAUDE.md | .cursorrules | AGENTS.md
Automatically score dependency health on every pull request that changes your manifest.
name: Stack Health Check
on:
pull_request:
paths:
- 'package.json'
- 'requirements.txt'
permissions:
pull-requests: write
jobs:
health-check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: Pattyboi101/stack-health-check@master
Add this to .github/workflows/stack-health.yml — every PR that changes dependencies gets a health score comment.
An API key unlocks higher rate limits and personalized recommendations.