docs: add paid MCP integration fixture#9
Draft
Bortlesboat wants to merge 1 commit into
Draft
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.
Summary
x402_mcp_calldevelopment_meta["x402/payment-response"]receipt-preservation behaviorWhy
AgentPay issue #7 needs a real x402 Foundation paid-MCP target for approval-gated signing work.
https://mcp.bitcoinsapi.comgives maintainers a live fixture with a free tool, auth-only tool, and paid tools without requiring them to invent a mock protocol transcript first.Validation
curl/PowerShell probe:https://mcp.bitcoinsapi.com/statusreturnedok: truewith the expected SSE transport and four toolsnpm run typechecknpm test(164/164 passing)npm run lint(exit 0; existing warnings only)Related: #7