Payment Layer FAQs

Question 1

Is there a reference implementation available for mcp-pay?

Accepted Answer

Yes, a reference Rust server (`mcp-pay-server`) is provided. It demonstrates how to implement payment-gated MCP tools using the defined JSON schema and the HTTP 402 payment flow, making integration straightforward.

Question 2

How does Payment Layer declare pricing and acceptable payment rails?

Accepted Answer

It uses a standardized JSON manifest (`mcp-pay.json`) served at a well-known URL (`/.well-known/mcp/pay.json`). This manifest declares pricing rules (e.g., per-call) and the payment rails a service accepts.

Question 3

What payment protocols does mcp-pay support?

Accepted Answer

It is designed to be rail-agnostic, currently implementing HTTP 402 payment flows compatible with x402. There are plans to extend support to MPP, Lightning, and traditional card payments (e.g., Stripe).

Question 4

What problem does mcp-pay solve for MCP developers?

Accepted Answer

mcp-pay bridges the existing gap in MCP ecosystems by providing a unified, rail-agnostic system for discovering and processing payments. This allows developers to easily monetize their MCP-enabled tools across diverse payment protocols.

Question 5

What is Payment Layer (mcp-pay)?

Accepted Answer

Payment Layer (mcp-pay) extends the Model Context Protocol (MCP) ecosystem by adding standardized, rail-agnostic payment capabilities. It enables monetization for MCP tools and services through a unified payment mechanism.

Payment Layer

Payment Layer

주요 기능

사용 사례

주요 기능

사용 사례