🍲

Created By
Aryan-Jhaveria year ago
A MCP Server for Canada's Food Guide - To allow LLM's with preset webscraping tools to fetch recipes.
Overview

What is MCP Food Guide Canada?

MCP Food Guide Canada is a web scraping server designed to provide easy access to recipes from Canada's Food Guide for language models (LLMs) using the Model Context Protocol (MCP).

How to use MCP Food Guide Canada?

To use the server, clone the repository, install the required dependencies, and configure it to work with your LLM. You can then call the server to search for recipes, retrieve detailed recipe information, and discover available filters.

Key features of MCP Food Guide Canada?

  • Search for recipes with smart filtering options (by ingredient, meal type, dietary preferences).
  • Retrieve complete recipe details including ingredients, instructions, and nutritional information.
  • Discover available filters for recipe searches.

Use cases of MCP Food Guide Canada?

  1. Finding themed recipes for meal planning.
  2. Retrieving recipes based on available ingredients.
  3. Integrating with AI assistants for cooking assistance.

FAQ from MCP Food Guide Canada?

  • Can this server be used with any LLM?

Yes! It is designed to work with any LLM that supports MCP.

  • Is there a limit to the number of recipes I can search?

Yes, the maximum number of pages and results is capped.

  • What happens if Canada's Food Guide website changes?

The server may break if the website structure changes, as it relies on specific HTML elements.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

a day ago