Sunvane Golden Hour
REMOTE · GOLDEN-HOUR.ZOVO.ONE
Sun times & shoot planning
Available components
Last scanned (22 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 22 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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 819 tokens (~204/item across 4 items; 3 tools + 1 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 22 Oct 26 74
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 22 Oct 2026 · Probed https://golden-hour.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a02831e2e6efce24131c4d7c96c4f8e1 |
| SANs: zovo.one, golden-hour.zovo.one, *.golden-hour.zovo.one | ||||||
| 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 golden-hour.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://golden-hour.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://golden-hour.zovo.one/mcp | HTTPS enforced | 301 | https://golden-hour.zovo.one/mcp |
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 →
compare_day_length Compare day length ~272
Use this when the user asks for day length differences and average change per day between two local dates, or the solstices and equinoxes of a year. Returns daylight duration for each date and signed changes. Limits: cities with population 50,000+ (plus Tromso), dates/years 1900–2100, flat sea-level horizon; use either date_a and date_b or year, and not both. Does not forecast weather.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name, for example New York. Cities with population 50,000+ are supported; the largest same-name match is used. |
| country | string | – | Optional country name or two-letter code to narrow the match, for example US. |
| date_a | string | – | First local date for a two-date comparison, for example 2026-03-20. Required with date_b; omit with year. |
| date_b | string | – | Second local date, for example 2026-06-21. Required with date_a; omit with year. |
| state | string | – | Optional US state name or abbreviation, for example NY or New York. |
| year | integer | – | Year whose equinox and solstice local dates to compare, for example 2026. Omit date_a/date_b. |
| Name | Type | Req | Description |
|---|---|---|---|
| astronomical | – | – | – |
| blue | array | – | – |
| changes | array | – | – |
| civil | – | – | – |
| date | string | – | – |
| dayLength | string | – | – |
| dayLengthSeconds | number | – | – |
| dayStatus | string | – | – |
| days | number | – | – |
| definitions | string | yes | – |
| downloads | object | – | – |
| eventCount | number | – | – |
| golden | array | – | – |
| limitations | string | yes | – |
| location | object | yes | – |
| mode | string | yes | – |
| nautical | – | – | – |
| period | string | – | – |
| preview | array | – | – |
| request | object | yes | – |
| solarNoon | – | – | – |
| startDate | string | – | – |
| sunrise | – | – | – |
| sunriseAzimuth | number|null | – | – |
| sunset | – | – | – |
| sunsetAzimuth | number|null | – | – |
| timeZone | string | – | – |
| values | array | – | – |
No examples provided.
find_sun_times Find sun times ~220
Use this when the user asks for a golden hour calculator, golden hour time, sunrise sunset times, sunset time today, what time is golden hour, blue hour, sunrise time, or twilight times for a city and local date. Returns local sunrise, sunset, solar noon, day length, twilight, light windows and sun azimuth. Limits: cities with population 50,000+ (plus Tromso), dates 1900–2100, flat sea-level horizon; Does not model weather or terrain.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name, for example New York. Cities with population 50,000+ are supported; the largest same-name match is used. |
| country | string | – | Optional country name or two-letter code to narrow the match, for example US. |
| date | string | yes | Local calendar date, YYYY-MM-DD, from 1900 to 2100; for example 2026-06-21. |
| state | string | – | Optional US state name or abbreviation, for example NY or New York. |
| Name | Type | Req | Description |
|---|---|---|---|
| astronomical | – | – | – |
| blue | array | – | – |
| changes | array | – | – |
| civil | – | – | – |
| date | string | – | – |
| dayLength | string | – | – |
| dayLengthSeconds | number | – | – |
| dayStatus | string | – | – |
| days | number | – | – |
| definitions | string | yes | – |
| downloads | object | – | – |
| eventCount | number | – | – |
| golden | array | – | – |
| limitations | string | yes | – |
| location | object | yes | – |
| mode | string | yes | – |
| nautical | – | – | – |
| period | string | – | – |
| preview | array | – | – |
| request | object | yes | – |
| solarNoon | – | – | – |
| startDate | string | – | – |
| sunrise | – | – | – |
| sunriseAzimuth | number|null | – | – |
| sunset | – | – | – |
| sunsetAzimuth | number|null | – | – |
| timeZone | string | – | – |
| values | array | – | – |
No examples provided.
plan_golden_hour_shoot Plan golden hour shoot ~248
Use this when the user wants photography golden hour shoot windows for a city and a date range, with an ICS calendar file and CSV table. Choose morning, evening or both. Limits: 1–31 days, cities with population 50,000+ (plus Tromso), years 1900–2100, flat sea-level horizon; missing polar windows are reported and calendar events are only included for existing windows. Does not access or change a calendar.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name, for example New York. Cities with population 50,000+ are supported; the largest same-name match is used. |
| country | string | – | Optional country name or two-letter code to narrow the match, for example US. |
| days | integer | yes | Number of consecutive days, 1 to 31, for example 7. |
| period | string | yes | Light windows to include, for example evening. A continuous window includes both periods. |
| start_date | string | yes | First local date in YYYY-MM-DD, for example 2026-10-12. |
| state | string | – | Optional US state name or abbreviation, for example NY or New York. |
| Name | Type | Req | Description |
|---|---|---|---|
| astronomical | – | – | – |
| blue | array | – | – |
| changes | array | – | – |
| civil | – | – | – |
| date | string | – | – |
| dayLength | string | – | – |
| dayLengthSeconds | number | – | – |
| dayStatus | string | – | – |
| days | number | – | – |
| definitions | string | yes | – |
| downloads | object | – | – |
| eventCount | number | – | – |
| golden | array | – | – |
| limitations | string | yes | – |
| location | object | yes | – |
| mode | string | yes | – |
| nautical | – | – | – |
| period | string | – | – |
| preview | array | – | – |
| request | object | yes | – |
| solarNoon | – | – | – |
| startDate | string | – | – |
| sunrise | – | – | – |
| sunriseAzimuth | number|null | – | – |
| sunset | – | – | – |
| sunsetAzimuth | number|null | – | – |
| timeZone | string | – | – |
| values | array | – | – |
No examples provided.
How do I install the Sunvane Golden Hour MCP server?
Sunvane Golden Hour is a hosted endpoint at https://golden-hour.zovo.one/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 · golden-hour.zovo.one
claude mcp add --transport http theluckystrike-golden-hour 'https://golden-hour.zovo.one/mcp'
What is the Sunvane Golden Hour MCP server?
Sunvane Golden Hour is an MCP server listed in the public MCP registry as io.github.theluckystrike/golden-hour. Sun times & shoot planning. This page covers its hosted endpoint (https://golden-hour.zovo.one/mcp).
Is the Sunvane Golden Hour MCP server safe to use?
Sunvane Golden Hour scores 74 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 Sunvane Golden Hour MCP server expose?
Sunvane Golden Hour exposes 3 tools: find_sun_times, plan_golden_hour_shoot, compare_day_length. Their descriptions and schemas cost roughly 740 tokens of context every time the server is loaded.
Does the Sunvane Golden Hour MCP server require authentication?
No. We connected to Sunvane Golden Hour without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sunvane Golden Hour MCP server still maintained?
Sunvane Golden Hour is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.