Distribute five missing MCP servers and repair mirror sync

[acedatacloud-dev]

Summary

• Add standalone-repository sync mappings for five active MCP services whose public repositories are empty: DigitalHuman, hCaptcha, Image2Text, reCAPTCHA, and Turnstile.
• Use the existing ADMIN_GITHUB_TOKEN fallback for mirror sync. Two recent full syncs failed to clone DiscordBotMCP with BOT_GITHUB_TOKEN (Repository not found).
• Add PyPI build and trusted-publishing workflows to those five packages and DiscordBotMCP, which currently lack a PyPI release. The workflows generate a CalVer version, build and verify distributions, then publish through the existing PYPI_TOKEN mechanism used by other MCP packages. Publishing starts only after the source PR lands and the standalone mirrors receive the workflow.

The MCPs monorepo remains the source of truth. This PR prepares the missing distributions; the external awesome-mcp-servers list will include them only after public repository and PyPI readback confirms release.

Verification

• python3 scripts/check_readme_inventory.py passed.
• python3 -m unittest -q passed (26 tests).
• All 33 catalog services now have a sync mapping.
• Built wheels locally with uv build for all six packages and verified their console entry points.
• Parsed all six new workflows and verified they use the established PyPI token path.
• git diff --check passed.

Rollout

After merge, run the full sync-to-repos workflow and inspect each mirror job. Confirm six public repository files and six PyPI releases before adding entries to the upstream list. If the PyPI token lacks access to a new package name, report that publish failure and keep its listing pending.