Food Tracker MCP

Created By
nagarjun226a year ago
A simple Model Context Protocol (MCP) server that connects Claude AI with the OpenFoodFacts database to create an intelligent nutritional assistant.
Overview

What is Food Tracker MCP?

Food Tracker MCP is a Model Context Protocol (MCP) server that connects Claude AI with the OpenFoodFacts database to create an intelligent nutritional assistant for tracking food consumption and managing dietary restrictions.

How to use Food Tracker MCP?

To use Food Tracker MCP, set up the server by following the installation instructions, then register it with the Claude platform to interact with it using various commands related to food tracking and nutrition analysis.

Key features of Food Tracker MCP?

  • Search for food products by barcode or keyword
  • Analyze nutritional content of food products
  • Create meal plans based on specific nutrition goals
  • Track food consumption with meal logging
  • Manage dietary restrictions and allergies
  • Check product compatibility with user restrictions
  • View food logs and nutrition summaries

Use cases of Food Tracker MCP?

  1. Logging daily food intake and tracking nutrition.
  2. Managing dietary restrictions for allergies or specific diets.
  3. Analyzing nutritional content of various food products.
  4. Creating personalized meal plans based on user preferences.

FAQ from Food Tracker MCP?

  • Can Food Tracker MCP help with all dietary restrictions?

Yes! It allows users to manage various dietary restrictions including allergens and specific diets.

  • Is Food Tracker MCP free to use?

Yes! Food Tracker MCP is free to use for everyone.

  • How does Food Tracker MCP analyze nutrition?

It connects to the OpenFoodFacts database to retrieve and analyze nutritional information of food products.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nagarjun226
Star
0
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago