ReciPal MCP for AI. Audit recipes and track nutritional compliance instantly.

Q: How do I list all recipes using ReciPal? (listrecipalrecipes)

You run listrecipalrecipes to get your entire catalog. It provides a full inventory of every recipe ID you have access to, which is the starting point for any audit.

Q: Can I search for ingredients using listrecipalingredients? (listrecipalingredients)

Yes, running listrecipalingredients provides the complete master list. You can then ask your agent to filter or check if a specific ingredient is present in that massive catalog.

Q: How do I check if ReciPal is working? (checkapistatus)

Run checkapistatus first. This confirms the entire data source is online and ready for use, so you don't waste time running queries that will fail.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Connect to your AI in seconds.

ReciPal lets your AI agent handle complex food manufacturing audits. It connects to a specialized database to check nutrition labels, audit ingredient lists, and retrieve full recipe details—all through natural conversation.

Stop opening dozens of portals; let your agent do the data heavy lifting for compliance checks.

What your AI can do

Check api status

Confirms if the ReciPal service is currently running and accessible.

Get recipe details

Retrieves full nutritional facts, including ingredients and calorie counts for a specific recipe ID.

List recipal ingredients

Generates a complete list of all available ingredient components in the database.

+ 1 more capabilities included

List all known recipes

Retrieves the full list of recipe identifiers from your ReciPal account.

Get specific recipe details

Pulls comprehensive nutritional and ingredient facts for a single recipe using its unique ID.

Audit available ingredients

Lists every ingredient stored in the ReciPal database, letting you check component availability.

Check service status

Verifies if the entire nutritional data source is currently operational and connected.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

ReciPal MCP Server: 4 Tools for Recipe Auditing

These tools let your AI client check API status, list all recipes, audit ingredients, or pull specific nutritional data from the ReciPal database.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using ReciPal on Vinkius

Check Api Status

Confirms if the ReciPal service is currently running and accessible.

Get Recipe Details

Retrieves full nutritional facts, including ingredients and calorie counts for a...

List Recipal Ingredients

Generates a complete list of all available ingredient components in the database.

List Recipal Recipes

Fetches an inventory listing of every recipe stored in your account.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The ReciPal integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "recipal": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the ReciPal tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"recipal": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with ReciPal, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,000+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ReciPal. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 4 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Checking ingredient compliance shouldn't require jumping between five different portals.

Today, verifying a single recipe’s label involves logging into the labeling portal, finding the SKU, downloading the nutritional sheet as a PDF, opening Excel to cross-reference allergens, and then emailing it to compliance. It's slow, error-prone, and takes hours.

With ReciPal MCP Server, you simply ask your agent: 'What are the allergens in Recipe ID 12345?' The agent runs `get_recipe_details`, pulls the verified data directly from the source, and gives you a clean answer. You get verifiable facts, not documents.

ReciPal MCP Server: Get full nutritional details with one call.

Manual steps that vanish include searching for specific component names in massive spreadsheets and having to manually check API uptime before starting the audit. You used to spend time gathering data on *how* to search, not what the ingredients actually were.

Now you run `get_recipe_details` and get structured JSON output instantly. The process is direct: identify the recipe ID, call the tool, receive clean data. It’s that simple.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

What your AI can actually do with this

ReciPal lets your AI agent handle complex food manufacturing audits. It connects to a specialized database so you can check nutrition labels, audit ingredient lists, and pull full recipe details—all just by talking to it. Don't open dozens of portals; let your agent do the data heavy lifting for compliance checks.

Recipe Inventory & Lookup

You need to know what recipes you've got on file? You can use list_recipal_recipes to pull a full roster of every recipe identifier stored in your account. This gives you the initial list—the roadmap, if you will. Once you have that ID, or if you already know it, you'll want to run get_recipe_details.

That tool doesn't just give you basic stats; it pulls comprehensive nutritional facts and ingredient breakdowns for a single recipe using its unique identifier. You get the full picture: precise calorie counts and detailed lists of components needed for compliance checks.

Ingredient Audit Capabilities

If you need to know what raw materials you can even work with, list_recipal_ingredients generates a complete inventory of every single component stored in the ReciPal database. This lets you audit ingredient availability and check component distribution across your product line. You use this when you gotta confirm if a specific allergen or a core vitamin is actually sitting in your system before writing up a label.

