# CdpHub

> Find which CDPs connect to your tools, compare CDP catalogs, and check a whole stack

- name: com.cdphub/cdphub
- version: 1.0.3
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 91/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.cdphub%2Fcdphub
- tools: https://api.protogrid.dev/v1/servers/com.cdphub%2Fcdphub/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "cdphub": {
      "type": "http",
      "url": "https://cdphub.com/functions/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-9d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 91/100 (strong)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 6 of 6 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,271 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 1 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 6, about 1,271 tokens to load them all
- tool set hash: ab5db3b49bc5340308828b24ae78ff69
- tools last changed: 2026-11-03T06:38:46.371Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.cdphub/cdphub.svg)](https://protogrid.dev/servers/com.cdphub/cdphub)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-03 `check_stack` changed (description)
  - before: Check a stack of two to ten tools against every CDP in CdpHub's directory, as the stack check on cdphub.com does: how many CDPs list all of them and which, those CDPs grouped by how they connect to each tool with each group counted, the CDPs that miss exactly one tool grouped by the tool they miss, and a link to the same check on cdphub.com. Use it for any question about two or more tools together, such as which CDPs fit a company's stack.
  - after: Check a stack of two to ten tools against every CDP in CdpHub's directory, as the stack check on cdphub.com does: how many CDPs list all of them and which, those CDPs grouped by how they connect to each tool with each group counted, how they connect to each tool on its own with each group counted and a sentence for it, the CDPs that miss exactly one tool grouped by the tool they miss, and a link to the same check on cdphub.com. Use it for any question about two or more tools together, such as which CDPs fit a company's stack.

Full history: https://api.protogrid.dev/v1/servers/com.cdphub%2Fcdphub/changes

## Remotes

- https://cdphub.com/functions/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (6)

- `check_stack`: Check a stack of two to ten tools against every CDP in CdpHub's directory, as the stack check on cdphub.com does: how many CDPs list all of them and which, those CDPs grouped by how they connect to each tool with each group counted, how they connect to each tool on its own with each group counted and a sentence for it, the CDPs that miss exactly one tool grouped by the tool they miss, and a link to the same check on cdphub.com. Use it for any question about two or more tools together, such as which CDPs fit a company's stack.
- `compare_cdps`: Compare two CDPs' integration catalogs in CdpHub's directory, tool by tool: how many tools both list, how many only one does, the most widely listed tools in both, each side's largest categories of tools the other lacks, and the link to their comparison page on cdphub.com.
- `get_cdp`: Look up one customer data platform's integration catalog in CdpHub's directory: its number of tools and listings and its rank by catalog size, which way its integrations run, its largest categories with their most widely listed tools, how it connects to the main data warehouses, the CDPs that list the most of the same tools, and its page on cdphub.com.
- `get_tool`: Look up one marketing or data tool (for example Snowflake, Braze, Google Ads or The Trade Desk) in CdpHub's directory: how many of the customer data platforms (CDPs) it tracks list an integration with it, each CDP counted once (both sends data to it and reads from it, only sends, only reads), which CDPs list it in each group and which don't, every listing with its direction, how it runs (server-side, client-side, in the warehouse) and a link to the CDP's own documentation, and the tool's page on cdphub.com. Use it for any question about one tool.
- `list_cdps`: List every customer data platform in CdpHub's directory with its number of tools and listings and its page on cdphub.com, largest catalog first, with the directory's totals.
- `search_directory`: Search CdpHub's directory of CDP integrations by keyword, CDP, category, direction or how the integration runs. Returns the exact totals, the first results and the link to the same search on cdphub.com. Use get_tool for one named tool and check_stack for several.