← Registry tracker

Denodo MCP Connector

This extension connects Claude Desktop to a running Denodo MCP Server, enabling AI-powered querying of Denodo Virtual DataPort databases. Supports three authentication modes: (1) Basic Auth with username and password; (2) OAuth bearer token — paste a static JWT, optionally with automatic refresh via a refresh token grant; (3) OAuth Authorization Code flow — a browser window opens for you to log in, and the connector handles token refresh silently from then on (uses PKCE for public clients). Requires a Denodo MCP Server (v9, build 20260317 or later) running and accessible.

View in the Claude registry
Integration type
Connector
Verification status
Verified connector
Platform
Claude
Category
Data & Analytics

The broad Category that contains the Primary Subcategory.

Primary Subcategory
Pending

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is visible.

Brand
Denodo
Access
Unknown
First tracked
2026-08-13
Tool count
6
Geography
US

Claude Discoverability Score

Your public score is being prepared

Denodo MCP Connector is tracked in the public registry. Its Discoverability Score will appear as soon as the public benchmark is ready - never as an estimate.

Get your Discoverability Score
Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Denodo MCP Connector has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.
Score explained

How the Discoverability Score works

The Claude Discoverability Score will be the percentage of contested conversations where Denodo MCP Connector appears in the connector picker or Claude invokes it directly. Found and Positioned will be shown as diagnostics, not score inputs.

InvisibleBuriedEmergingCompetitiveWinning

Organic discovery scoring is pending. Your Connector score will appear on this scale when measurement goes live.

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.

Read the full scoring methodologyRecommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.
Tools

6 tools agents can invoke

Denodo MCP Connector FAQ
How do I improve a Verified 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.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.