System Health Checks

Before you start running reports, you gotta make sure the data source isn't offline. check_api_status verifies if the entire nutritional data set is currently operational and connected. If that status check fails, you know right away that your whole research workflow is stalled, saving you time chasing phantom errors.

How You Use It

You tell your agent what you're doing—maybe "Check all recipes with less than 500 calories" or "List every ingredient containing gluten." Your AI client then figures out which tools to run: it calls list_recipal_recipes first, maybe filters that list using the data from get_recipe_details, and keeps track of component availability using list_recipal_ingredients.

It's built for compliance teams, food manufacturers, and anyone whose job depends on having fast, verifiable numbers about ingredients and nutrition. You don't manually cross-reference spreadsheets; you talk to your agent, and it pulls the verified data right back.

The system handles all that deep linking between ingredient components and finished recipe structures, letting you audit everything from a simple component list to complex nutritional breakdowns in one conversation.

Built · Hosted · Managed by Vinkius ReciPal MCP Server - Audit Nutrition & Ingredients

Server ID 019d8476-7f7e-7246-9707-35587afaea85

Vinkius Inspector

Compliance Grade A+

Score 100/100

Report View Report ↗

Here's how it actually works

The bottom line is that your AI client acts as a real-time nutritional consultant, querying the database for you instead of requiring manual input or portal navigation.

Subscribe to the ReciPal server and enter your unique API key into your AI client.

Your agent runs a command (e.g., list_recipal_recipes) through the MCP connection.

The agent receives structured data containing recipe names, IDs, and metadata, which it then presents in plain language.

Who is this actually for?

Compliance Leads and Food Manufacturers who spend their days manually auditing ingredient lists against strict regulatory standards. If your job involves verifying label markers across dozens of recipes, this is built for you. It’s for the ops engineer who can't afford to spend hours cross-referencing spreadsheets just to confirm a calorie count.

Compliance Officer

Runs rapid audits on labeling markers and ingredient lists using natural language queries against get_recipe_details.

Food Manufacturer Operations Lead

Automates data querying to track recipe compliance and manage cross-functional manufacturing requirements.

Nutritionist/Chef

Verifies ingredient breakdowns or calculates calorie counts for new product development without manual searching or external database lookups.

What Changes When You Connect

Verify Nutritional Counts: Use get_recipe_details to pull exact calorie counts and full nutritional breakdowns for any recipe ID. You get the precise numbers needed for labeling, eliminating manual calculation errors.

Full Ingredient Inventory: Run list_recipal_ingredients to see every component in your database at once. This lets you quickly check if a specific ingredient is available before starting product research.

Manage Recipe Catalog: The list_recipal_recipes tool gives you a complete, up-to-date list of all recipes in your account without needing to log into the main labeling portal.

Compliance Confidence: By asking your agent to audit ingredients against dietary rules, you ensure data is always verified and precise. This capability drastically cuts down on manual compliance checks.

Always Operational: Use check_api_status first. Knowing your nutritional research workflow is active means you can trust the data when deadlines are tight.

See it in action

01 01

Checking a new product's ingredient compliance

A manufacturer needs to know if Product X contains any restricted allergens. Instead of cross-referencing multiple sheets, they ask their agent: 'Check all recipes for the allergen list.' The agent uses list_recipal_ingredients and reports back on component availability.

02 02

Comparing two recipe versions

A chef needs to compare the nutritional profile of an old granola bar versus a new one. They feed both Recipe IDs into their agent, which runs get_recipe_details for both and provides a side-by-side calorie and ingredient comparison.

03 03

Auditing product line completeness

An operations lead needs to know how many recipes are in the system. They run list_recipal_recipes, immediately getting an accurate count and list of available titles without needing admin access to the backend portal.

04 04

Validating raw material usage

A team needs to know if they have enough oats for a new batch. They run list_recipal_ingredients and search the massive component list, confirming 'oats' is available before committing production resources.

The honest tradeoffs

Searching by keyword

Anti-pattern

Asking the agent, 'Tell me about granola bars.' The system might fail or provide generic data because it doesn't know which specific recipe ID you mean.

The Fix

