# io.github.JaviMaligno/vitamind (remote · getvitamind.app)

Know when the sun can make vitamin D where you are, for your skin type. Live UV data.

- Trust score: 70/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `getvitamind.app`: 38/100, [markdown](https://verifymcp.io/servers/javimaligno-vitamind/api-mcp-auth-mcp.md), [page](https://verifymcp.io/servers/javimaligno-vitamind/api-mcp-auth-mcp)
- remote · `getvitamind.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/javimaligno-vitamind/api-mcp-mcp.md), [page](https://verifymcp.io/servers/javimaligno-vitamind/api-mcp-mcp)

## Channel facts

- Endpoint: `https://getvitamind.app/api/mcp/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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3089 tokens (~154/item across 20 items; 15 tools + 5 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http javimaligno-vitamind https://getvitamind.app/api/mcp/mcp
```

### Codex

```toml
[mcp_servers.javimaligno-vitamind]
url = "https://getvitamind.app/api/mcp/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "javimaligno-vitamind": {
      "type": "remote",
      "url": "https://getvitamind.app/api/mcp/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add javimaligno-vitamind --url https://getvitamind.app/api/mcp/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  javimaligno-vitamind:
    url: "https://getvitamind.app/api/mcp/mcp"
```

### Other

```json
{
  "mcpServers": {
    "javimaligno-vitamind": {
      "type": "http",
      "url": "https://getvitamind.app/api/mcp/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-08-03 (score 70, 0)

- [security] Tool “get_my_history” rewrote its description, which is the text the model reads
- [functional] New tool “set_history_location”

### 2026-08-02 (score 70, +1)

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

### 2026-08-01 (score 69, 0)

- [functional regression] Schema quality: 2534 → 2860
- [functional] New resource “Sun forecast”
- [functional] New tool “get_sun_forecast”

### 2026-07-31 (score 69, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, +1)

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

### 2026-07-29 (score 65, +1)

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

### 2026-07-28 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 64)

First indexed and scored.

## MCP tools (15)

### `search_city` (~68 tokens)

Find a city in the app's database by name (any of the app's six languages works) and get its coordinates, IANA timezone and elevation — feed those into the other tools.

Input parameters:

- `query` (string, required): City name, e.g. 'Madrid', 'London', 'Nueva York'

### `get_sun_times` (~130 tokens)

Sunrise, sunset, solar noon, civil dawn/dusk, morning AND evening golden hour, and day length (with day-over-day trend) for a location and date. Handles midnight sun and polar night. Pure sun times — for vitamin D questions use the vitamin_d tools instead.

Input parameters:

- `date` (string): Date as YYYY-MM-DD; defaults to today
- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees
- `timezone` (string): IANA timezone like 'Europe/Madrid'. Strongly recommended — without it all times are UTC

### `get_vitamin_d_window` (~353 tokens)

The solar vitamin D synthesis window for ONE specific day at a location, for a personal profile: when UV is strong enough (index ≥ 3), the best hour, the clear-sky minutes needed to reach the target IU, and (with atTime) the minutes at the specific hour the user plans to go out. Returns synthesisPossible=false when the sun never gets high enough that day. Only for single-day questions — for months, seasons or 'when during the year', call get_vitamin_d_year instead of calling this once per date.

Input parameters:

- `age` (number): Age in years (synthesis declines with age); omit for adult baseline
- `atTime` (string): Local HH:MM the user plans to go out — adds minutesNeeded and UV at that exact time
- `date` (string): Date as YYYY-MM-DD; defaults to today
- `elevationM` (number): Ground elevation in metres (UV rises ~8%/km); default sea level
- `exposedSkinFraction` (number): Skin exposed: 0.10 face+hands, 0.18 face+arms, 0.25 t-shirt+shorts (default), 0.40 swimsuit
- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees
- `skinType` (integer): Fitzpatrick skin type 1 (very fair) to 6 (very dark); default 3
- `targetIU` (number): Vitamin D target per session in IU; default 1000
- `timezone` (string): IANA timezone like 'Europe/Madrid'. Strongly recommended — without it all times are UTC

### `get_vitamin_d_year` (~331 tokens)

The WHOLE YEAR of solar vitamin D for a location in a single call. monthsWithSun lists every month with at least one viable day (season edges count as partial months, see byMonth[].viableDays); solidMonths lists months where most days work; exactViableSpan gives the exact season boundaries; summary carries per-year aggregates for comparing places. Use this for any question about months, seasons, winter/summer or 'when during the year can I…' — never probe individual dates with get_vitamin_d_window for that.

Input parameters:

- `age` (number): Age in years (synthesis declines with age); omit for adult baseline
- `elevationM` (number): Ground elevation in metres (UV rises ~8%/km); default sea level
- `exposedSkinFraction` (number): Skin exposed: 0.10 face+hands, 0.18 face+arms, 0.25 t-shirt+shorts (default), 0.40 swimsuit
- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees
- `placeName` (string): The place's name as the user said it — used to caption the chart
- `skinType` (integer): Fitzpatrick skin type 1 (very fair) to 6 (very dark); default 3
- `targetIU` (number): Vitamin D target per session in IU; default 1000
- `timezone` (string): IANA timezone like 'Europe/Madrid'. Strongly recommended — without it all times are UTC

### `configure_sun_profile` (~288 tokens)

Show the user an interactive form for the four values every other tool assumes — Fitzpatrick skin type, fraction of skin exposed, age and target IU — with the minutes they need updating live. Use this when those values are unknown, when the user wants to change them, or instead of asking for them one at a time in conversation. Whatever the user picks comes back into the conversation; pass those values explicitly to the other tools afterwards.

Input parameters:

- `age` (number): Age in years (synthesis declines with age); omit for adult baseline
- `exposedSkinFraction` (number): Skin exposed: 0.10 face+hands, 0.18 face+arms, 0.25 t-shirt+shorts (default), 0.40 swimsuit
- `lat` (number): Latitude of the place being discussed, so the live estimate uses today's real UV there
- `lon` (number): Longitude, paired with lat
- `placeName` (string): How to label that place in the widget
- `skinType` (integer): Fitzpatrick skin type 1 (very fair) to 6 (very dark); default 3
- `targetIU` (number): Vitamin D target per session in IU; default 1000
- `timezone` (string): IANA timezone like 'Europe/Madrid'. Strongly recommended — without it all times are UTC

### `get_sun_forecast` (~309 tokens)

The NEXT FEW DAYS of vitamin D sun at a location, using the live Open-Meteo forecast: per day the peak UV, average cloud cover, the synthesis window and the minutes needed, plus bestDay. Use this for any question spanning several days — 'which day this week should I go out', 'will it be better tomorrow', 'when's my next chance' — instead of calling get_vitamin_d_window once per date.

Input parameters:

- `age` (number): Age in years (synthesis declines with age); omit for adult baseline
- `days` (integer): How many days ahead, 2 to 7; default 5
- `elevationM` (number): Ground elevation in metres (UV rises ~8%/km); default sea level
- `exposedSkinFraction` (number): Skin exposed: 0.10 face+hands, 0.18 face+arms, 0.25 t-shirt+shorts (default), 0.40 swimsuit
- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees
- `skinType` (integer): Fitzpatrick skin type 1 (very fair) to 6 (very dark); default 3
- `targetIU` (number): Vitamin D target per session in IU; default 1000
- `timezone` (string): IANA timezone like 'Europe/Madrid'. Strongly recommended — without it all times are UTC

### `compare_vitamin_d_year` (~229 tokens)

Compare the vitamin D year of 2 to 5 places side by side in ONE call — 'Madrid vs Berlin vs Oslo, where do I actually get winter sun?'. Returns each place's months with sun, exact season span and viable days per year, plus rankedByViableDays. Use this instead of calling get_vitamin_d_year once per city: only this tool can draw the years on a shared axis.

Input parameters:

- `age` (number): Age in years (synthesis declines with age); omit for adult baseline
- `exposedSkinFraction` (number): Skin exposed: 0.10 face+hands, 0.18 face+arms, 0.25 t-shirt+shorts (default), 0.40 swimsuit
- `places` (array, required): The places to compare, 2 to 5
- `skinType` (integer): Fitzpatrick skin type 1 (very fair) to 6 (very dark); default 3
- `targetIU` (number): Vitamin D target per session in IU; default 1000

### `get_current_status` (~244 tokens)

Whether RIGHT NOW is a good moment for vitamin D synthesis at a location, using live Open-Meteo UV/cloud data when reachable (clear-sky model otherwise): current UV index, minutes needed now, and when today's window opens or closes.

Input parameters:

- `age` (number): Age in years (synthesis declines with age); omit for adult baseline
- `elevationM` (number): Ground elevation in metres (UV rises ~8%/km); default sea level
- `exposedSkinFraction` (number): Skin exposed: 0.10 face+hands, 0.18 face+arms, 0.25 t-shirt+shorts (default), 0.40 swimsuit
- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees
- `skinType` (integer): Fitzpatrick skin type 1 (very fair) to 6 (very dark); default 3
- `targetIU` (number): Vitamin D target per session in IU; default 1000
- `timezone` (string): IANA timezone like 'Europe/Madrid'. Strongly recommended — without it all times are UTC

### `estimate_sun_session` (~327 tokens)

Estimate a sun session's outcome: 'I was (or will be) out N minutes — how much vitamin D did I make?' plus 'how long before I'd burn?' for the profile. Takes a start time (defaults to the day's best hour) and session minutes; returns estimated IU (with the physiological cap), average UV and clear-sky minutes-to-sunburn. Use for any 'how much did I get / can I get in X minutes' or 'how long without burning' question.

Input parameters:

- `age` (number): Age in years (synthesis declines with age); omit for adult baseline
- `date` (string): Date as YYYY-MM-DD; defaults to today
- `elevationM` (number): Ground elevation in metres (UV rises ~8%/km); default sea level
- `exposedSkinFraction` (number): Skin exposed: 0.10 face+hands, 0.18 face+arms, 0.25 t-shirt+shorts (default), 0.40 swimsuit
- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees
- `minutes` (number, required): Session length in minutes
- `skinType` (integer): Fitzpatrick skin type 1 (very fair) to 6 (very dark); default 3
- `startTime` (string): Local HH:MM the session starts; defaults to the day's best hour
- `timezone` (string): IANA timezone like 'Europe/Madrid'. Strongly recommended — without it all times are UTC

### `get_my_profile` (~67 tokens)

The signed-in user's saved Vitamin D profile: skin type, exposed-skin default, age, target IU and their current city. Requires connecting with OAuth (scope profile:read). Call this FIRST for any personal question, then pass its values to the public tools instead of asking the user.

### `get_my_cities` (~41 tokens)

The signed-in user's current city and favorite cities with coordinates and timezones, ready to feed into the public tools. Requires OAuth (scope profile:read).

### `update_my_profile` (~175 tokens)

Save the signed-in user's synthesis profile — skin type, exposed-skin fraction, age and target IU — to their account, so the app and every later call use them. Requires OAuth (scope profile:write). Only these four values are writable; favourites, cities and history are not.

Input parameters:

- `age`: Age in years, or null for the adult baseline
- `exposedSkinFraction` (number): Skin exposed: 0.10 face+hands, 0.18 face+arms, 0.25 t-shirt+shorts (default), 0.40 swimsuit
- `skinType` (integer): Fitzpatrick skin type 1 (very fair) to 6 (very dark); default 3
- `targetIU` (number): Vitamin D target per session in IU; default 1000

### `get_my_history` (~120 tokens)

The signed-in user's sun history from the app's calendar: which recent days had viable sun, which they confirmed going outside, and their current streak. Covers the calendar days from `from` to `to`; records exist only for days the app was open, so a date missing from `records` means nothing was measured, not that the sun was insufficient. Requires OAuth (scope history:read). Renders as a calendar the user can tap to confirm a day.

Input parameters:

- `days` (integer): How many recent days to return; default 30

### `log_sun_session` (~133 tokens)

Sets a day's answer in the signed-in user's history calendar. Three values: confirmed=true (went out, the default), confirmed=false (had usable sun but stayed in), confirmed=null (clear the answer). Defaults to today. Requires OAuth (scope history:write).

Input parameters:

- `confirmed` (boolean|null): true (default) the user went out; false they had sun but stayed in; null clears the answer
- `date` (string): Day to set, YYYY-MM-DD; defaults to today
- `minutes` (number): Minutes the user reports having spent in the sun (acknowledged, not stored)

### `set_history_location` (~187 tokens)

Records where the signed-in user was over a range of past days, so their history stops assuming. Use it when the user corrects a stretch — get_my_history marks inherited days with `locationAssumed`, and the history calendar offers those stretches for correction. Pass a cityId from search_city, or lat/lon. Changes only the location: whether they went outside that day is untouched. Requires OAuth (scope history:write).

Input parameters:

- `cityId` (string): City id from search_city, e.g. 'builtin:londres'
- `from` (string, required): First day of the stretch, YYYY-MM-DD
- `lat` (number): Latitude, for a place not in the database
- `lon` (number): Longitude, paired with lat
- `to` (string, required): Last day of the stretch, YYYY-MM-DD; same as `from` for one day

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/javimaligno-vitamind/api-mcp-mcp#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 70
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 66
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 64

## Links

- Remote endpoint: https://getvitamind.app/api/mcp/mcp
- Repository: https://github.com/JaviMaligno/vitamind
- Website: https://getvitamind.app/connect
- Changelog RSS feed: https://verifymcp.io/servers/javimaligno-vitamind/api-mcp-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/javimaligno-vitamind/api-mcp-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/javimaligno-vitamind/api-mcp-mcp