nutripulse
NutriPulse: Global nutrition intelligence API — 15 endpoints. GLP-1 nutrition companion (deterministic protein targets + muscle preservation for semaglutide/tirzepatide users), barcode-level ultra-processed food checks (NOVA + additive census, live Open Food Facts), supplement brand safety verifi...
This record as markdown: /tools/com-theaslangroupllc-pulse-pulsenetwork/nutripulse.md
What nutripulse does on Pulsenetwork
AI agents call nutripulse to retrieve information from Pulsenetwork without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
age | string | — | Age |
sex | string | — | Sex |
diet | string | — | diet |
drug | string | — | semaglutide | ozempic | wegovy | tirzepatide | mounjaro | zepbound | liraglutide | saxenda | other |
goal | string | — | goal |
lang | string | — | lang |
meal | string | — | meal |
name | string | — | name |
brand | string | — | Supplement brand to verify |
foods | string | — | Comma-separated food names e.g. chicken,beef,tofu |
goals | string | — | Health goals |
query | string | — | query |
Parameters from the server's own tool schema.
Why nutripulse is rated Low
Retrieves nutrition intelligence and food/supplement data; no data modification, deletion, or financial transactions occur.
From the tool's definition queries nutrition data, food profiles, supplement information, PubMed research, lab interpretation
Risk signalsHigh parameter count (30 properties)
Attacks that exploit this kind of access
The rule that runs nutripulse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pulsenetwork, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nutripulse, this is the rule to start with:
nutripulse is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pulsenetwork, apply this rule, and every nutripulse call is checked against it from then on.
Questions about nutripulse
NutriPulse: Global nutrition intelligence API — 15 endpoints. GLP-1 nutrition companion (deterministic protein targets + muscle preservation for semaglutide/tirzepatide users), barcode-level ultra-processed food checks (NOVA + additive census, live Open Food Facts), supplement brand safety verification (FDA recalls verbatim + third-party-testing status), plus PubMed-grounded supplement analysis, glucose patterns, lab interpretation, longevity, prenatal. Coverage: Global Endpoints: • research ($0.10): Nutrition research synthesis • food ($0.08): Food nutrition profile • supplement ($0.10): Supplement analysis • plan ($0.15): Personalized nutrition plan • compare ($0.08): Food comparison • analyze ($0.08): Meal analysis • stack ($0.12): Supplement stack • glucose ($0.10): CGM glucose pattern interpretation • interactions ($0.10): Supplement interaction checker • labs ($0.15): Blood work interpretation • longevity ($0.10): Longevity protocol synthesis • prenatal ($0.10): Prenatal nutrition by trimester • glp1 ($0.15): GLP-1 nutrition companion • upf-check ($0.02): Ultra-processed food check by barcode • supplement-check ($0.15): Supplement brand safety verification. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.
nutripulse accepts 12 parameters: age, sex, diet, drug, goal, lang, meal, name, brand, foods, goals, query. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for nutripulse: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Pulsenetwork. Nothing to install.
nutripulse is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the nutripulse rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for nutripulse. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
nutripulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pulsenetwork, and thousands of servers like it.
This server
Across the catalogue