Mcp Endpoint Ids
Objective
Capture and validate the mcp endpoint ids element within the Generative, Agentic & Control Plane layer.
UAIF requirement
The incident record should implement the canonical mcp_endpoint_ids field using the defined UAIF data type, validation constraints, and conditional rules.
Business impact
Captures generative, agentic and control-plane context needed to investigate escalation and system-to-system propagation.
Validation approach
Validate mcp_endpoint_ids for declared JSON type and applicable conditional rules. Then review semantic consistency against the source incident evidence and the selected conformance profile.
Expected evidence
Retain the source record or analyst input for mcp_endpoint_ids, schema-validation output, transformation history, selected profile, schema version and reviewer rationale where judgement is involved.
Mapping and source
UAIF Schema Specification; UAIF Technical Specification; JSON pointer /properties/mcp_endpoint_ids.
Implementation guidance
Populate mcp_endpoint_ids from an identified source or documented analyst decision. Enforce the schema constraints at record creation and update, preserve the original value and provenance, and surface validation failures without silently coercing data.
Assessment considerations
Sample records across normal, boundary and invalid conditions. Confirm that mcp_endpoint_ids is populated only when applicable, conditional rules are enforced, provenance is retained and downstream systems do not change its meaning or precision.
Canonical schema definition
| JSON property | mcp_endpoint_ids |
|---|---|
| Required in core profile | No |
| Type | "array" |
Source: UAIF Schema Specification and UAIF Core JSON Schema.