Skip to content

D Fetcher

Estimates minutes of sun exposure needed for a target vitamin D dose, using solar geometry, a UV forecast feed and a skin-type model.

Maintained

At a glanceswept Oct 22, 2026

not read yet

Use

For
People wanting to estimate daily sun time for vitamin D while avoiding sunburn
Activity
Maintainedrelease 5 months ago · site updated 5 months ago
Used for
  • estimate minutes of sun needed for daily vitamin D
  • check sunburn risk for current local conditions
  • plan outdoor timing by hour and season
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 24, 2026
  • MCP servercom.dfetcher/vitamin-dverified in the MCP registry
  • Stateanswers, 3 toolschecked 2026-10-24
  • Address to connectdfetcher.com/mcp
  • API docsdfetcher.com/apithe vendor's page ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Most used in Securityby use, among tools still maintained — this tool shares no tags yet

Figure and bar: visits/mo, estimate · year: online since

Compare D Fetcher with

Pick up to two.

All 10 alternatives to D Fetcher →

All Security tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use D Fetcher for?

Sign in to leave a note
Questions this page answers
  • What is D Fetcher?

    Estimates minutes of sun exposure needed for a target vitamin D dose, using solar geometry, a UV forecast feed and a skin-type model. It is listed in the Atlas under Security.

  • Who is D Fetcher for?

    People wanting to estimate daily sun time for vitamin D while avoiding sunburn

  • Do people use D Fetcher?

    Little sign of use.

  • Is D Fetcher still maintained?

    Maintained: release 5 months ago · site updated 5 months ago.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk