Adoption · Pour: lead

A team can install MCP and still have agents ignore it because config, permissions or instructions are wrong.

Detector checks configs, tool permissions, hooks, instructions and recent MCP calls across the agent stack.

$ aindex adoption --repair --json

agent
configured
last_mcp_call
repair_command
contract_verified

Commande

Agent Adoption Detector

Verify Codex, Claude Code, Cursor, Windsurf, VS Code, Zed, Copilot and Amp really call MCP.

CLI

aindex adoption --repair --json

MCP

status detail=adoption

Example output

Ce que le Cerveau fait automatiquement

Install success stops being a guess because every agent is checked against real MCP usage.

session

At the start of every agent session.

Not measuredPreuve

Non mesuréNo public benchmark covers this workflow yet — the proof is the live command output above, not a positioning claim.

Source—

AvailableRuntime feature status · 0 evidence item(s). Metadata-only; no raw source included.

Tier requis

Verifies that Codex, Claude Code, Cursor and friends actually call MCP, then emits an idempotent repair command.

Advanced · €9.99/mo

Visible as a product workflow and pilot proof target; do not treat as fully shipped enterprise automation yet.

Buyer grade

Names the parity workflow and proof path without claiming full Sourcegraph-class depth.

Visible in

This workflow stays discoverable across setup, CLI, MCP status, docs, dashboard and pricing — never a hidden command.

Feature visibility checklist

This keeps grouped product names discoverable without claiming a separate maturity level from the underlying workflow.

Adoption DetectorFoundation

Configured agents are checked against recent MCP usage.

Adoption

MCP usage rate