Remote MCP · Endpoint
D Fetcher MCP server
No. D Fetcher answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://dfetcher.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.dfetcher/vitamin-d
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 268 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Vitamin D synthesis calculator: sun position, UV, IU/min, time to dose, sunburn risk, daily window.
- Website
- https://dfetcher.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 268 ms |
| 18 hours ago | Handshake completed | 85 ms |
| 2 days ago | Handshake completed | 104 ms |
| 3 days ago | Handshake completed | 90 ms |
| 4 days ago | Handshake completed | 68 ms |
| 5 days ago | Handshake completed | 155 ms |
| 6 days ago | Handshake completed | 161 ms |
| 7 days ago | Handshake completed | 318 ms |
| 10 days ago | Handshake completed | 85 ms |
| 13 days ago | Handshake completed | 531 ms |
| 15 days ago | Handshake completed | 88 ms |
| 17 days ago | Handshake completed | 136 ms |
| 19 days ago | Handshake completed | 123 ms |
| 21 days ago | Handshake completed | 76 ms |
| 23 days ago | Handshake completed | 96 ms |
| 25 days ago | Handshake completed | 80 ms |
| 27 days ago | Handshake completed | 124 ms |
| 28 days ago | Handshake completed | 119 ms |
| 29 days ago | Handshake completed | 330 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with D Fetcher and makes no claim about it beyond what these checks measured.