AiFinPay

● degraded model-context-protocol-mcp

skills: {'id': 'pay-per-call', 'name': 'Per-call payment settlement', 'description': 'Atomic on-chain settlement of HTTP 402 challenges via Polygon (payMatic + USDC roadmap) or Solana (Seat PDA + Ed25519).', 'tags': [], 'examples': None, 'input_modes': None, 'output_modes': None}, {'id': 'provider-discovery', 'name': 'Provider discovery and routing', 'description': 'Live catalog of x402-compatible service providers (search, compute, inference) reachable through bridge endpoints.', 'tags': [], 'examples': None, 'input_modes': None, 'output_modes': None}, {'id': 'atomic-split', 'name': 'Atomic 99/1 fee-on-top split', 'description': 'Single-tx merchant 98.99% / treasury 1% / IP creator 0.01% split via AiFinPaySplitter contract.', 'tags': [], 'examples': None, 'input_modes': None, 'output_modes': None}; conformance: fail

Quality grade

How grading works

D 31.3 / 100

Availability 18.0 / 40

Reachable but returned HTTP 404

Payability 13.3 / 20

✓ Answers a real HTTP 402 challenge
✓ Publishes a /.well-known/x402 descriptor
✗ Payment address on record
✗ Settlement network declared
✗ Price declared

Demand 0.0 / 40

No payment address on record, so demand cannot be measured

Owner verified 0.0 / 3

Nobody has claimed this listing yet

Endpoint last checked 12 h ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass.

How to call

cURL · x402-fetch / x402-axios will auto-handle 402

curl -sS -i -X GET https://aifinpay.io  # expect HTTP 402 Payment Required (price advertised in the 402 response)

MCP endpoint

https://aifinpay.io

/.well-known/x402.json

https://aifinpay.io/.well-known/x402

Listed in

Directories this entry was found in.

mcp