Armory
Source

Pipeline

The layers the Armory is built from, in the order an agent meets them

Every figure below is computed from catalog.json when this page builds.

  1. Layer 1

    Sources

    Agents crawl 4 MCP registries and hand-curated GitHub collections, then dedupe and merge them into one catalog.

    56,508

    Distinct source repositories, deduped

    Registries Crawled

    Glama41,156
    PulseMCP15,701
    mcp.so2,853
    Smithery587

    Curated Collections

    davila7/claude-code-templates1,644
    affaan-m/ecc529
    wshobson/agents260
    PatrickJS/awesome-cursorrules256
    VoltAgent/awesome-claude-code-subagents153

  2. Layer 2

    Components

    Each entry is filed under one of 11 harness components, named as on the Components page.

    65,239

    In the catalog, across 11 harness components

    MCPs61,707
    Skills1,132
    Sub-Agents724
    Identity499
    Hooks134
    Dispatch59
    Tools57
    Evals37
    Memory36
    Observability34
    Sandbox26

    Sandbox, Tools and Dispatch list only rows made for their job. The other 794 rows filed under them are still in search and Browse.

  3. Layer 3

    Ranking

    Components with at least one public signal get a Score: each signal becomes a 0–100 percentile within its own kind, then the strongest counts 0.8 and the second strongest 0.2. More signals, more confidence.

    29,112

    Ranked on at least one signal

    TestedMentionsStarsUsageForks

  4. Layer 4

    Verticals

    Components are also tagged with the industry they serve, so an agent can filter by vertical or ignore it.

    12

    Industry verticals

    FinanceLegalHealthcareE-commerceMarketingEducationGamingProductivityData & AnalyticsSecurityDev ToolsAI Infra

  5. Layer 5

    Query Surface

    The same catalog is readable three ways.

    3

    Ways to reach the one catalog

    REST

    /api/rank · /api/search

    CLI

    armory rank · armory search

    MCP

    armory-mcp · search, rank, get, submit