Skip to content

Docs: optional TOA verify after conformance - #479

Closed
dulrajnr wants to merge 4 commits into
modelcontextprotocol:mainfrom
dulrajnr:toa-optional-verify
Closed

Docs: optional TOA verify after conformance#479
dulrajnr wants to merge 4 commits into
modelcontextprotocol:mainfrom
dulrajnr:toa-optional-verify

Conversation

@dulrajnr

Copy link
Copy Markdown

Summary

Docs-only. Optional step to run toa-verify when a toa.json attestation is present, after MCP protocol conformance.

  • README section under GitHub Action
  • SDK_INTEGRATION.md section for SDK maintainers
  • examples/toa-after-conformance.yml

Does not add a conformance scenario. TOA is adjacent delivery evidence (toa/0.1), not wire-protocol checks. No AgentStatus account is required to verify.

Test plan

  • README / SDK_INTEGRATION examples are valid YAML
  • Copy is clear that TOA is optional and not a protocol scenario
  • Example workflow path is copy-paste only

Made with Cursor

AgentStatus and others added 4 commits August 30, 2026 19:09
Adjacent delivery-evidence check only. Not a protocol scenario.
Match toa-verify --require-emitter / --max-age 7d after Carmel-Labs-Inc/toa#1.
Carmel-Labs-Inc/toa@99e2690 ships keys/agentstatus-v1.json inside the python package (toa#2).
Match the sample command, which requires emitter.name=agentstatus and the packaged key.

Co-authored-by: Cursor <cursoragent@cursor.com>
@pcarleton

Copy link
Copy Markdown
Member

Closing as part of a maintainer backlog sweep: if you would like to propose an extension & have conformance tests for it, we could consider that.

@pcarleton pcarleton closed this Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants