TACO Brasil
NPM · TACO-BR-MCP
Tabela Brasileira de Composição de Alimentos (TACO): 597 foods, nutrients and household measures
Available components
Last scanned (17 hours ago)
Scores higher than 69% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ianhudsonai/taco-br-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 740 tokens (~123/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Oct 26 81
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/taco-br-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ianhudsonai/taco-br-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ianhudsonai/taco-br-mcp/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 3584184939 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:8a97669da8b696cae86c5d43e4478a2e8088ae7ed8af8b8de6db0afc2693978ae4340cc1bf6029929fca029eecf615d2a27b637e1391ab76312c682b8 |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calc_meal Calculate the nutrients of a meal ~140
Sum nutrients over a list of TACO foods (ids from search_food). Each item has either grams or a household_measure with quantity (e.g. "colher de sopa" x 2, covered foods only; see convert_household_measure). Totals are lower bounds when an item has no data for a nutrient: the response says which. Defaults to energy, protein, fat, carbohydrate, fiber and sodium.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Foods in the meal. The same food may appear more than once. |
| nutrients | array | – | Nutrient keys to total. Omit for energy, protein, fat, carbohydrate, fiber and sodium. |
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | yes | True when every requested nutrient has data for every item (no total is a lower bound). |
| household_source | string | – | Citation for the household measure weights; set when any item used one. |
| items | array | yes | The meal items in the order received. |
| notes | array | yes | Caveats about this answer. |
| source | string | yes | Citation for the data. |
| total_grams | number | yes | Sum of the item quantities. |
| totals | array | yes | One entry per requested nutrient, in table order. |
No examples provided.
compare_foods Compare foods side by side ~104
Compare 2 to 10 TACO foods (ids from search_food) on chosen nutrients, per 100 g of edible portion. Missing data stays null or {"trace":true}; do not rank a food with null as having less.
| Name | Type | Req | Description |
|---|---|---|---|
| food_ids | array | yes | TACO food numbers to compare, as returned by search_food. |
| nutrients | array | – | Nutrient keys to compare. Omit for energy, protein, fat, carbohydrate, fiber and sodium. |
| Name | Type | Req | Description |
|---|---|---|---|
| basis | string | yes | Quantity all values refer to. |
| foods | array | yes | The foods compared, in the order received. |
| notes | array | yes | Caveats about this answer. |
| nutrients | array | yes | One row per requested nutrient, in table order. |
| source | string | yes | Citation for the data. |
No examples provided.
convert_household_measure Convert a household measure to grams ~210
Convert a Brazilian household measure (e.g. 2 colheres de sopa, 1 unidade, 1 fatia) of a TACO food to grams, using the IBGE POF table through a hand-curated mapping. Only some foods are covered; it never guesses: on ambiguity it returns candidates, and for uncovered foods or measures it says so. Pass food_id (from search_food) or food_query.
| Name | Type | Req | Description |
|---|---|---|---|
| food_id | integer | – | TACO food number, as returned by search_food. Preferred over food_query. |
| food_query | string | – | Food name in Portuguese, used only when food_id is not given; must match exactly one food. |
| measure | string | yes | Household measure in Portuguese, e.g. "colher de sopa", "unidade", "fatia", "concha", "copo americano". |
| quantity | number | – | How many of the measure (default 1; may be fractional, e.g. 0.5). |
| Name | Type | Req | Description |
|---|---|---|---|
| available_measures | array | – | Measures known for this food (status unknown_measure). |
| candidates | array | – | Foods matching the query (status ambiguous_food), best first. |
| food | object | – | The resolved food (not set for ambiguous_food / no_food_match). |
| grams | number | – | quantity x grams_per_measure (status ok). |
| grams_per_measure | number | – | Weight of one measure in grams (status ok). |
| household_source | string | yes | Citation for the household measure weights. |
| measure | object | – | The matched household measure (status ok). |
| notes | array | yes | Caveats and next steps. |
| quantity | number | – | How many of the measure (status ok). |
| source | string | yes | Citation for the nutrient table. |
| status | string | yes | ok: grams computed. ambiguous_food: the query matched several foods, pick an id from candidates. no_food_match: no food found. no_household_data: this food has no curated household measures, ask for… |
No examples provided.
get_nutrients Get nutrients of a food ~132
Full composition of one TACO food by id (from search_food), per 100 g or scaled to a quantity in grams. Missing data is reported as null (not analyzed) or {"trace":true}, never as 0.
| Name | Type | Req | Description |
|---|---|---|---|
| food_id | integer | yes | TACO food number, as returned by search_food. |
| grams | number | – | Quantity in grams of edible portion. Omit for the table basis of 100 g. |
| nutrients | array | – | Nutrient keys to return (e.g. "energy_kcal", "protein_g", "iron_mg"). Omit for all. |
| Name | Type | Req | Description |
|---|---|---|---|
| basis_grams | number | yes | Quantity the amounts refer to, in grams of edible portion. |
| food | object | yes | – |
| not_analyzed_nutrients | array | yes | Keys with no value in the TACO table; not zero. |
| notes | array | yes | Caveats about this food or this answer. |
| nutrients | array | yes | Requested nutrients, in table order. |
| scaled | boolean | yes | True when amounts were computed from the per-100 g table values for another quantity. |
| source | string | yes | Citation for the data. |
| trace_nutrients | array | yes | Keys reported as trace (Tr). |
No examples provided.
ping Ping ~42
Health check for the taco-br server. Returns the server name, version and the data source citation.
| Name | Type | Req | Description |
|---|---|---|---|
| echo | string | – | Optional text to echo back in the message. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | Always true when the server is alive. |
| server | string | yes | Server name. |
| source | string | yes | Citation for the data this server exposes. |
| version | string | yes | Server version. |
No examples provided.
search_food Search foods in TACO ~112
Find foods in the Brazilian TACO table (597 items, per 100 g) by name in Portuguese. Accent-insensitive; knows a few synonyms (aipim, macaxeira, pão de sal). Returns ids to use with get_nutrients. Restaurant dishes and brands are mostly absent.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results (default 10). |
| query | string | yes | Food name in Portuguese, e.g. "feijão carioca cozido" or "pao de queijo". |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The query as received. |
| results | array | yes | Best matches first. |
| source | string | yes | Citation for the data. |
| total_matches | integer | yes | How many foods in the table match the query. |
No examples provided.
How do I install the TACO Brasil MCP server?
TACO Brasil runs locally as an npm package, launched with npx -y taco-br-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · taco-br-mcp
claude mcp add ianhudsonai-taco-br -- npx -y taco-br-mcp
What is the TACO Brasil MCP server?
TACO Brasil is an MCP server listed in the public MCP registry as io.github.ianhudsonai/taco-br. Tabela Brasileira de Composição de Alimentos (TACO): 597 foods, nutrients and household measures. This page covers its npm package (taco-br-mcp).
Is the TACO Brasil MCP server safe to use?
TACO Brasil scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TACO Brasil MCP server expose?
TACO Brasil exposes 6 tools: ping, search_food, get_nutrients, calc_meal, compare_foods, convert_household_measure. Their descriptions and schemas cost roughly 740 tokens of context every time the server is loaded.
Is the TACO Brasil MCP server still maintained?
TACO Brasil is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the TACO Brasil MCP server under?
TACO Brasil declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.