Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Zelta Daily Calorie Target

REMOTE · CALORIE-MCP.ZELTA.IN

Daily calorie target to lose, keep or gain weight, plus a weight goal timeline.

+3 this week 74 Trust /100

Last scanned (22 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability36
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 373 tokens (~124/item across 3 items; 2 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Changelog

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.

  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 31 Oct 26 +1
    • Server version: 1.0.0 → 1.0.1 functional
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 · Probed https://calorie-mcp.zelta.in/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zelta.in CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 c40e4600d08a6ac013bb2b31fd1adf15
SANs: zelta.in, calorie-mcp.zelta.in, *.calorie-mcp.zelta.in
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of calorie-mcp.zelta.in. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
in. present 10094 13 Verified
zelta.in. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://calorie-mcp.zelta.in/mcp Verified 200
http (plaintext) http://calorie-mcp.zelta.in/mcp Inconclusive 405
MCP tools · 2 exposed · ~363 tokens

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 →

Tool Tokens
daily_calorie_target ~225

Use this when an adult asks how many calories to eat a day to lose weight or maintain, such as "how many calories should I eat to lose weight, 30 year old woman 70 kg 160 cm", "maintenance calories", "TDEE calculator" or "calorie deficit for 0.5 kg a week". Do not use for children, pregnancy or breastfeeding, eating disorders, medical diets, or medication questions.

NameTypeReqDescription
activitystringyesActivity level: sedentary, light, moderate, active or very_active
ageintegeryesAge in years
height_cmnumber–Height in centimetres
height_ftnumber–Height feet part, if not using centimetres
height_innumber–Height inches part, used with height_ft
loss_kg_per_weeknumber–Weekly loss pace in kg, default 0.5; 0 = maintenance
sexstringyesSex used by the formula
weight_kgnumberyesCurrent weight in kilograms

No output schema declared.

No examples provided.

weight_loss_timeline ~138

Use this when someone asks how long it takes to lose a set amount of weight, such as "how long to lose 10 kg", "85 to 75 kg how many weeks" or "how fast can I lose 5 kg with a 500 calorie deficit". Do not use for medical weight-loss plans, crash diets, children, pregnancy, or medication questions.

NameTypeReqDescription
current_kgnumberyesCurrent weight in kilograms
daily_deficit_kcalnumber–Daily calorie deficit, default 500 (max 1,000)
target_kgnumberyesGoal weight in kilograms, below current

No output schema declared.

No examples provided.

Install

How do I install the Zelta Daily Calorie Target MCP server?

Zelta Daily Calorie Target is a hosted endpoint at https://calorie-mcp.zelta.in/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · calorie-mcp.zelta.in

# add to Claude Code
claude mcp add --transport http in-zelta-calorie-target 'https://calorie-mcp.zelta.in/mcp'
Common questions

What is the Zelta Daily Calorie Target MCP server?

Zelta Daily Calorie Target is an MCP server listed in the public MCP registry as in.zelta/calorie-target. Daily calorie target to lose, keep or gain weight, plus a weight goal timeline. This page covers its hosted endpoint (https://calorie-mcp.zelta.in/mcp).

Is the Zelta Daily Calorie Target MCP server safe to use?

Zelta Daily Calorie Target scores 74 out of 100 on VerifyMCP. 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 Zelta Daily Calorie Target MCP server expose?

Zelta Daily Calorie Target exposes 2 tools: daily_calorie_target, weight_loss_timeline. Their descriptions and schemas cost roughly 363 tokens of context every time the server is loaded.

Does the Zelta Daily Calorie Target MCP server require authentication?

No. We connected to Zelta Daily Calorie Target without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Zelta Daily Calorie Target MCP server still maintained?

Zelta Daily Calorie Target 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.