Skip to main content
Glama
mwamedacen

dune-mcp

by mwamedacen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to dune-mcp

Related Servers

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 19 tools

Disambiguation4/5

Most tools have distinct purposes, but there is some potential for confusion between execute_query and execute_sql (both execute queries, with one using saved queries and the other raw SQL) and between get_query_results and get_execution_results (both retrieve results, with one for saved queries and the other for executions). The descriptions help clarify these distinctions, but an agent might initially misselect without careful reading.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (e.g., archive_query, cancel_execution, create_table). The verbs are clear and descriptive (e.g., create, get, update, delete), and there are no deviations in style or convention throughout the set.

Tool Count4/5

With 19 tools, the count is slightly high but reasonable for a comprehensive data query and management platform like Dune. It covers query execution, result retrieval, table management, and query lifecycle operations, which justifies the number, though it might feel a bit heavy for simpler use cases.

Completeness5/5

The tool set provides complete coverage for Dune's domain, including CRUD operations for queries (create, get, update, archive, privacy toggles) and tables (create, clear, delete, insert rows, upload CSV), plus execution management (execute, cancel, status, results retrieval). There are no obvious gaps; agents can handle full workflows from query creation to result analysis.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources