Sunrise & Sunset Times
REMOTE · API.SUNRISE-SUNSET.ORG
Sunrise, sunset, twilight, golden hour and moon times for any place on Earth. Free, no API key.
Available components
Last scanned (18 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 499 tokens (~249/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_sun_times” rewrote its description, which is the text the model reads security
- Tool “get_sun_times_range” rewrote its description, which is the text the model reads security
- Schema quality: 279 → 249 ▲ functional
- MCP protocol: fail → pass ▲ functional
- Tool “get_sun_times” now declares an output schema ▲ functional
- Tool “get_sun_times_range” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.0.0 → 1.1.0 functional
- 15 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://api.sunrise-sunset.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sunrise-sunset.org | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 90e74aed7a5d000c13e17457d6d8462a |
| SANs: sunrise-sunset.org, *.sunrise-sunset.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.sunrise-sunset.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| sunrise-sunset.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.sunrise-sunset.org/mcp | Verified | 200 | |
| http (plaintext) | http://api.sunrise-sunset.org/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_sun_times Sunrise & sunset times ~200
Sunrise, sunset, solar noon, day length, civil/nautical/astronomical twilight, dawn/dusk, first/last light, golden hour, blue hour, sunrise/sunset azimuth, solar noon altitude, moonrise/moonset, moon phase and illumination for any coordinates on Earth and any date. Times are ISO 8601 in the local timezone of the location. Polar day/night handled via sun_status (normal | midnight_sun | polar_night); events that do not occur are null.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | 'today' (default), 'tomorrow' or YYYY-MM-DD. Relative dates resolve in the local timezone of the coordinates. |
| lat | number | yes | Latitude in decimal degrees. |
| lng | number | yes | Longitude in decimal degrees. |
| tz | string | – | IANA timezone like 'Europe/Madrid'. Omit to use the local timezone of the coordinates, resolved automatically (recommended). |
| Name | Type | Req | Description |
|---|---|---|---|
| astronomical_twilight_begin | string|null | yes | Start of astronomical twilight, ISO 8601 with the local UTC offset; null if it does not happen that day. |
| astronomical_twilight_end | string|null | yes | End of astronomical twilight, ISO 8601 with the local UTC offset; null if it does not happen that day. |
| attribution | string | – | – |
| blue_hour | object | yes | – |
| civil_twilight_begin | string|null | yes | Start of civil twilight, ISO 8601 with the local UTC offset; null if it does not happen that day. |
| civil_twilight_end | string|null | yes | End of civil twilight, ISO 8601 with the local UTC offset; null if it does not happen that day. |
| date | string | yes | Local date, YYYY-MM-DD. |
| dawn | string|null | yes | Dawn (start of civil twilight), ISO 8601 with the local UTC offset; null if it does not happen that day. |
| day_length | integer|null | yes | Seconds of daylight: 86400 with midnight sun, 0 with polar night, null on a day with only one of sunrise/sunset. |
| dusk | string|null | yes | Dusk (end of civil twilight), ISO 8601 with the local UTC offset; null if it does not happen that day. |
| first_light | string|null | yes | First light (start of astronomical twilight), ISO 8601 with the local UTC offset; null if it does not happen that day. |
| golden_hour | object | yes | – |
| last_light | string|null | yes | Last light (end of astronomical twilight), ISO 8601 with the local UTC offset; null if it does not happen that day. |
| lat | number | yes | – |
| lng | number | yes | – |
| moon_illumination | number | yes | Illuminated fraction of the moon at local noon, in percent (0-100). |
| moon_phase | string | yes | Moon phase at local noon. |
| moonrise | string|null | yes | Moonrise, ISO 8601 with the local UTC offset; null if it does not happen that day. |
| moonset | string|null | yes | Moonset, ISO 8601 with the local UTC offset; null if it does not happen that day. |
| nautical_twilight_begin | string|null | yes | Start of nautical twilight, ISO 8601 with the local UTC offset; null if it does not happen that day. |
| nautical_twilight_end | string|null | yes | End of nautical twilight, ISO 8601 with the local UTC offset; null if it does not happen that day. |
| solar_noon | string|null | yes | Solar noon, ISO 8601 with the local UTC offset; null if it does not happen that day. |
| solar_position | object | yes | – |
| sun_status | string | yes | – |
| sunrise | string|null | yes | Sunrise, ISO 8601 with the local UTC offset; null if it does not happen that day. |
| sunset | string|null | yes | Sunset, ISO 8601 with the local UTC offset; null if it does not happen that day. |
| tzid | string | yes | IANA timezone used. |
| utc_offset | string | yes | UTC offset of the location at local noon, like +02:00. |
No examples provided.
get_sun_times_range Sunrise & sunset times for a date range ~223
Same per-day data as get_sun_times but for an inclusive date range (up to 366 days) in a single call. Use this instead of repeated get_sun_times calls when you need several consecutive days. The days array may contain fewer entries than the number of dates requested: calendar days that never existed in that timezone (Samoa skipped 30 December 2011 when it crossed the date line) are left out, so read each entry's date field instead of assuming one per requested date.
| Name | Type | Req | Description |
|---|---|---|---|
| date_end | string | yes | Last day (inclusive), YYYY-MM-DD. The range covers at most 366 days counting both ends, so date_end can be at most 365 days after date_start. |
| date_start | string | yes | First day, YYYY-MM-DD. |
| lat | number | yes | Latitude in decimal degrees. |
| lng | number | yes | Longitude in decimal degrees. |
| tz | string | – | IANA timezone like 'Europe/Madrid'. Omit to use the local timezone of the coordinates, resolved automatically (recommended). |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | – |
| days | array | yes | One entry per local day that exists in that timezone, in order; match entries by their date field. |
| lat | number | yes | – |
| lng | number | yes | – |
| tzid | string | yes | IANA timezone used. |
No examples provided.
How do I install the Sunrise & Sunset Times MCP server?
Sunrise & Sunset Times is a hosted endpoint at https://api.sunrise-sunset.org/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.
remote · api.sunrise-sunset.org
claude mcp add --transport http org-sunrise-sunset-sun-times 'https://api.sunrise-sunset.org/mcp'
What is the Sunrise & Sunset Times MCP server?
Sunrise & Sunset Times is an MCP server listed in the public MCP registry as org.sunrise-sunset/sun-times. Sunrise, sunset, twilight, golden hour and moon times for any place on Earth. Free, no API key. This page covers its hosted endpoint (https://api.sunrise-sunset.org/mcp).
Is the Sunrise & Sunset Times MCP server safe to use?
Sunrise & Sunset Times scores 67 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 Sunrise & Sunset Times MCP server expose?
Sunrise & Sunset Times exposes 2 tools: get_sun_times, get_sun_times_range. Their descriptions and schemas cost roughly 423 tokens of context every time the server is loaded.
Does the Sunrise & Sunset Times MCP server require authentication?
No. We connected to Sunrise & Sunset Times without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sunrise & Sunset Times MCP server still maintained?
Sunrise & Sunset Times is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.