# Nutrition Intelligence Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Nutrition Intelligence

Look up nutrition facts for foods, brands and supplements, and total up what you ate.

- Record: https://musedirectory.ai/connector/nutrition-intelligence
- Category: Health
- Developer: Prospre (https://nutrition.prospre.io)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 521ms, checked 2026-11-08T05:45:51Z
- Endpoint: https://nutrition.prospre.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-07T22:46:17Z)
- Source: Found in the official MCP Registry (io.prospre/nutrients) https://registry.modelcontextprotocol.io/v0/servers?search=io.prospre%2Fnutrients

Connects to a nutrition database built from USDA, Health Canada, CIQUAL and label data. Muse can resolve everyday food phrases, look up barcodes, total the nutrients in a meal or recipe, compare products, and check a day of food and supplements against recommended intakes.

Example request: "Add up the calories, protein and fibre in my lunch and tell me how it fits my day."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Nutrition Intelligence to help me. It is a free service with an MCP server at https://nutrition.prospre.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- describe: Start here. Returns the property registry (every nutrient key with its unit and meaning), the labelling regimes, entity kinds, proof ranks, your quota, and how to use every operation. Free.
- resolve: Find what free-text food phrases refer to: "2 large eggs scrambled", "1 cup cooked rice", "Clif Bar chocolate chip". Batch up to 50 phrases. Default mode "candidates" returns, per phrase, the parsed amount and ranked candidates, each with its portions (label and grams), the amoun
- get: Full entity cards by id (batch up to 100): every published fact with unit, basis, proof rank and source; portions; identifiers; serving; quality hints. A nutrient not in "nutrients" is unknown, never zero. "missing" gives the reason only for the core label nutrients (energy, prot
- search: Supplement hits show headline_nutrients and literal headline_lines in place of food macros; other_labels lists collapsed DSLD label ids accepted by get. Find entities by name in any language, by barcode, or semantically. Filter by kind, brand, market. Returns compact hits with ke
- lookup_barcode: Product or supplement for a barcode (UPC-A, EAN-13, GTIN-14, any length; normalised). The same barcode can carry different recipes in different countries: pass market to choose. A miss opens a task for agents to find proof.
- nutrition: Totals for any mix of foods, products, recipes and supplements in any amounts (up to 200 items, at most 50 of them text; a text item costs what resolve charges for one phrase), and each item's own values: every line in items has nutrients for the same fields, in the total's unit,
- compute_recipe: Exact nutrition for a recipe: the sum of its ingredient lines (text or ids). Returns the total and per serving, plus per 100 g when you give the weighed cooked weight. Nothing is estimated: where cooking changes an ingredient, use its cooked form ("chicken breast, roasted"). A va
- compare: Items side by side on one basis: per_100g, per_serving or per_100kcal.
- query: Search and mine the whole database: keywords (the last word also matches as a prefix, for type-ahead), filters on any nutrient, sorting by up to three keys, per 100 g, per 100 kcal or per serving. E.g. foods with at least 20 g protein per 100 kcal and under 5 g sugars sorted by f
- label_lines: The master list of free label lines: every line name that labels print and the registry has no key for (a botanical, a branded blend, "creatine monohydrate"), as stored under line:<name>, with how many items state it (entities), from how many proofs (sources), and in which units.
- label: The item's nutrition panel as a given country would print it (rounding, basis, mandatory nutrients, salt vs sodium, carbohydrate definition). Values that cannot be derived exactly come back null with the reason; derived rows (salt from sodium, kJ from kcal) list derived_from. "al
- reference_values: Recommended intakes (RDA/AI), upper limits (UL, with scope e.g. "supplemental only") and label reference values (DV/RI/NRV) for a population and jurisdiction. Each value carries its source and a cite line.
- check_intake: A day of foods and supplements (up to 200 items, at most 50 of them text; a text item costs what resolve charges for one phrase) checked against recommended intakes and upper limits for a population. Limits that apply only to supplements (magnesium, vitamin E, folic acid, niacin)
- explain: Every fact behind one value: each source, its proof rank and date, which one is published and why. Use before trusting a surprising number.
- flag: Report a value that looks wrong, or a label photo that looks fake. Free. Include why and any evidence (a URL to the brand's own page is best; it is kept as text for people, never visited). Flags open review tasks. With proof_id (a photo proof, from a card's sources, e.g. "p123" i
- add_proof: Submit proof: a first-party URL (brand or restaurant page, PDF, CSV), or label photos (base64; several sides of one package beat one photo), with your reading of it. A URL is a citation: we never download it. Values that fill gaps publish at once, marked unverified; they become v
- submit_reading: Your reading of a proof from a read_proof task (one submitted without a reading): what the proof states, as typed values. Read only the proof files (GET /v1/proofs/{proof_id}/files/{n}). A proof is read once: to verify an item from a verify_reading task, find your own proof and s
- claim_status: Status of a claim (checks, decision, reason) or of submitted proof (how many readings it has and whether they agree; values stay hidden so later readers read blind) and which claims it opened).
- tasks: Small jobs that improve the data, near what you are doing: items whose values wait for independent proof, values that need proof, missing nutrients, unknown barcodes, open flags. Listing reserves nothing. Follow how to contribute; only verification and barcode tasks currently clo
- needs: What agents asked for and did not get, ranked by how many asked and how recently: phrases and searches with no match, unknown barcodes. Free. Fill one when you have the item in hand or can open its own page: add_proof with new_entity {kind, name, brand, barcode}, market, url or f
- research: One task that improves the database, with everything needed to finish it in one call: the gap or the item, what proof counts, the add_proof call prefilled, and what it earns. Free. A fill task is something two or more agents asked for and did not get; a verify task asks for your 
- suggest_domain: Suggest a website as a trusted source: a government food database, or the official site of one brand or restaurant chain. A link on a trusted domain counts as that owner's own data (the brand's site is rank 1 for its items); a link anywhere else is an unknown website at rank 4. A
- feedback: Tell us what would make this service better for you: a tool that confused you, a missing operation or field, a slow call, a wrong result, an unclear doc or skill, or what worked well. Free. Wrong nutrition values go to flag instead, so they can be fixed at the source. Feedback is
- changes: Entities changed after a sequence number (paid plans).
- link_email: Link your operator's email to this key to raise its limits and allow contributions (flag, add_proof, tasks, submit_reading). A 6-digit code is emailed to the address; confirm it with verify. Your key keeps working meanwhile. Free.
- verify: Confirm the 6-digit code emailed by register or link_email, with the key that asked for it: links the email, moves the key to the free plan and adds the contribute scope. Five wrong codes end every code sent to this key; then call link_email again.
- usage: Your key's plan, balances, limits and operation costs. Free.
- register: Create an API key. It works immediately for reads, with a small daily quota. Optionally pass your operator's email (or call link_email later): a 6-digit code is emailed, and confirming it with verify raises the quota and allows contributions. One verified email owns all its keys.

Screening checks:
- MCP handshake: pass (Answered in 517ms)
- Domain against threat feeds (Cloudflare security DNS): pass (nutrition.prospre.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (27 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)