Sunset Score

Plan sunrise and sunset shoots

Plan sunrise and sunset photography with visual quality forecasts from Sunset Score. Choose a destination such as Chicago, provide coordinates, or ask about the approximate location shared by your client.

What you can ask

How promising are the sunrises and sunsets in Chicago over the next three days?
Example path

MCP connector

Server URL: https://api.sunset-score.com/mcp/chatgpt
Login: None
Protocol: MCP 2026-07-28
Instructions: Sunrise/sunset beauty forecasts. Scores measure visual quality, not probability or a guarantee. One location, 1–3 local calendar days; event timestamps are UTC. Local days start today, or tomorrow after both events have passed. Empty results can occur in polar conditions or when weather is unavailable. Shared with REST: 900 requests/day, 60/network/day, 15/network/minute, one forecast at a time. Accepted failures count. Respect retryAfterSeconds; never retry immediately or bypass limits. No production SLA. Documentation: https://sunset-score.com/api/ Use for near-me requests with client-provided approximate location. Use for a destination explicitly chosen by the user: supplied coordinates, or an approximate city/public-place center resolved by the assistant. State the chosen place and approximate scope; clarify ambiguous place names. Explicit destinations take precedence over device location. Do not infer personal location from chat history or ask for a home address or precise device GPS. If local metadata is unavailable, explain that near-me forecasting is unavailable; a user may instead choose a public destination. No historical dates, alerts or subscriptions.

Tools

Reads data2

Skills

None in the store listings or on the server

MCP connector

Server URL

https://api.sunset-score.com/mcp/chatgpt

None

Protocol

MCP 2026-07-28

Instructions

Sunrise/sunset beauty forecasts. Scores measure visual quality, not probability or a guarantee. One location, 1–3 local calendar days; event timestamps are UTC. Local days start today, or tomorrow after both events have passed. Empty results can occur in polar conditions or when weather is unavailable. Shared with REST: 900 requests/day, 60/network/day, 15/network/minute, one forecast at a time. Accepted failures count. Respect retryAfterSeconds; never retry immediately or bypass limits. No production SLA. Documentation: https://sunset-score.com/api/ Use for near-me requests with client-provided approximate location. Use for a destination explicitly chosen by the user: supplied coordinates, or an approximate city/public-place center resolved by the assistant. State the chosen place and approximate scope; clarify ambiguous place names. Explicit destinations take precedence over device location. Do not infer personal location from chat history or ask for a home address or precise device GPS. If local metadata is unavailable, explain that near-me forecasting is unavailable; a user may instead choose a public destination. No historical dates, alerts or subscriptions.