Index integrity

Live counts straight from the database. We're honest about overlap, estimation, and which numbers are exact — no inflated marketing math.

Total indexed

—

Postgres estimated count

Domain pattern matches

—

Sum across 11 domains (skills can match more than one)

Domain coverage

—

0 of 0 skills caught by our domain probes.

Domain distribution

Percentage of indexed repos that match each domain's tightened pattern set.

How we count

Total — direct COUNT(*) on the skills table when fast enough, else a Postgres reltuples estimate.
Domain counts — case-insensitive substring match on description, full_name, repo_name, category against a tightened pattern set per domain.
Overlap — a single repo can match multiple domains (e.g. an MCP server written in TypeScript). The sum of domain counts will exceed the total; we expose that explicitly above.
Primary domain — the in-app card label is computed at query time by scoring against topics, name, and description, so each card shows its single best-fit domain.

Discover the toolingbehind modern intelligence

The operating system for AI infrastructure discovery. Search a live map of MCP servers, AI agents, LLM tools, automation systems, and developer infrastructure.

Back to explore