Bridge DC Hub's official MCP server in the dchub adapter - #1629

Summary

DC Hub asked us to point the DC Hub connector at their official remote MCP server instead of our own REST description, and to drop the plan name from the key wording (plan names change and the line goes stale). The adapter now bridges https://dchub.cloud/mcp, like the Linear, GitHub and Notion adapters: users get DC Hub's full tool set (94 tools in a live keyless tools/list on 2026-11-11, instead of our 20) and new DC Hub tools through Discover tools.

Changes

• intl/dchub.json: connector.type: "MCP", baseUrl: https://dchub.cloud/mcp, config.mcpToolPrefix: "dchub_". The key stays optional: authType: API_KEY with X-API-Key: {{DCHUB_API_KEY}} (the header DC Hub documents on dchub.cloud/connect); keyless installs and calls work (an empty X-API-Key header is accepted, checked live). requiredEnvVars stays empty.
• Tool snapshot generated from the live tools/list: local names dchub_<remote>, standard annotations only, no em/en dashes. Twelve tools that act for the user outside AnythingMCP install switched off (an email address sent to DC Hub, newsletter/alert subscriptions, webhooks, accepting DC Hub's terms, operator introductions, partner data reports). The per-call payment parameters mpp_pay / mpp_credential are dropped with omitParameters, so the model is never offered to pay per call.
• Description based on DC Hub's suggested text; instructions link the official endpoint and use the neutral sentence "A few tools return previews without a DC Hub key; a key unlocks full answers. Get one at https://dchub.cloud/connect." No plan names in our wording.
• prerequisites added (required for MCP bridge adapters by mcp-adapter.spec.ts); the REST probe is gone (an MCP adapter is checked by listing the server's tools).
• intl/dchub.live.spec.ts rewritten for the bridge: static checks (endpoint, optional key, prefix and names, switched-off set, payment parameters, neutral wording, no dashes) and a live check gated by RUN_DCHUB_LIVE=1 that every tool the snapshot switches off or trims still exists on the server.

Cloud and self-hosted behave the same: both call dchub.cloud directly. Installed connectors keep their REST tools until an admin clicks Apply update on the connector (one workspace has a DC Hub connector, no calls in the last 30 days). docs/catalog/connectors/dchub.md is generated by the website's export-github-catalog.mjs from the live catalogue, so it refreshes after this ships.

Type

• Bug fix
• New feature
• Documentation
• Refactoring
• Performance improvement
• Other (describe below)

Testing

• Added/updated unit tests
• Tested manually (describe steps below)
• No tests needed (explain why)

All in packages/backend unless noted, after npm ci and prisma generate:

• npx jest src/adapters src/connectors/mcp-connector-config src/common/unresolved --maxWorkers=4: first run 1 failure (mcp-adapter.spec.ts: MCP adapters need prerequisites), fixed; then npx jest src/adapters/mcp-adapter.spec.ts src/adapters/intl/dchub.live.spec.ts: 42 passed, 1 skipped (live).
• RUN_DCHUB_LIVE=1 npx jest src/adapters/intl/dchub.live.spec.ts: 8 passed.
• npx eslint src/adapters/intl/dchub.live.spec.ts: clean. npx tsc --noEmit -p tsconfig.json: clean.
• Repo root: node scripts/validate-adapters.mjs --warn: exit 0, no dchub warnings, same warnings as main. node scripts/regenerate-catalog.mjs, node scripts/generate-llms-txt.mjs, node scripts/generate-cli-operations.mjs: no diff. node scripts/adapter-count.mjs --check: OK (731 adapters, 42 keyless).
• Manual: keyless initialize + tools/list + tools/call get_market_intel against https://dchub.cloud/mcp with an empty X-API-Key header: 200, preview result.

Checklist

• My code follows the existing code style
• I have tested my changes locally
• I have updated documentation (if applicable)
• All existing tests pass (npm test) (adapter, MCP and placeholder suites run; full suite left to CI)
• This PR has a descriptive title

Related Issues

Relates to the DC Hub listing request (vendor email).