# Sunvane Golden Hour (remote · golden-hour.zovo.one)

Sun times & shoot planning

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `golden-hour.zovo.one`: 74/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-golden-hour/golden-hour.md), [page](https://verifymcp.io/servers/theluckystrike-golden-hour/golden-hour)

## Channel facts

- Endpoint: `https://golden-hour.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-golden-hour 'https://golden-hour.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-golden-hour": {
      "url": "https://golden-hour.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-golden-hour": {
      "type": "http",
      "url": "https://golden-hour.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-golden-hour]
url = "https://golden-hour.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-golden-hour": {
      "type": "remote",
      "url": "https://golden-hour.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-golden-hour --url 'https://golden-hour.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-golden-hour:
    url: "https://golden-hour.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-golden-hour": {
      "Transport": "http",
      "Url": "https://golden-hour.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-golden-hour -t streamable-http -u 'https://golden-hour.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-golden-hour": {
      "type": "http",
      "url": "https://golden-hour.zovo.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 74)

First indexed and scored.

## MCP tools (3)

### `find_sun_times` (~220 tokens)

Find sun times

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.

Input parameters:

- `city` (string, required): 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, required): 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.

Output parameters:

- `astronomical`
- `blue` (array)
- `changes` (array)
- `civil`
- `date` (string)
- `dayLength` (string)
- `dayLengthSeconds` (number)
- `dayStatus` (string)
- `days` (number)
- `definitions` (string)
- `downloads` (object)
- `eventCount` (number)
- `golden` (array)
- `limitations` (string)
- `location` (object)
- `mode` (string)
- `nautical`
- `period` (string)
- `preview` (array)
- `request` (object)
- `solarNoon`
- `startDate` (string)
- `sunrise`
- `sunriseAzimuth` (number|null)
- `sunset`
- `sunsetAzimuth` (number|null)
- `timeZone` (string)
- `values` (array)

### `plan_golden_hour_shoot` (~248 tokens)

Plan golden hour shoot

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.

Input parameters:

- `city` (string, required): 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, required): Number of consecutive days, 1 to 31, for example 7.
- `period` (string, required): Light windows to include, for example evening. A continuous window includes both periods.
- `start_date` (string, required): 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.

Output parameters:

- `astronomical`
- `blue` (array)
- `changes` (array)
- `civil`
- `date` (string)
- `dayLength` (string)
- `dayLengthSeconds` (number)
- `dayStatus` (string)
- `days` (number)
- `definitions` (string)
- `downloads` (object)
- `eventCount` (number)
- `golden` (array)
- `limitations` (string)
- `location` (object)
- `mode` (string)
- `nautical`
- `period` (string)
- `preview` (array)
- `request` (object)
- `solarNoon`
- `startDate` (string)
- `sunrise`
- `sunriseAzimuth` (number|null)
- `sunset`
- `sunsetAzimuth` (number|null)
- `timeZone` (string)
- `values` (array)

### `compare_day_length` (~272 tokens)

Compare day length

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.

Input parameters:

- `city` (string, required): 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.

Output parameters:

- `astronomical`
- `blue` (array)
- `changes` (array)
- `civil`
- `date` (string)
- `dayLength` (string)
- `dayLengthSeconds` (number)
- `dayStatus` (string)
- `days` (number)
- `definitions` (string)
- `downloads` (object)
- `eventCount` (number)
- `golden` (array)
- `limitations` (string)
- `location` (object)
- `mode` (string)
- `nautical`
- `period` (string)
- `preview` (array)
- `request` (object)
- `solarNoon`
- `startDate` (string)
- `sunrise`
- `sunriseAzimuth` (number|null)
- `sunset`
- `sunsetAzimuth` (number|null)
- `timeZone` (string)
- `values` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-golden-hour/golden-hour#diagnostics

## Score history

- 2026-10-22: 74

## Common questions

### 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.

## Links

- Remote endpoint: https://golden-hour.zovo.one/mcp
- Website: https://golden-hour.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-golden-hour/golden-hour.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-golden-hour/golden-hour.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-golden-hour/golden-hour