MCP.Market

Vitamind MCP server

online · 79% uptime
by JaviMaligno·io.github.JaviMaligno/vitamind·v1.0.0·1 stars
No reviews yet

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

A97/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

1 stars

Reviews

Write one

Nobody has reviewed Vitamind yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vitamind tools (15, 1 write)

write = sends, deletes, buys or posts
  • compare_vitamin_d_yearFree

    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.

  • configure_sun_profileFree

    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.

  • estimate_sun_sessionFree

    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.

  • get_current_statusFree

    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.

  • get_my_citiesFree

    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).

  • get_my_historyFree

    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.

  • get_my_profileFree

    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_sun_forecastFree

    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.

  • get_sun_timesFree

    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.

  • get_vitamin_d_windowFree

    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.

  • get_vitamin_d_yearFree

    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.

  • log_sun_sessionFree

    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).

  • search_cityFree

    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.

  • set_history_locationFree

    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).

  • update_my_profilewrite actionFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1381ms20/20
  • Tool poisoning15 tool descriptions checked15/15
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Vitamind compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,255 servers
Tools
15
the typical server has 7
Tools that change things
7%
typical: 0%. Fewer write tools means less an agent can break
Uptime
79%
of our recent checks; the typical remote server answers 100%
Response time
290 ms
faster than 49% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers

What its tools let an agent do: 13 read · 2 change

Install Vitamind in Claude Code, Cursor or VS Code

claude mcp add --transport http vitamind https://getvitamind.app/api/mcp/mcp
Add to Cursor

What the publisher says

From the Vitamind repository's README, as published. We do not edit it. Read it on GitHub

VitaminD Explorer

Solar vitamin D calculator PWA — know when and where you can synthesize vitamin D from sunlight, based on solar elevation, real-time UV index, skin type, body exposure and age.

Live: https://getvitamind.app

Stack

Next.js (App Router) · next-intl (es/en/fr/de/ru/lt) · Tailwind CSS v4 · D3 · Supabase (auth, profiles, city search, push subscriptions) · Web Push · Vercel (hosting + daily cron).

Development

npm install
cp .env.example .env.local   # fill in values
npm run dev                  # localhost:3000

Quality gate (all must pass, enforced by CI on every push/PR):

npm run lint && npm run typecheck && npm test && npm run build

Docs

gotchas and incident history.

  • CLAUDE.md — architecture, deployment runbook, operational

production-readiness assessment and the practices that keep it that way.

  • docs/PRODUCTION_READINESS.md —

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Vitamind: common questions

Is Vitamind MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Vitamind safety report
How do I install Vitamind?
It runs remotely at getvitamind.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Vitamind need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Vitamind maintained?
The last commit was 8 days ago (2026-10-27). The latest release is v1.0.0.
Is Vitamind up?
79% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Vitamind compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,255 servers); tools 15 (the typical server has 7); tools that change things 7% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.