AWS brings validated metadata schemas to Agent Registry
AWS Agent Registry now supports administrator-defined metadata schemas for validating and classifying agents, MCP servers, skills and custom resources. The feature became available October 13; AWS's November 17 post walks through implementation.
AWS made custom metadata schemas available in Agent Registry on October 13, giving administrators a way to require consistent, typed information across records for agents, MCP servers, skills and custom resources. The fields can support approval checks and make records easier to filter as registries grow.
A November 17 AWS technical post explains how to implement the feature. Published after the availability notice, the walkthrough is not the initial launch announcement. The post’s AnyCompany payments MCP server, security scanner, configuration database lookup and automated approval flow are illustrative. AWS says the scanner and database calls are stubs, and customers create the approval automation.
Administrators can define one custom metadata schema per registry. The schema can apply common attributes to every record and add fields for individual record types. Fields accept Text, Enum, URL or Boolean values, can be required or optional, and can restrict Enum entries to specified values. Agent Registry identifies the supported record categories as AGENT, MCP, SKILL and CUSTOM.
When metadata is included in a record creation or update, Agent Registry validates field names, required entries, types and allowed values. Unknown fields and invalid values are rejected. A record can still be created or updated without metadata, but it cannot be submitted for approval until every required field has a value. Updating a record’s custom metadata replaces the full metadata map instead of merging only the new fields.
The service calculates compliance against the latest schema. A COMPLIANT result means the metadata matches that schema; it does not mean the record is approved. If a schema change makes an existing record noncompliant, the record keeps its approval status but must conform before its next approval submission.
Schema changes are largely additive. Administrators can add fields or Enum values and make an optional field required, but generally cannot rename, remove or change a field’s type, remove allowed values, or make a required field optional. AWS says changing a schema does not rewrite existing records.
Agent Registry’s discovery search returns approved records only, excluding Draft, Pending approval, Rejected and Deprecated records. Custom metadata fields can be filtered with equality, inequality and membership operators. AWS also exposes discovery through a registry MCP endpoint.
More news

Cohere Adds Crunchbase Connector to North

Chevron Technical Center signs three-year UptimeAI deal after pilot

Cohere adds third-party open models to Model Vault
