Evaluates dataset and AI application quality through Dingo’s rule-based, LLM-based, and MCP interfaces.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Dingo.
DataEval/dingo MCP server connects AI agents to Dingo, a Python tool for evaluating the quality of machine-learning datasets, LLM data, and production AI systems. The MCP interface lets an agent interact with Dingo’s evaluation functions instead of calling the library directly. It also exposes the available evaluation rules and prompts so an agent can discover the checks it can use.
Dingo supports two broad evaluation styles. Rule-based checks cover deterministic quality conditions, while LLM-based evaluations provide deeper assessment where a language model is appropriate. The underlying project describes more than 30 built-in heuristic rules, along with evaluation features for retrieval-augmented generation and hallucination detection.
The server is included in the dingo-python package and is started with Dingo’s command-line interface. It can use SSE transport on its default port, a custom SSE port, or stdio transport for desktop MCP clients. Agents communicate with the running process through MCP and can request Dingo evaluations or inspect the available rules and prompts.
Dingo’s broader evaluation workflow can read local files, PostgreSQL, MySQL, and SQLite databases, Hugging Face datasets, and S3 storage. Evaluations can apply different rules to different fields and can run locally or with Spark for large datasets. These data-source and execution options belong to Dingo’s evaluation system; the provided material does not specify separate MCP tool names or schemas.
Install the core package with:
Optional package extras add HHEM hallucination detection, retrieval benchmarking, or all listed optional features:
Start the MCP server over SSE with the default port:
Use dingo serve --port 9000 to select another port, or use dingo serve --transport stdio for clients such as Claude Desktop. LLM evaluation may require configuring a model API key, API URL, and model name. The example uses an OpenAI-compatible endpoint, but the material does not state that one provider is mandatory.
DataEval/dingo MCP server supports these documented capability areas:
The supplied material does not document the individual MCP tool names, argument schemas, response formats, or client configuration JSON. It also does not state that the MCP server itself provides Dingo SaaS features such as web dashboards, access control, visual reports, or REST APIs; those are described as part of the separate enterprise SaaS version.
LLM-based checks are not equivalent to local rule checks: the example configures an API key, endpoint, and model before invoking an LLM evaluator. Optional HHEM and retrieval features add separate installation requirements. Choose stdio when the client launches the process locally, and SSE when the client connects to the running server over its configured port.
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/dataeval-dingo)<a href="https://allmcps.com/mcp/dataeval-dingo"><img src="https://allmcps.com/api/badge/dataeval-dingo?style=directory" alt="Dingo on AllMCPs" /></a>