Developer toolby ZillizCUR
Coverage gap: Repository Indexing
Coverage gap · HypothesisOverall 54.3 / 100 DERConfidence Low DERCalculated
Only 30 indexed products match "Repository Indexing" by keyword DER, inside a much larger parent category. This is a hypothesis, not a validated market: demand was inferred from the parent and discounted, and a missing record is not proof that anyone wants it. Score 54.3 of 100, confidence Low, as of 2026-11-21.
Not indexed by search engines: coverage-gap hypothesis: demand is a proxy, not measured.
Score breakdown
Contribution = weight × component score. The contributions add up to the overall score.
| Component | Weight | Score | Score (0–100) | Contribution | Kind |
|---|---|---|---|---|---|
| Demand | 0.25 | 59.0 | 0.25 × 59.0 = 14.75 | Heuristic | |
| Competition gap | 0.20 | 76.0 | 0.20 × 76.0 = 15.20 | Measured | |
| Monetisation | 0.20 | 40.0 | 0.20 × 40.0 = 8.00 | Heuristic | |
| Growth (relative) | 0.15 | 16.0 | 0.15 × 16.0 = 2.40 | Measured | |
| Feasibility | 0.10 | 60.0 | 0.10 × 60.0 = 6.00 | Heuristic | |
| Distribution | 0.10 | 79.0 | 0.10 × 79.0 = 7.90 | Measured | |
| Overall | 1.00 | 54.25 → 54.3 |
Solid bars are measured components; dashed outlines are rules of thumb. The full formula is on the radar page.
Confidence: Low
Rule: every coverage gap is Low.
What would raise it
- Confidence for coverage gaps is fixed at Low: demand is inferred from the parent category. It would rise only with a direct demand measurement for this capability (none is connected), or with researcher review of products the keyword rules missed.
The opportunity
All text in this section is generated by rule from the record. It is a starting point, not research.
- Description
- Indexing codebases for semantic search and retrieval. Few indexed products offer it, although the surrounding category (Context Engineering) is large.DER
- Problem
- Only 30 indexed products match "Repository Indexing", against 1466 in Context Engineering overall.DER
- Target users
- Teams already using agents for context engineeringHEU
- Product form
- MCP server, agent skill or pluginHEU
- Revenue model
- Not assessedHEU
- Complexity
- Not assessedHEU
- Competition level
- HighDER
- Subject
- Repository Indexing (capability)
Evidence for
3 row(s) from opportunity_evidence.
DemandHeuristicHEUvalue 2,189,570
The parent category Context Engineering holds 1466 products with 2,189,570 combined GitHub stars (98th percentile of subcategories). Interest in the parent is only a proxy — demand for this exact capability was not measured — so the percentile is discounted by 40% to 59.
/categories/developer-tools/ai-coding-agents/context-engineering/
Competition gapMeasuredDERvalue 30
30 indexed products match this capability by keyword.
DistributionMeasuredDERvalue 37
37 of 47 tracked agent platforms document MCP support.
Evidence against
4 row(s) from opportunity_evidence.
Competition gapHeuristicHEU
Classification is keyword-based: products that offer this without naming it are not counted, so the real gap may be smaller.
MonetisationHeuristicHEU
Rule of thumb by ecosystem (Developer Tools); no pricing data behind it.
Growth (relative)MeasuredDERvalue 480
480 launches in the parent category in the last 90 days versus 350 in the previous 90.
FeasibilityHeuristicHEU
Technical feasibility was not assessed for this capability; a neutral 60 is used.
Existing products
All Repository Indexing productsThe most notable profiled products matching this capability (up to 8). 30 indexed in total.
MCP serverby cocoindex-ioSRC
MCP serverby giancarloerraSRC
Infrastructureby kantordHEU
MCP serverby DavidyzHEU
Pluginby orySRC
MCP serverby bartolliHEU
MCP serverby bgts-ai-orgHEU
Where it could be distributed
All platforms37 of 47 tracked agent platforms document MCP support CUR, so one MCP server could reach all of them. No pairing has been tested.
ContinueOpenCodeClaude CodeCodexGemini CLIZedOpenHandsClineWarpgooseQwen CodeRoo Code+25 more
Channels: Official MCP Registry listing, plugin marketplaces for Claude/Cursor/Codex, and the integration vendor's own app directory where one exists. HEU
Data coverage
- Indexed products
- 30DER
- With a full profile
- 8+DER
- Launches, last 90 days
- 5 vs 6 in the 90 beforeSRC
- Segment calculated
- Score calculated
Risks and counterarguments
- This is a hypothesis: demand is inferred from the parent category, not measured.
- A low count can mean low demand rather than an unmet need — a missing record is not proof of a market.
- Keyword classification under-counts products that do not name this capability.
- Classification is keyword-based: products that offer this without naming it are not counted, so the real gap may be smaller.
- Rule of thumb by ecosystem (Developer Tools); no pricing data behind it.
- 480 launches in the parent category in the last 90 days versus 350 in the previous 90.
- Technical feasibility was not assessed for this capability; a neutral 60 is used.
Assumptions
What has to be true for the score to mean anything.
- Interest in the parent category (combined GitHub stars) stands in for demand for this capability; the proxy is discounted by 40%.
- Keyword classification finds the products that offer this capability; products that do not name it are not counted.
- Monetisation and feasibility are not assessed beyond a fixed rule of thumb.
- A platform that documents MCP support can run any MCP server; no pairing has been tested.
How to verify this yourself
- No direct demand query exists for this capability; the demand figure comes from the parent category's GitHub stars.
- Check the supply on the Repository Indexing page, and search the catalogue for products that offer it without naming it.
- Download the record with all evidence: /api/dataset/opportunities.json.
Page data last updated .