Skip to content

Add Muse connector domain verification file - #384

Open
acoyfellow wants to merge 1 commit into
cloudflare:mainfrom
acoyfellow:feat/muse-domain-verification
Open

acoyfellow wants to merge 1 commit into
cloudflare:mainfrom
acoyfellow:feat/muse-domain-verification

Conversation

@acoyfellow

Copy link
Copy Markdown
Contributor

What

Serves one small text file so Meta's Muse connector platform can confirm we own mcp.cloudflare.com:

  • URL: https://mcp.cloudflare.com/.well-known/muse-challenge/0a43b9686a1b69cb039d2ba9aebb409c65fae31d720507fa338782bc66c66ac0
  • Body (plain text): muse-challenge=0a43b9686a1b69cb039d2ba9aebb409c65fae31d720507fa338782bc66c66ac0

Why

Cloudflare's Muse listing is stuck at Technical details. Muse now requires "Verify MCP server" before it will test the connector. Muse fetches that URL over HTTPS and needs HTTP 200 with only the line above, with no sign-in or redirect.

Time limit: the challenge expires Nov 8, 2026, 12:41 PM. After that Muse issues a new one, and this needs another PR.

How

It's the same pattern as the OpenAI check from #218: one exact path match in src/index.ts, before any OAuth or MCP routing, returning text/plain. All other paths behave as before.

Test

tests/auth/oauth-routes.test.ts checks the 200 status, content type and exact body. npx vitest run tests/auth/oauth-routes.test.ts gives 40/40 passing.

After deploy: curl -s https://mcp.cloudflare.com/.well-known/muse-challenge/0a43b9686a1b69cb039d2ba9aebb409c65fae31d720507fa338782bc66c66ac0, then click Verify file on Muse.

@acoyfellow
acoyfellow requested a review from a team as a code owner November 7, 2026 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant