# AGT-006: Discover the MCP servers and connectors employees attach to their AI clients


- Area: Agent & MCP Governance

- Verification: Live test
- OWASP adoption tier: AT3, AT4, AT6
- Formerly: DIS-007
- URL: /r/AGT-006

**Acceptance criteria:** Inventory local and remote MCP servers reached from desktop, IDE and CLI AI tools with owner, scope and exposure.

**Why it matters:** MCP-capable clients now ship inside IDEs, terminals and desktop apps, and each connector is a new path to corporate data.

**How to verify:** Local and remote MCP servers used by pilot users appear with client, owner, scope and exposure.

**OWASP adoption context:** Citizen-built, code-executing and MCP-extended workflows can attach external servers, so connector discovery must reach those integration paths.

**Mappings:**
- NIST CSF 2.0: GV.SC-04, ID.AM-04; NIST AI RMF: MAP 4.1 — The MCP and connector inventory identifies third-party components and services, with owner, scope and exposure to inform supplier prioritization and component-risk mapping. Discovery alone does not assess their risks.
- ISO 42001: A.4.2, A.10.3 — ISO/IEC 42001: The local and remote MCP/connector inventory documents resources relevant to AI activities, including their owner, scope and exposure, supporting A.4.2. External MCP servers and connectors also identify supplier relationships to govern under A.10.3; locally owned servers are not automatically suppliers. Inventory does not establish supplier due diligence or trustworthiness.
- OWASP ASI: ASI04 — The inventory exposes external MCP servers and runtime-connected components relevant to agentic supply-chain compromise. It provides a review surface, not evidence that components are trustworthy.
- SOC 2: CC2.1, CC9.2; ISO 27001: A.5.9, A.5.19 — Owned connector records supply usable inventory/control information and inputs to supplier-risk review. Keeping the register current does not itself approve a connector or reduce its permissions.
ISO/IEC 27001: Maintain usable, owned inventory records. Internally owned servers are not automatically suppliers, and discovery does not assess supplier security.