You must first use list_recipal_recipes to get a list of IDs, then pass the correct ID into get_recipe_details. This ensures accurate nutritional reporting.

Assuming connectivity

Anti-pattern

Running complex audits right before a major product launch without checking the data source first. You might waste time running queries against an offline server.

The Fix

Always start with check_api_status. If it fails, you know immediately that your nutritional workflow is down and needs fixing.

Over-querying the database

Anti-pattern

Running list_recipal_ingredients when all you really needed was to check for one specific component (e.g., 'sugar'). This wastes time scanning thousands of irrelevant items.

The Fix

If you only need a small subset, use your agent's natural language query capability after identifying the necessary tool call.

When It Fits, When It Doesn't

Use ReciPal if your core workflow revolves around ingredient compliance, nutritional tracking, or verifying recipe data against strict standards. You need to know what is in a product and how much. Don't use this if you are trying to analyze market trends, predict consumer behavior, or manage supply chain logistics outside of ingredients. For those tasks, look for tools that connect to financial databases or e-commerce platforms instead. If you just need a general list of products without nutritional data, check for product management APIs rather than relying on get_recipe_details.

Questions you might have

How do I list all recipes using ReciPal? (list_recipal_recipes) +

You run list_recipal_recipes to get your entire catalog. It provides a full inventory of every recipe ID you have access to, which is the starting point for any audit.

What data does get_recipe_details provide? (get_recipe_details) +

This tool gives deep-dive nutritional and ingredient information. It reports precise calorie counts, serving sizes, and a full breakdown of components for one specific recipe.

Can I search for ingredients using list_recipal_ingredients? (list_recipal_ingredients) +

Yes, running list_recipal_ingredients provides the complete master list. You can then ask your agent to filter or check if a specific ingredient is present in that massive catalog.

How do I check if ReciPal is working? (check_api_status) +

Run check_api_status first. This confirms the entire data source is online and ready for use, so you don't waste time running queries that will fail.

When using `get_recipe_details`, how can I pull out just the serving metadata and calorie totals? +

It returns structured data for extraction. Your AI client receives a full JSON payload, allowing your agent to specifically parse and isolate only the required fields—like total calories or per-serving counts—without processing unnecessary text.

If I have thousands of recipes, does `list_recipal_recipes` handle bulk requests? +

Yes, it supports pagination for large catalogs. The tool returns results in manageable batches, so your agent can safely iterate through the entire recipe list without running into rate limits or timeouts.

Can I use `list_recipal_ingredients` to filter by ingredient category? +

The function lists all available ingredients. While it doesn't offer filtering by category, you can pass the resulting list to your agent for rapid classification and thematic grouping.

What happens if I provide an invalid ID when calling `get_recipe_details`? +

The system throws a specific error code indicating the missing resource. Your agent catches this error, allowing it to alert you immediately and prompt for a correct recipe identifier without stopping your workflow.

How do I find my ReciPal API Key? +

Log in to your ReciPal account, navigate to your account settings, and you will find your API Key in the integrations or developer section. Copy and paste it below.

Can the agent show serving sizes? +

Yes. Every recipe record retrieved by your agent includes serving size metadata and the number of servings per recipe.

Does it support ingredient lists? +

Yes. The get_recipe_details tool retrieves the full list of ingredients used in a specific recipe, along with their weights.

Connect to your AI in seconds.

Check api status

Get recipe details

List recipal ingredients

ReciPal MCP Server: 4 Tools for Recipe Auditing

Make your AI actually useful.

Check Api Status

Get Recipe Details

List Recipal Ingredients

List Recipal Recipes

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Works with Claude, ChatGPT, Cursor, and more

Checking ingredient compliance shouldn't require jumping between five different portals.

ReciPal MCP Server: Get full nutritional details with one call.

What your AI can actually do with this

Recipe Inventory & Lookup

Ingredient Audit Capabilities

System Health Checks

How You Use It

Here's how it actually works

Who is this actually for?

What Changes When You Connect

See it in action

Checking a new product's ingredient compliance

Comparing two recipe versions

Auditing product line completeness

Validating raw material usage

The honest tradeoffs

Searching by keyword

Assuming connectivity

Over-querying the database

When It Fits, When It Doesn't

Questions you might have