fix: add mcp-name ownership proof to README for MCP Registry

[shenxianpeng]

Problem

After fixing the race condition (race between PyPI publish and MCP Registry publish), the workflow now fails with a different error:

PyPI package 'commit-check-mcp' ownership validation failed.
The server name 'io.github.commit-check/commit-check-mcp'
must appear as 'mcp-name: io.github.commit-check/commit-check-mcp'
in the package README

The MCP Registry requires the server name to appear as mcp-name: ... in the PyPI package README as proof of ownership. The registry reads the README from PyPI and checks that it contains this line before accepting the server.json publication.

Fix

Added mcp-name: io.github.commit-check/commit-check-mcp to README.md (with an HTML comment pointing to the MCP Registry docs for context). This line will be included in the package uploaded to PyPI, satisfying the ownership validation.

Relevant run

https://github.com/commit-check/commit-check-mcp/actions/runs/28819007662/job/85465869552

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 1 minute

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: adf59e24-4f20-480c-b526-4764bf3a9a72

📥 Commits

Reviewing files that changed from the base of the PR and between 8840323 and 9557382.

📒 Files selected for processing (1)

• README.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bugfix/add-mcp-name-ownership-proof

---

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.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (8840323) to head (9557382).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #22   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines          209       209           
=========================================
  Hits           209       209           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.