From the source
Amazon's guide shows how to keep AWS Agent Registry records current by wiring CloudTrail, EventBridge and Lambda into a push-based sync for MCP servers.
- The problem it addresses is staleness: when an MCP server gains a tool or changes its schema, the registry record must be updated or consumers discover outdated metadata.
- The post says stale metadata reduces registry reliability and pushes teams toward hardcoded endpoints, informal knowledge sharing and stale documentation.
- The pipeline captures UpdateAgentRuntime API calls in CloudTrail, routes them through EventBridge to a Lambda in the registry account, which authenticates through AgentCore Identity, calls the MCP server's initialize and tools/list, diffs the result and updates the matching record.
- CloudTrail records the event as a management event with a delivery delay of approximately 5–15 minutes.
- The sample uses two accounts, with the registry account owning the registry, EventBridge rule, Lambda and CloudTrail logs, and the MCP server account hosting the runtime and Cognito OAuth provider; a single-account setup skips cross-account forwarding.
- The Lambda updates existing records only and does not create new ones, so the MCP server must already be pre-registered.






