Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe
Free
Nothing to run from here
Fatsecret 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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server for FatSecret API - food search, nutrition, diary, recipes, weight tracking (unofficial)
Quickstart
# 1 — run it from where its publisher ships it
npx -y fatsecret-mcp
# 2 — ask your agent something
> MCP server for FatSecret API - food search, nutrition, diary, recipes, weight tracking (unofficial)
Fatsecret is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
FLAll 1 server
fliptheweb1 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 Fatsecret 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. It is scanned, signed and pinned to the version you choose — 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. Claude Code registers it in one command.
claude mcp add fatsecret-mcp -- npx -y fatsecret-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: FATSECRET_CLIENT_ID, FATSECRET_CLIENT_SECRET, FATSECRET_CONSUMER_SECRET. You set them after installing; the value is sealed here and sent to the server on each call.
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
44 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.
Search the FatSecret food database. Returns food names, descriptions, and basic nutrition info.
Takes no parameters.
Example callreturns →
Get detailed nutritional information for a specific food by ID. Returns servings, calories, macros, and micronutrients.
Takes no parameters.
Example callreturns →
Find food by barcode (GTIN-13). UPC-A, EAN-13 and EAN-8 supported. Premier exclusive.
Takes no parameters.
Example callreturns →
Get autocomplete suggestions for a partial food search expression. Premier exclusive.
Takes no parameters.
Example callreturns →
Search recipes with optional filters for calories, macros, prep time, and recipe types.
Takes no parameters.
Example callreturns →
Get detailed recipe information by ID including ingredients, directions, and nutrition.
Takes no parameters.
Example callreturns →
Get the full list of food categories. Premier exclusive.
Takes no parameters.
Example callreturns →
Get food sub categories for a given food category. Premier exclusive.
Takes no parameters.
Example callreturns →
Get the list of food brands, optionally filtered by starting letter and type. Premier exclusive.
Takes no parameters.
Example callreturns →
Get the full list of supported recipe type names.
Takes no parameters.
Example callreturns →
Get food diary entries for a date or a specific entry by ID. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Get daily nutrition summary for a month. Returns calories and macros per day. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Add a food diary entry. Requires food_id, serving_id, and meal type. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Edit an existing food diary entry. Cannot change the date. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Delete a food diary entry by ID. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Copy food entries from one date to another, optionally filtered by meal. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Copy entries from a saved meal to a meal on a specific date. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Get the user
Takes no parameters.
Example callreturns →
Remove a food from the user
Takes no parameters.
Example callreturns →
Get the user
Takes no parameters.
Example callreturns →
Get the user
Takes no parameters.
Example callreturns →
Get the user
Takes no parameters.
Example callreturns →
Add a recipe to the user
Takes no parameters.
Example callreturns →
Remove a recipe from the user
Takes no parameters.
Example callreturns →
Get the user
Takes no parameters.
Example callreturns →
Create a new saved meal. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Edit a saved meal name, description, or associated meals. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Delete a saved meal. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Get all food items in a saved meal. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Add a food item to a saved meal. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Edit a food item in a saved meal (name or units). Cannot change serving_id. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Remove a food item from a saved meal. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Record the user
Takes no parameters.
Example callreturns →
Get the user
Takes no parameters.
Example callreturns →
Get the full list of supported exercise types and their IDs. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Shift exercise time between activities for a date. Moves minutes from one exercise to another. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Get daily calories expended from exercise for a month. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Save the current day
Takes no parameters.
Example callreturns →
Get profile status information for the authenticated user. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Create a custom food with nutrition info. Premier exclusive. Requires profile auth (check_auth_status first).
Takes no parameters.
Example callreturns →
Check if API credentials and profile authentication are configured. Call this first to understand what setup is needed.
Takes no parameters.
Example callreturns →
Configure FatSecret API credentials. Get them at https://platform.fatsecret.com/ → My Account → API Keys. Saves to persistent config file.
Takes no parameters.
Example callreturns →
Start the OAuth 1.0 authorization flow for profile access. Returns an authorization URL the user must visit. Requires API credentials (setup_credentials first).
Takes no parameters.
Example callreturns →
Complete the OAuth 1.0 flow with the verifier code from the authorization page.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Fatsecret costs nothing to install and nothing to call, 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: $8.42
$16.58 left
ATrust score 97 / 100
Release 0.0.9 · scanned 25 Aug 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 score97
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest7b1a0edae8a62385a68c9752536bd15ab9222210e90ee6b42fe878087986c90b
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| 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 surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (44 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, 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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_foods | no tags | |
| get_food | no tags | |
| find_food_by_barcode | no tags | |
| autocomplete_foods | no tags | |
| search_recipes | no tags | |
| get_recipe | no tags | |
| get_food_categories | no tags | |
| get_food_sub_categories | no tags | |
| get_brands | no tags | |
| get_recipe_types | no tags | |
| get_food_entries | no tags | |
| get_food_entries_month | no tags | |
| create_food_entry | no tags | |
| edit_food_entry | no tags | |
| delete_food_entry | no tags | |
| copy_food_entries | no tags | |
| copy_saved_meal_entries | no tags | |
| get_favorite_foods | no tags | |
| delete_favorite_food | no tags | |
| get_most_eaten_foods | no tags | |
| get_recently_eaten_foods | no tags | |
| get_favorite_recipes | no tags | |
| add_favorite_recipe | no tags | |
| delete_favorite_recipe | no tags | |
| get_saved_meals | no tags | |
| create_saved_meal | no tags | |
| edit_saved_meal | no tags | |
| delete_saved_meal | no tags | |
| get_saved_meal_items | no tags | |
| add_saved_meal_item | no tags | |
| edit_saved_meal_item | no tags | |
| delete_saved_meal_item | no tags | |
| update_weight | no tags | |
| get_weight_month | no tags | |
| get_exercises | no tags | |
| edit_exercise_entries | no tags | |
| get_exercise_entries_month | no tags | |
| save_exercise_template | no tags | |
| get_profile | no tags | |
| create_food | no tags | |
| check_auth_status | no tags | |
| setup_credentials | no tags | |
| start_auth | no tags | |
| complete_auth | no tags |
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 digest7b1a0edae8a62385
Scanned2026-08-25
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
Pinned to 0.0.9 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.0.9
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Fatsecret in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.