Decube
Decube MCP Server gives AI assistants direct, live access to governed context about your data, turning confident guesses into confidently right answers. Instead of asking a separate dashboard, teams query trusted context directly inside the tools they already use: Data Analysts can check whether a table is current, complete, or duplicated before reporting on it, and pull governed metric definitions on demand. Data Engineers can trace real upstream to downstream lineage before a schema change, find ownership gaps, write context back into Decube, and run automated checks in the CI pipeline via a pre-push git hook. Data Governance teams can run PII sweeps, check regulation compliance readiness (APRA, DORA, and similar regimes), and confirm every sensitive asset has an accountable owner, all without waiting on a manual audit cycle.
View in the Claude registry- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Primary Subcategory
- Data Catalog, Governance & Observability
- Secondary Subcategories
- None listed
- Brand
- Decube
- Access
- Account required
- First tracked
- 2026-07-16
- Tool count
- 33
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is visible.
Claude Discoverability Score
Live · refreshed daily. Last refreshedDecube in Data Catalog, Governance & Observability
#7of 9competitors
This is the score for the Integration’s Primary Category, Data Catalog, Governance & Observability. Decube's tools align with this Category, which is why we measure it here. Claude did not find it in connector search, show it in the connector picker, or invoke it in the measured contested Runs. That is why the score is 0.
How this score is measuredWhat we measure
One core score. Three important factors to discoverability.
- Sets the score
Picked
· 0/100 - Diagnostic
Found
· 0/100 - Diagnostic
Positioned
· 0/100
Competing in Claude Data Catalog, Governance & Observability
View CategoryWhat does 0/100 mean?
0 is Decube's rounded picker appearance rate. It appeared in the connector picker, or Claude invoked it directly, in 0% of contested conversations. All three measures are important to discoverability: Picked determines the headline score, Found shows how often Claude found Decube in connector search, and Positioned shows where it appeared in the picker.
Decube is 10 points from Buried.
FoundDiagnostic
Whether Claude found your Connector in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.
PickedMain score
How often your Connector appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.
PositionedDiagnostic
What position your Connector appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.
33 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Decube alternatives on Claude?
As of 2026-08-14, Decube competes with dbt, Monte Carlo, DataHub, Snowflake, Dremio Cloud, BigID, Hubbl, Rockhopper in Claude Data Catalog, Governance & Observability, ranked by public Discoverability Score.
Where does Decube rank in Data Catalog, Governance & Observability on Claude?
As of 2026-08-14, Decube ranks #7 of 9 in Claude Data Catalog, Governance & Observability with a Discoverability Score of 0/100 (Invisible).
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.