Add a live mainnet x402 MCP conformance fixture

Open
#60 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github, python
Domain
devtools, testing

Research direction

Start by locating the buyer skill's x402 MCP transport and its existing tests or examples. Then check how it handles tools/list, an unpaid tools/call, payment metadata, a paid retry, and the settlement response against the public HumanMirror endpoint. Done means a documented optional workflow exercises that sequence; the issue does not name repository files or tests.

Written by the indexing model from the issue text.

Description

The buyer skill now supports the x402 MCP transport, but I could not find a public mainnet conformance fixture in this repo that exercises the full MCP flow end-to-end against an independent seller.

Would it be useful to add one documented external fixture for:

  1. tools/list discovery
  2. unpaid tools/call → PaymentRequired in structuredContent
  3. payment in _meta["x402/payment"]
  4. paid retry
  5. settlement in _meta["x402/payment-response"]

HumanMirror can serve as that fixture without requiring an account or API key.

Public MCP server:
POST https://humanmirror.fr/api/x402/mcp/

Two paid tools:

  • humanmirror_machine_resolve — 0.001 USDC on Base
  • humanmirror_safe_preflight — 0.010 USDC on Base

The MCP-originated PaymentRequired now uses the x402 MCP resource identity form:
mcp://tool/

and includes Bazaar MCP discovery metadata (type=mcp, toolName, inputSchema, example, streamable-http).

Canonical discovery:
https://humanmirror.fr/.well-known/x402
https://humanmirror.fr/kit.json

Independent public evidence already exists that HumanMirror is x402-compliant and listed in CDP Bazaar:
https://forgemesh.io/partners/humanmirror

I am not proposing a special-case integration or any change to MetaMask payment policy. The useful outcome would be a small optional example/conformance workflow that lets contributors test the MetaMask buyer against a live third-party seller.

If you prefer a different public seller for the fixture, the same test shape would still be valuable; I can help adapt the HumanMirror side if your MCP buyer exposes a stricter requirement than the current x402 v2 spec.

Dominant language
Python
Stars
30
Forks
16
Avg merge
11h 59m
Merged PRs (30d)
5

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MetaMask/agent-skills

All issues in MetaMask/agent-skills

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.