Skip to content
Major Labs logo

Major Labs MCP server

Which servers in the official MCP registry are Major Labs's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to Major Labs

Whose server it is
  • Registry nameco.majorlabs/major-labsverified in the MCP registry

The registry name sits under majorlabs.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13
  • Stateanswerschecked 2026-10-13
  • Tools5
  • Server calls itselfmajor-labs
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 325 ms.

Tools it offers5 tools · read 2026-10-13
  • get_trust_index

    The weekly Agent Trust Index: one composite score (0-100) for how safe the agentic web is to transact on, fused from code-safety, identity, and supply-chain pillars, with the per-pillar numbers and methodology version.

  • get_mcp_ecosystem_stats

    Aggregate statistics from the Major Labs weekly sweep of the MCP server ecosystem: census size, activity, transport and language breakdowns, and security/identity aggregates. Firsthand, read-only measurement.

  • list_incidents

    A dated, sourced record of frontier AI control incidents: containment escapes, unsanctioned live-system actions, evaluation incidents, and insider disclosures, with published inclusion criteria and sources for every claim.

  • get_agent_identity_tracker

    Every announced framework, protocol, standard, and regulation for AI agent identity, delegation, and know-your-agent (KYA) verification, dated and traced to primary sources.

  • get_threshold_watch

    Dated, hashed snapshots of the frontier labs' published safety frameworks, with diffs when a framework changes. A change event means a lab edited its safety commitments.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "major-labs": {
      "type": "http",
      "url": "https://majorlabs.co/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.