Lukka Reference Data MCP
Institutional reference data for digital assets: asset taxonomy, quality scores, entity and VASP directories, cross-exchange mappings, and a crypto actions feed.
- Brand
- Unknown
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
Lukka Reference Data MCP brings institutional digital asset reference data to Claude, normalized across exchanges, custodians, and wallets. Ask for an asset, an entity, or a mapping and get back structured data: canonical asset records with names, supply and tokenomics, blockchain and token standard, issuer and foundation participants, regulatory classifications and governance attributes, plus directories of exchanges, custodians, OTC desks, prime brokers and VASPs, and derivative contract reference data. Crypto actions cover the events that change an asset's identity or economics - hard forks, airdrops, chain migrations, token swaps and more - as a structured feed with what changed, when and why. Every asset record also carries the crypto action that established it, so a name, supply figure or mapping can be traced back to the event behind it. Reference data comes in several layers, so you can pick the one that matches the question - the Lukka Asset ID that keeps "BTC" on one venue and "XBT" in the data set pointing at the same thing, the Lukka Digital Asset Classification Standard with its five tiers from category down to sub-sector, and the Lukka Core Asset Score with a letter grade and numeric quality score. Where a ticker is ambiguous, the mapping view shows every venue-side code that resolves to the same canonical asset or pair. Typical uses: resolving tickers before pricing or reporting, checking an asset's classification and quality grade, finding how a pair is named on a given venue, screening counterparty entities, and tracking forks, airdrops and migrations across assets. Lukka is a digital-asset data company serving institutional clients, and this connector exposes the same reference data behind its commercial products. Access is read-only.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-07-29
- Tool count
- 22
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
22 tools agents can invoke
Lukka Reference Data MCP Claude Connector FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Lukka Reference Data MCP's Claude Connector 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.