DC Hub adapter merged — is there a public listing URL to link to?

[azmartone67]

The DC Hub adapter merged last week — thanks for building it. #653, adapter slug dchub, tracked on #652.

Is there a canonical public URL for the listing yet?

We'd like to link to it from https://dchub.cloud/connect, where we point people at the catalogues DC Hub is reachable through. Our CI refuses to ship a placeholder link on that page, so the card is written and parked until there's a real URL to put in it.

Checked today and couldn't find one, so we're likely looking in the wrong place:

URL
https://anythingmcp.com/marketplace	200, but no DC Hub entry
https://anythingmcp.com/connectors/dchub	404
https://anythingmcp.com/adapters/dchub	404
https://anythingmcp.com/integrations/dchub	404
https://anythingmcp.com/guides/connect-dchub-to-claude	404
https://anythingmcp.com/guides/connect-dc-hub-to-claude	404

If it lives under a slug we haven't guessed, just point us at it and we'll link that exact URL. If listings are generated on a schedule rather than at merge, knowing the cadence is enough — we'll wait and check back instead of probing.

Second, smaller question: dchub.live.spec.ts in #653 looks like a live conformance check. If it runs against production on your CI, roughly what does it call and how often? Nothing is wrong on our side — we'd just rather recognise it in our own traffic than treat it as unexplained, and if it needs a key or a higher rate limit to be genuinely useful, we're happy to arrange that.

Asked the first question on #652 as well, but that issue is closed and the PR thread is locked, so posting here per the contact-links guidance. Happy to answer anything about the OpenAPI spec or the tiering if it helps the adapter.