find_toolsLABSCO SUMMARY
The dependency is checked before it is installed, not after the build fails.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command — claude mcp add indiestack -- uvx --from indiestack indiestack-mcp
USE CASES
01
Stopping an agent installing a package that does not exist
Look the tool up before the install command runs - a hallucinated or typosquatted name has no record behind it.
02
Choosing the auth or payments piece for a stack you already have
Ask what is compatible with what you run and read the conflict warnings, rather than finding out at integration time.
03
Assembling a stack from a description
Say what the project needs and get back a set that has been seen working together, with the install commands attached.
04
Deciding whether to write it yourself
Run the build-versus-buy assessment against what already exists in the category before committing a sprint to it.
05
Auditing what a project has accumulated
Scan the project, analyse its dependencies, and check the health of the ones you are still carrying.
06
Feeding back what actually happened
Report the outcome and the compatibility you found, so the next person's answer is better than yours was.
19 tools
Listed in project docs. Your client may show a different list.
find_compatibleget_tool_detailsscan_projectreport_compatibilityreport_outcomecheck_healthlist_categoriescompare_toolsbuild_stackpublish_toolbrowse_new_toolslist_tagsget_market_gapslist_stacksanalyze_dependenciesevaluate_build_vs_buyget_recommendationsvalidate_packageBEFORE YOU INSTALL
What to know first
Tools you get
19 tools named in the project's documentation.
Where it runs
All 4 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
Claude Code
TERMINAL
claude mcp add indiestack -- uvx --from indiestack indiestack-mcpMCP Clients
Claude Desktop, Cursor, Windsurf
JSON
{
"mcpServers": {
"indiestack": {
"command": "uvx",
"args": [
"--from",
"indiestack",
"indiestack-mcp"
]
}
}
}
