Host the HTTP-01 challenge

When you run mrpd publish, you’ll get:

• a path: /.well-known/mrp-registry-challenge/<token>
• an expected string

Your server must return the exact expected string at:

https://YOUR_DOMAIN/.well-known/mrp-registry-challenge/<token>

Common ways

Static hosting (recommended)

Create a file at:

.well-known/mrp-registry-challenge/<token>

with the body exactly equal to the expected string.

Next.js

Add a route that returns plain text with no extra whitespace.

nginx

Map that path to a static file.

Gotchas

• Must be reachable over HTTPS.
• Avoid redirects.
• The response body must match exactly (trimmed). If you accidentally add newlines, it can fail.