Avoid false MCP cautions for absent optional A2A cards - #199
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AG’s preflight returned
delegate_with_cautionfor BotHire’s working MCP endpoint solely because the unrelated A2A Agent Card returned 404. This also made retained endpoint evidence misleading for MCP-only services.Preserve a structured record of a successful MCP initialization. When that handshake is observed and the optional A2A card returns 404, report card resolution as unknown and exclude it from scored checks. A missing required A2A card, invalid MCP handshake, and served malformed or unsigned card keep their existing findings. No payment or task-execution safety is implied.
Validation: 158 distinct focused tests passed after rerunning the loopback TLS test with network permission and making Node available for the eight previously skipped verifier cases. Six regression cases cover JSON/SSE MCP responses, unknowns, malformed/unsigned cards, unproven protocol labels and missing A2A cards. The protected ship workflow performs the full CI matrix and deployment verification before completing the release.