<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>mcp-pay writing</title><description>Notes on MCP payment awareness, the HTTP 402 flow, and rail-agnostic monetization for agentic tools. From the Neul Labs team.</description><link>https://mcp-pay.neullabs.com/</link><language>en-us</language><item><title>Wallet-side vs server-side metering for agentic spend</title><link>https://mcp-pay.neullabs.com/blog/wallet-side-vs-server-side-metering/</link><guid isPermaLink="true">https://mcp-pay.neullabs.com/blog/wallet-side-vs-server-side-metering/</guid><description>Who counts the calls? The wallet, the MCP server, or both? A look at the tradeoffs mcp-pay&apos;s v0.1 schema makes, and why the answer ends up being &apos;both, but for different things&apos;.</description><pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate></item><item><title>Designing payment flows that don&apos;t break the LLM call</title><link>https://mcp-pay.neullabs.com/blog/payment-flows-that-dont-break-llm-calls/</link><guid isPermaLink="true">https://mcp-pay.neullabs.com/blog/payment-flows-that-dont-break-llm-calls/</guid><description>Most payment flows assume a human at the other end. Agentic calls have a tighter latency budget and a smaller error tolerance. Here is what the v0.1 mcp-pay flow does to stay inside both.</description><pubDate>Sat, 18 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Why MCP servers need payment awareness, not paywalls</title><link>https://mcp-pay.neullabs.com/blog/payment-awareness-not-paywalls/</link><guid isPermaLink="true">https://mcp-pay.neullabs.com/blog/payment-awareness-not-paywalls/</guid><description>Paywalls are 1990s vocabulary for a problem agents need to solve differently. mcp-pay treats payment as metadata an agent can read at /.well-known/, not a wall it has to bounce off.</description><pubDate>Sat, 04 Apr 2026 00:00:00 GMT</pubDate></item></channel></rss>