Agent Standards Watch — 2026-07-25

The AgentAtlas Standards Watch is a weekly, source-linked briefing for people shipping AI products. This edition covers verified records from the maintainers of MCP, A2A, Agent Skills, UCP, and AP2. It does not treat social engagement, commentary, or a repository timestamp as proof of adoption. The goal is to separate current stable guidance from previews and maintenance activity so teams can decide what deserves implementation work.

Across these sources, the recurring pattern is a broader operating surface for agents: tool interoperability, agent-to-agent communication, portable skills, commerce, and payments. Those layers can reinforce one another, but they do not automatically share maturity, release cadence, or compatibility. Production teams should pin exact versions, record the source used for each decision, and evaluate upgrades in a reversible environment.

1. [Model Context Protocol](https://github.com/modelcontextprotocol/modelcontextprotocol/releases/tag/2025-11-25)

Verified from Model Context Protocol on May 29, 2026. The official release record identifies **2025-11-25** as stable and **2026-07-28-RC** as a preview, not the stable specification. For teams evaluating MCP interoperability, the practical signal is that the stable specification and the release candidate are separate compatibility targets.

For Model Context Protocol, teams should implement and advertise the stable protocol version they have actually tested. Release candidates are useful for compatibility trials, but production claims should stay tied to stable behavior until the maintainers publish a final release.

**A practical evaluation:** Record the negotiated protocol version, exercise initialization and one read-only tool call against the stable specification, then run any release-candidate work in a separate compatibility suite. Review the [official specification](https://modelcontextprotocol.io/specification/) before changing a production implementation.

2. [Agent2Agent Protocol](https://github.com/a2aproject/A2A/releases/tag/v1.0.1)

Verified from Agent2Agent Protocol on May 28, 2026. The official release record identifies **v1.0.1** as stable. For teams evaluating agent-to-agent interoperability, the practical signal is that A2A has a current stable 1.0-series release that teams can pin instead of coding against an unspecified moving target.

For Agent2Agent Protocol, agent-to-agent integrations need an explicit contract for discovery, task state, messages, artifacts, authentication, and failure handling. Pinning the stable release makes conformance tests and upgrade decisions reproducible.

**A practical evaluation:** Validate one end-to-end task against the stable specification, including cancellation and an error path, and retain the exchanged task states as evidence. Review the [official specification](https://a2a-protocol.org/latest/specification/) before changing a production implementation.

3. [Agent Skills](https://github.com/agentskills/agentskills/commit/38a2ff82958afee88dadf4831509e6f7e9d8ef4e)

Verified from Agent Skills on Jul 10, 2026. The official repository was last updated at revision **38a2ff82958a**. A repository update is evidence of active maintenance, not by itself proof that every implementation requirement changed. For teams evaluating portable agent capabilities, the practical signal is that portable skill packages are being actively maintained, while repository activity alone does not establish a new compatibility promise.

For Agent Skills, a useful skill should make its trigger, instructions, dependencies, and expected result inspectable. Teams should version the package, review executable assets, and test the same skill across supported agent environments before calling it portable.

**A practical evaluation:** Install one narrowly scoped skill in an isolated project, inspect every bundled instruction and script, and verify its output and permission boundary in each supported host. Review the [official specification](https://agentskills.io/specification) before changing a production implementation.

4. [Universal Commerce Protocol](https://github.com/Universal-Commerce-Protocol/ucp/commit/20bb02d1e089e2ddcf9f33509a38b7106c237c67)

Verified from Universal Commerce Protocol on Jul 24, 2026. The official repository was last updated at revision **20bb02d1e089**. A repository update is evidence of active maintenance, not by itself proof that every implementation requirement changed. For teams evaluating agentic commerce, the practical signal is that commerce workflows now have a dedicated protocol surface, but an active repository is not evidence that a particular merchant or platform supports it.

For Universal Commerce Protocol, commerce integrations must preserve authoritative product, price, availability, consent, order, and fulfillment state across system boundaries. Compatibility should be proven with the merchant's current implementation and documented extensions.

**A practical evaluation:** Run a sandbox purchase from discovery through order status, verify totals and consent at every boundary, then exercise inventory change, cancellation, and refund paths. Review the [official specification](https://ucp.dev/) before changing a production implementation.

5. [Agent Payments Protocol](https://github.com/google-agentic-commerce/AP2/commit/e1ea56db72a6385bce3e5c1112b3a56ce60acb43)

Verified from Agent Payments Protocol on Apr 29, 2026. The official repository was last updated at revision **e1ea56db72a6**. A repository update is evidence of active maintenance, not by itself proof that every implementation requirement changed. For teams evaluating agentic payments, the practical signal is that agent-initiated payment work requires explicit authorization evidence and auditable state transitions, regardless of protocol availability.

For Agent Payments Protocol, payment automation should separate shopping intent, purchase authorization, credentials, execution, and dispute evidence. A protocol can structure that exchange, but it does not replace payment-provider controls or local compliance review.

**A practical evaluation:** Use a sandbox to test an approved amount, a changed amount, an expired authorization, and a refund while confirming that every actor and state transition is auditable. Review the [official specification](https://ap2-protocol.org/) before changing a production implementation.

What to do with this week's signals

• Pin stable protocol versions in architecture decisions and dependency records.
• Keep prerelease experiments isolated from production compatibility promises.
• Test one real but reversible workflow instead of relying on a synthetic demo.
• Define the expected output, review owner, permission boundary, and rollback path before granting write access.
• Recheck the linked specification when the official monitor reports a material release or repository update.

Closing view

The strongest agent products will be differentiated by dependable execution and clear evidence, not by the number of protocols named on a landing page. Use these official records as starting points, then validate each decision against your own users, data, threat model, and operating constraints. The next Standards Watch will publish only after the monitored primary sources change and the content passes the same citation and quality gates.

Sources

• [modelcontextprotocol/modelcontextprotocol](https://github.com/modelcontextprotocol/modelcontextprotocol/releases/tag/2025-11-25) — 5/29/2026, 12:51:22 UTC
• [a2aproject/A2A](https://github.com/a2aproject/A2A/releases/tag/v1.0.1) — 5/28/2026, 11:34:36 UTC
• [agentskills/agentskills](https://github.com/agentskills/agentskills/commit/38a2ff82958afee88dadf4831509e6f7e9d8ef4e) — 7/10/2026, 00:11:48 UTC
• [Universal-Commerce-Protocol/ucp](https://github.com/Universal-Commerce-Protocol/ucp/commit/20bb02d1e089e2ddcf9f33509a38b7106c237c67) — 7/24/2026, 11:59:20 UTC
• [google-agentic-commerce/AP2](https://github.com/google-agentic-commerce/AP2/commit/e1ea56db72a6385bce3e5c1112b3a56ce60acb43) — 4/29/2026, 16:51:41 UTC