Govern and discover records with common metadata in AWS Agent Registry

What happened
Custom metadata schemas are now available in AWS Agent Registry. Custom metadata schemas in AWS Agent Registry let an administrator define typed, validated fields that every agent, MCP server, and skill must carry. Amazon Web Services is a cloud computing company based in Seattle.
As organizations build more agents, Model Context Protocol (MCP) servers and skills, they need a consistent way to describe, govern, and find them. AWS Agent Registry provides a catalog for registering, approving, and discovering these resources and custom records.
Each record carries a name, a description, a protocol descriptor, and an approval status. However, every organization has attributes and facts that it wants to track, and some are unique to that organization, such as its business units, resource owners, risk classifications, and development environments.
Organizations want one common definition for each of these attributes, and they want every agent, MCP server, and skill in the registry to carry these facts. Artificial Intelligence As organizations build more agents, Model Context Protocol (MCP) servers and skills, they need a consistent way to describe, govern, and find them.
Until now, organizations had no way to define these facts in AWS Agent Registry and store them on each record. A custom metadata schema is a set of organization-defined key-value pairs that records in an AWS Agent Registry carry.
An administrator defines the schema and applies it to the registry, and all records within the registry must then adhere to the schema. When publishers create or submit records, they supply values for the fields specified in the applicable schema, and AWS Agent Registry validates those values against the schema set by the admin.