CommunityAbandoned· 1.1y★ 4.3by kukapay

Dune Analytics MCP

Runs and retrieves results from Dune Analytics queries for on-chain data, delivered as CSV strings.

View repo

Safety & Trust

Delv Safety Grade: C

Score 58/100 · assessed 2026-04-28

Maintainer45

Permissions75

Supply chain55

Transparency65

Incidents100

This community MCP server interfaces with Dune Analytics to run blockchain queries and retrieve on-chain data as CSV. The maintainer 'kukapay' appears to be a solo developer with limited public track record, creating moderate bus factor risk. The server requires a Dune API key stored in environment variables, which grants access to your Dune account and query execution capabilities. Permissions are reasonably scoped to read-only data retrieval from Dune's API, though the API key itself may have broader account access depending on Dune's permission model. Supply chain uses npm distribution via Smithery CLI but lacks clear versioning or dependency pinning information. The repository is open source with basic documentation, though transparency could be improved with more detailed changelogs and security practices. No known security incidents. Suitable for non-sensitive blockchain data analysis with awareness of API key exposure risks.

Lethal Trifecta (prompt-injection exposure)

TWO OF THREE

Private dataNo

Reads secrets, credentials, private files

Untrusted inputYes

Ingests web pages, PRs, issues, emails

External commsYes

Can send data outbound

On-chain data is public; query results travel outbound. Small input-axis risk from labels.

Green flags

Read-only data retrieval with scoped blockchain analytics use case
Open source repository with visible code for inspection
Uses established Dune Analytics API rather than custom infrastructure
No known security incidents or malicious activity

Red flags

Solo maintainer 'kukapay' with limited public development history
API key grants potentially broad access to Dune Analytics account
No visible dependency pinning or security audit information
Sparse commit history and minimal community engagement

Permissions requested

Outbound networkAccess secretsDB read

Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

npx -y @smithery/cli install @kukapay/dune-analytics-mcp --client claude

Env vars needed: DUNE_API_KEY

Review

Dune Analytics MCP plugs Claude directly into the blockchain analytics platform that crypto researchers actually use. You give it a Dune query ID, it runs the query and hands back CSV-formatted results. That's it. No web scraping, no manual exports, no copy-paste from the Dune UI. I'd reach for this when I'm building dashboards or reports that need fresh on-chain data without leaving the LLM context. Say you're tracking wallet activity for a DeFi protocol: you've already got queries saved in Dune that pull transaction volumes, top holders, liquidity flows. This MCP lets Claude fetch those results on demand, then reason about them or format them into a report. The CSV output means Claude can parse it directly, which works surprisingly well for tables under a few hundred rows. The main quirk is that you're working with query IDs, not raw SQL. You need to have already built and saved your queries in Dune's web interface. This isn't a tool for ad-hoc blockchain queries; it's for automating access to queries you've already written and tested. That's actually a feature if you're doing serious analysis, because Dune queries can be complex and you don't want to debug SQL through an LLM. Performance depends entirely on Dune's API and your query complexity. Heavy queries can take 30 seconds or more, which means Claude will wait. The CSV string format is fine for most use cases, but if you're pulling massive datasets, you'll hit practical limits on what Claude can process in one go. This is a niche tool. If you're not already using Dune Analytics, don't start here. If you are, and you're tired of manually exporting data to feed into analysis workflows, this is exactly what you need. It's a single-purpose bridge that does one thing competently.

Verdict

Install this if you already live in Dune Analytics and want Claude to pull query results without the export dance. Skip it if you're not doing blockchain research or don't have a Dune account with saved queries ready to go.

Good at

Direct access to Dune's blockchain data without leaving Claude, which beats manual exports for iterative analysis.
CSV output format is immediately usable by Claude for parsing, summarising, or feeding into further reasoning.
Works with your existing Dune queries, so you're not rewriting SQL or debugging through an LLM.
Clean single-purpose tool with no feature bloat or unnecessary abstractions.

Watch out

Requires a paid Dune Analytics plan with API access, which is a non-trivial monthly cost.
Only works with pre-saved Dune queries, not ad-hoc SQL, so you need to set up queries in the web UI first.
Large result sets come back as long CSV strings that can overwhelm Claude's context window.
Query execution time is entirely dependent on Dune's API, which can be slow for complex queries.

Use cases

on-chain analytics
protocol research
wallet tracking
DeFi dashboards

Getting started

1. Grab your Dune API key from the Dune Analytics dashboard (you'll need a paid plan for API access). 2. Run `npx -y @smithery/cli install @kukapay/dune-analytics-mcp --client claude` and follow the prompts to add your API key. 3. Restart Claude Desktop, then ask it to run a Dune query using a query ID from one of your saved Dune queries. 4. Verify it works by checking that Claude returns CSV-formatted results. If it times out, your query is probably too heavy or Dune's API is slow. 5. Watch out for query execution limits on your Dune plan; each MCP call burns an API credit.

Works with

Claude DesktopClaude CodeCursor