What is the key difference between Nutriref API and Aegis Dq?

Nutriref API belongs to the Data Platforms category with local stdio execution, while Aegis Dq belongs to the Data Platforms category with local stdio execution.

How do I install Nutriref API or Aegis Dq in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Nutriref API and Aegis Dq free or paid?

Nutriref API operates under a BYOK (Pay Provider Direct) model (API Key required). Aegis Dq operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Nutriref API lists 6 tools with 2 views and 1 GitHub stars. Aegis Dq lists 6 tools with 3 views and 4 GitHub stars.

Can I use both Nutriref API and Aegis Dq together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Nutriref API vs Aegis Dq

In-depth architectural comparison of the Nutriref API and Aegis Dq MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Nutriref API

Data Platforms · Local stdio

Quality: 47/100 (Fair) | Auth: API Key required

Aegis Dq

Data Platforms · Local stdio

Quality: 48/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Nutriref API if you need specialized Data Platforms tools running via a local process. Choose Aegis Dq if your workspace requires Data Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Nutriref API when:

You need dedicated capabilities in the Data Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: USDA_API_KEY, USDA_BASE_URL, REDIS_URL, X402_NETWORK, X402_RECEIVER_ADDRESS, X402_FACILITATOR_URL, CDP_API_KEY_ID, CDP_API_KEY_SECRET.
Primary tools included: Four endpoints: search, detail, compare, recipe, Uses x402 micropayment protocol with USDC on Base, No signup or API keys required for usage.

Explore Nutriref API Details

Choose Aegis Dq when:

You need dedicated capabilities in the Data Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).

Feature & Specification Comparison

Specification	Nutriref API Younghef Data Platforms	Aegis Dq aegis-dq Data Platforms
Summary	USDA FoodData Central nutrition for AI agents — pay-per-call in USDC on Base via x402. Four tools (search, detail, compare, recipe) at $0.001–$0.005 per call. No signup, no API keys; MCPB-packaged for one-click install.	Agentic data quality framework that runs structured rules against warehouses (DuckDB, BigQuery, Athena, Databricks, Postgres), diagnoses failures with LLM root cause analysis, and proposes SQL remediations. Every LLM decision is audit-logged with cost and latency.
Category & Scope

Tools & Capabilities Breakdown

Nutriref API Tools (6)

Four endpoints: search, detail, compare, recipe

Uses x402 micropayment protocol with USDC on Base

No signup or API keys required for usage

Caching of USDA responses to reduce latency and cost

Open source with option for self-hosting

MCP server packaged for easy integration with AI agents

Aegis Dq Tools (6)

MCP pipeline loading and validation

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Nutriref API Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "younghef-nutriref-api": {
      "command": "uvx",
      "args": [
        "nutriref-mcp"
      ],
      "env": {
        "USDA_API_KEY": "YOUR_USDA_API_KEY_HERE",
        "USDA_BASE_URL": "YOUR_USDA_BASE_URL_HERE",
        "REDIS_URL": "YOUR_REDIS_URL_HERE",
        "X402_NETWORK": "YOUR_X402_NETWORK_HERE",
        "X402_RECEIVER_ADDRESS": "YOUR_X402_RECEIVER_ADDRESS_HERE",
        "X402_FACILITATOR_URL": "YOUR_X402_FACILITATOR_URL_HERE",
        "CDP_API_KEY_ID": "YOUR_CDP_API_KEY_ID_HERE",
        "CDP_API_KEY_SECRET": "YOUR_CDP_API_KEY_SECRET_HERE"
      }
    }
  }
}

Aegis Dq Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "aegis-dq-aegis-dq": {
      "command": "uvx",
      "args": [
        "aegis-dq"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Nutriref API is categorized under Data Platforms and uses a local stdio subprocess. In contrast, Aegis Dq belongs to Data Platforms using local stdio subprocess. Select Nutriref API when you need capabilities focused on data platforms and Aegis Dq when you require tools for data platforms.

More alternatives to Nutriref API More alternatives to Aegis Dq Data Platforms category hub Canonical compare URL