fix: use a bot-safe MCP endpoint

[lifeodyssey]

What changed

• Introduces a single shared MCP machine endpoint constant for the production workers.dev origin.
• Publishes that endpoint in the MCP Registry manifest, MCP server card, llms.txt, and /agents quickstart.
• Verifies the workers.dev manifest and MCP methods from the protected Registry workflow.
• Keeps branded canonical pages and user-facing share links on sharehtml.zhenjia.dev.

Why

GitHub-hosted runners consistently received HTTP 403 from the branded zone before reaching the Worker, while the same Worker returned 200 through workers.dev. The zone is on Cloudflare Free, where Bot Fight Mode cannot be bypassed per path. Using a dedicated machine origin prevents legitimate data-center MCP clients from being rejected without weakening the branded site's security policy.

Validation

• 76 targeted tests passed
• npm run typecheck
• npm run build
• actionlint .github/workflows/publish-mcp.yml
• workers.dev server.json and MCP initialize return HTTP 200

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

Warning

Review limit reached

@lifeodyssey, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4351db5b-5b40-417c-ba31-91f666aa198d

📥 Commits

Reviewing files that changed from the base of the PR and between e43e04f and e523193.

📒 Files selected for processing (9)

• .github/workflows/publish-mcp.yml
• README.md
• server.json
• src/shared/marketing.ts
• src/shared/origins.ts
• src/worker/constants.ts
• src/worker/discovery.ts
• tests/client/components.test.tsx
• tests/discovery.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/mcp-machine-endpoint

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}