Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
TACO Brazil is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
12
downloads a day
local
runs on your machine
520
downloads in 30d
What it does
Brazilian Food Composition Table (TACO): 597 foods, nutrients, and household measures
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user taco-brazil-mcp '--' npx -y taco-br-mcp
# 2 — ask your agent for something these tools do
# calc_meal, compare_foods, convert_household_measure and 5 more
TACO Brazil costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
IAAll 1 server
ianhudsonai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts TACO Brazil as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user taco-brazil-mcp '--' npx -y taco-br-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | Foods in the meal. The same food may appear more than once. |
| nutrients | array | no | Nutrient keys to total. Omit for energy, protein, fat, carbohydrate, fiber and sodium. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| food_ids | array | yes | TACO food numbers to compare, as returned by search_food. |
| nutrients | array | no | Nutrient keys to compare. Omit for energy, protein, fat, carbohydrate, fiber and sodium. |
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.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| food_id | integer | no | TACO food number, as returned by search_food. Preferred over food_query. |
| food_query | string | no | 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 | no | How many of the measure (default 1; may be fractional, e.g. 0.5). |
Amino acid profile (lysine, leucine, tryptophan, etc.) of one TACO food by id, per 100 g or scaled to grams. TACO only has it for 26 foods; others return available:false with the list of foods that do (not zero).
No parameter schema on file.
Fatty acid profile (saturated, mono/polyunsaturated, omega-3/6, EPA, DHA, trans, and individual acids) of one TACO food by id, per 100 g or scaled to grams. Only 423 of 597 foods have it; others return available:false (not zero). Tr is {"trace":true}, missing is null.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| food_id | integer | yes | TACO food number, as returned by search_food. |
| grams | number | no | Quantity in grams of edible portion. Omit for the table basis of 100 g. |
| nutrients | array | no | Nutrient keys to return (e.g. "energy_kcal", "protein_g", "iron_mg"). Omit for all. |
Health check for the taco-br server. Returns the server name, version and the data source citation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| echo | string | no | Optional text to echo back in the message. |
Find foods in the Brazilian TACO table (597 items, per 100 g) by name in Portuguese. Accent-insensitive; tolerates typos; knows regional names (aipim, macaxeira, pão de sal, mandioquinha). Returns ids to use with get_nutrients. Restaurant dishes and brands are mostly absent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Food name in Portuguese, e.g. "feijão carioca cozido" or "pao de queijo". |
| limit | integer | no | Maximum number of results (default 10). |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install TACO Brazil or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 0.2.0 · scanned 31 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digestbd2f1a10fc65a3e187270f9ab0171f0899bf8ab689cae20adb3cfd29e462972e
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestbd2f1a10fc65a3e1
Scanned2026-10-31
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.0. Pin a release below and the command asks for exactly that one.
0.2.0
31 Oct 2026
latestNo release note was published with this version.
0.1.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish TACO Brazil can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.