When it fits
- A product exposes MCP tools.
Proposed guarantees
These describe the intended contract. Consult implementation and verification evidence before relying on them.
- Delegate protocol behavior to an established SDK
What stays outside
- New MCP stack
- Product authorization policy
Failure modes
- Tool accesses another tenant resource
Existing alternatives
Official MCP Go SDK
Reuse the SDK; product registers tools and enforces resource authorization.
Implementations
No AMSL implementation is recorded in this snapshot. External alternatives above are not claims of AMSL adoption.
Evidence and verification
Candidate selection includes restricted, maintainer-reported evidence. It is not independently reproducible here, and no private source details are published.
No executed verification or real consumer adoption is recorded in this snapshot.
Open questions
- Reconsider only a separately demonstrated integration gap.