Two things arrive together: evidence the package is real, and evidence about what it works alongside - which turns an agent's confident install command into a decision whose basis you can see.
A guardrail between an AI coding agent and the package it is about to install. It checks the package exists rather than being hallucinated or typosquatted, and backs the choice with a curated index of developer tools and compatibility data mined from public repositories.
- Tools searched across the index with filters for price, health, stars, success rate, language, tags and compatibility
- Compatibility both ways: what works with a given tool, grouped by category, with verified stacks and conflict warnings
- A tool's full record - integration code, pricing, API specifics and compatibility data
- A project scanned, or its dependencies analysed, so the advice is about what you actually have
- Health scores, side-by-side comparisons, and a build-versus-buy assessment for the thing you were about to write yourself
- A whole stack assembled from a description, plus categories, tags, published stacks and newly added tools to browse
- Outcomes and compatibility reported back into the index, and your own tool published into it
Uvx or pipx - one line wires it into Claude Code with nothing installed, and editors take the same command as a config entry. It works as a plain CLI too. The curation filter is independent developers and small teams, so large-vendor tooling is not what the index is built to cover.
One command — claude mcp add indiestack -- uvx --from indiestack indiestack-mcp