# Zelta Protein Per Day (remote · protein-mcp.zelta.in)

Daily protein need by weight and goal, with a sample Indian food plan to hit it.

- Trust score: 75/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `protein-mcp.zelta.in`: 75/100 (this document), [markdown](https://verifymcp.io/servers/in-zelta-protein-target/protein-mcp.md), [page](https://verifymcp.io/servers/in-zelta-protein-target/protein-mcp)

## Channel facts

- Endpoint: `https://protein-mcp.zelta.in/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 41/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 276 tokens (~92/item across 3 items; 2 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Zelta Protein Per Day MCP server?

Zelta Protein Per Day is a hosted endpoint at https://protein-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.

### Claude

```bash
claude mcp add --transport http in-zelta-protein-target 'https://protein-mcp.zelta.in/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "in-zelta-protein-target": {
      "url": "https://protein-mcp.zelta.in/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "in-zelta-protein-target": {
      "type": "http",
      "url": "https://protein-mcp.zelta.in/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.in-zelta-protein-target]
url = "https://protein-mcp.zelta.in/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "in-zelta-protein-target": {
      "type": "remote",
      "url": "https://protein-mcp.zelta.in/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add in-zelta-protein-target --url 'https://protein-mcp.zelta.in/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  in-zelta-protein-target:
    url: "https://protein-mcp.zelta.in/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "in-zelta-protein-target": {
      "Transport": "http",
      "Url": "https://protein-mcp.zelta.in/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add in-zelta-protein-target -t streamable-http -u 'https://protein-mcp.zelta.in/mcp'
```

### Other

```json
{
  "mcpServers": {
    "in-zelta-protein-target": {
      "type": "http",
      "url": "https://protein-mcp.zelta.in/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 75, +1)

- [security] Stability: 0.97 → pass

### 2026-10-31 (score 74, +1)

- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-29 (score 73, +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.

### 2026-10-27 (score 72, +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.

### 2026-10-25 (score 71, +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.

### 2026-10-23 (score 70, +1)

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

### 2026-10-20 (score 69, +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.

### 2026-10-18 (score 68, +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.

## MCP tools (2)

### `protein_per_day` (~135 tokens)

Protein per day

Use this when an adult asks how much protein they need a day, such as "how much protein per day for 70 kg", "protein for weight loss 80 kg woman" or "protein intake to build muscle 65 kg". Do not use for children, pregnancy, kidney or liver disease, medical diets, or supplement and medication questions.

Input parameters:

- `goal` (string, required): Goal: maintain, weight_loss or muscle_gain
- `height_cm` (number): Optional height in centimetres; above BMI 25 the target uses the weight at BMI 25
- `weight_kg` (number, required): Body weight in kilograms

### `protein_food_plan` (~132 tokens)

Sample Indian protein day

Use this when someone asks how to get a protein amount from Indian food, such as "how to get 80 g protein a day vegetarian", "high protein Indian veg foods for 100 g" or "eggetarian 90 g protein sample day". Builds a sample day from dal, paneer, curd, soya, milk, eggs, chicken and fish. Do not use for medical diets, kidney disease, allergies, or supplement questions.

Input parameters:

- `diet` (string, required): Diet type: veg, eggetarian or non_veg
- `grams` (number, required): Daily protein target in grams

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/in-zelta-protein-target/protein-mcp#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 70
- 2026-10-23: 70
- 2026-10-22: 69
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 68
- 2026-10-18: 68
- 2026-10-17: 67
- 2026-10-16: 67
- 2026-10-15: 66
- 2026-10-14: 66
- 2026-10-13: 65
- 2026-10-12: 65
- 2026-10-10: 64
- 2026-10-04: 61
- 2026-10-03: 61

## Common questions

### What is the Zelta Protein Per Day MCP server?

Zelta Protein Per Day is an MCP server listed in the public MCP registry as in.zelta/protein-target. Daily protein need by weight and goal, with a sample Indian food plan to hit it. This page covers its hosted endpoint (https://protein-mcp.zelta.in/mcp).

### Is the Zelta Protein Per Day MCP server safe to use?

Zelta Protein Per Day scores 75 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 Protein Per Day MCP server expose?

Zelta Protein Per Day exposes 2 tools: protein_per_day, protein_food_plan. Their descriptions and schemas cost roughly 267 tokens of context every time the server is loaded.

### Does the Zelta Protein Per Day MCP server require authentication?

No. We connected to Zelta Protein Per Day without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zelta Protein Per Day MCP server still maintained?

Zelta Protein Per Day is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://protein-mcp.zelta.in/mcp
- Website: https://zelta.in/tools/
- Changelog RSS feed: https://verifymcp.io/servers/in-zelta-protein-target/protein-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/in-zelta-protein-target/protein-mcp.json
- HTML version of this page: https://verifymcp.io/servers/in-zelta-protein-target/protein-mcp
