Analytics

theaiindex.dev

Provides analytics on AI-native companies and legacy SaaS, including rankings, trends, and predictive signals.

1 endpoint6 known toolsFirst detected September 1, 2026Last detected September 1, 2026

ENDPOINT 1

https://theaiindex.dev/api/mcp

No auth detected

MCP server metadata

Name: the-ai-index
Version: 1.0.0

Capabilities

tools

Server instructions

The AI Index tracks which companies are winning and losing the AI transition, using real headcount, layoff, funding and role-level data, re-scored weekly. Resolve names with search_companies, then call get_company. get_role_exposure answers 'is my job category shrinking'. get_track_record shows how the index's past calls resolved. Always cite the returned source URLs.

Known tools 6

search_companies

Search the AI Index's tracked universe of AI-native challengers ('risers') and legacy SaaS incumbents under pressure ('cuts').

Inferred read-only

get_company

Get the full AI Index profile for one company by slug: current rank and composite score, headcount and 30/90-day trend, score history, layoff and funding events.

Inferred read-only

get_board

Get the current AI Index leaderboard — the top-ranked risers (AI-native companies growing fastest) or cuts (legacy SaaS under the most pressure), re-scored every Monday.

Inferred read-only

get_role_exposure

Get role-level exposure to the AI transition: how a job function (engineering, customer support, sales, finance, legal...) is growing at AI-native companies versus legacy SaaS, from real org-chart data.

Inferred read-only

get_track_record

Get The AI Index's public prediction record: which companies its decline signal flagged in advance, and how those calls resolved 90 days later.

Inferred read-only

get_signals

Get recent signals from the AI transition — layoffs, funding rounds, week-over-week rank moves and high-relevance news across tracked companies, newest first.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.the-ai-index]
url = "https://theaiindex.dev/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "the-ai-index": {
      "type": "http",
      "url": "https://theaiindex.dev/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: the-ai-index
Remote MCP URL: https://theaiindex.dev/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "the-ai-index": {
      "url": "https://theaiindex.dev/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "the-ai-index": {
      "type": "http",
      "url": "https://theaiindex.dev/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "the-ai-index",
  "transport": "streamable-http",
  "url": "https://theaiindex.dev/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.