MCP Loot Drop
aissablk1/mcp-lootdrop
Acesse 1.700+ startups mortas, suas lições e planos de pivô com IA
Ver no GitHubServidor MCP não-oficial para acessar o banco de dados de startups falhas do loot-drop.io, contendo 1.700+ empresas mortas com análises de causa de morte, lições aprendidas e planos de reconstrução gerados por IA. Oferece ferramentas de busca, filtros avançados, análise de padrões de falha e estatísticas agregadas do ecossistema.
Instalação
npx convez-ai aissablk1/mcp-lootdrop1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Pesquisar padrões de falha em startups por setor, país ou causa
- Analisar lições aprendidas de empresas fracassadas para validar ideias
- Gerar planos de reconstrução e pivô baseados em IA para conceitos mortos
- Estudar clustering de falhas e identificar bottlenecks comuns
Veredito

Ferramenta única para pesquisa estruturada em startup failures. Bem mantida, com API estável e documentação clara. Ideal para founders, investidores e pesquisadores que querem aprender com fracassos anteriores.
README
A tradução para o português deste README ainda está na fila.
mcp-lootdrop
Unofficial, read-only Model Context Protocol server for loot-drop.io — The Startup Graveyard.
Gives AI agents structured access to 1 700+ dead startups: their causes of death, the lessons they left behind (the loot), failure clustering, and AI-generated rebuild / pivot plans (concept, MVP steps, tech stack, revenue model).
It consumes the same public API (Supabase REST + Row-Level Security) that the loot-drop.io website itself uses from the browser — no scraping, no writes.
Install
npm install -g mcp-lootdrop
# or run on demand:
npx -y mcp-lootdrop
Use with Claude Code / Desktop
Add to your MCP config (~/.claude/settings.json → mcpServers, or Claude Desktop config):
{
"mcpServers": {
"mcp-lootdrop": {
"command": "npx",
"args": ["-y", "mcp-lootdrop"]
}
}
}
Tools
| Tool | What it does |
|---|---|
lootdrop_diagnose | Check API connectivity + row counts |
search_startups | Full-text + filters (sector, country, cause, product type, funding, years), sortable, paginated |
get_startup | Full post-mortem of one startup (by id or name) |
list_rebuild_ideas | AI-generated rebuild/pivot plans, filterable |
failure_landscape | Failure clustering (normalized problems, bottleneck tags) |
graveyard_stats | Aggregates: counts or burned capital by sector/cause/product/country |
random_loot | One random dead startup (optionally filtered) |
top_startups | Ranked by burned capital or views |
list_facets | Distinct values for a facet, to guide filtering |
Configuration (optional)
All optional — sensible public defaults are built in.
| Env var | Default | Purpose |
|---|---|---|
LOOTDROP_SUPABASE_URL | loot-drop's public URL | Override the data source |
LOOTDROP_SUPABASE_KEY | loot-drop's public publishable key | Override the public key (e.g. if rotated) |
LOOTDROP_CACHE_TTL_MS | 300000 | In-memory cache TTL |
LOOTDROP_TIMEOUT_MS | 15000 | Per-request timeout |
Develop
npm install
npm run dev # run from TypeScript
npm run build # compile to dist/
npm test # real integration tests against the public API
npm run inspect # MCP Inspector
Disclaimer
mcp-lootdrop is an independent, unofficial project and is not affiliated with
loot-drop.io. It is read-only. The underlying content is AI-assisted and provided "as-is"
without warranty of accuracy or completeness. If the upstream API key is rotated or the
schema changes, override via the env vars above.
License
MIT © Aïssa BELKOUSSA