Dingo vs Server Everything

A side-by-side look at the Dingo and Server Everything MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Dingo logoDingoData Science Tools · Local subprocess (stdio)MCP server for the Dingo: a comprehensive data quality evaluation tool. Server Enables interaction with Dingo's rule-based and LLM-based evaluation capabilities and rules&prompts listing.60GoodAuth: no auth requiredServer Everything logoServer EverythingOther Tools and Integrations · Local subprocess (stdio)MCP server that exercises all the features of the MCP protocol55GoodAuth: no auth required

Verdict: choose Dingo for data science tools work as a local process; choose Server Everything for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Dingo logoChoose Dingo when

  • You need dedicated capabilities in the Data Science Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Dingo

Server Everything logoChoose Server Everything when

  • You need dedicated capabilities in the Other Tools and Integrations domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Server Everything

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDingo logoDingoServer Everything logoServer Everything
CategoryData Science ToolsOther Tools and Integrations
Quality signal60/100 · Good55/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars75991,405
Directory activity 5 views 0 installs 0 upvotes 9 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Dingo tools

No tool names declared yet. Check the project README from the listing page.

Server Everything tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Dingo

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dataeval-dingo": {
      "command": "uvx",
      "args": [
        "dingo-python"
      ]
    }
  }
}

Server Everything

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "modelcontextprotocol-server-everything": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-everything"
      ]
    }
  }
}

Frequently asked questions

Dingo is categorized under Data Science Tools and uses a local stdio subprocess. Server Everything belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Dingo for data science tools work and Server Everything for other tools and integrations.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Dingo is listed as free. Auth: no auth required. Server Everything is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add dataeval-dingo and modelcontextprotocol-server-everything as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Dingo has a quality signal of 60/100 (Good) with 5 views, 0 installs and 759 GitHub stars. Server Everything has 55/100 (Good) with 9 views, 0 installs and 91,405 GitHub stars.