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

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

## Components

- remote · `api.sunrise-sunset.org`: 67/100 (this document), [markdown](https://verifymcp.io/servers/org-sunrise-sunset-sun-times/api.md), [page](https://verifymcp.io/servers/org-sunrise-sunset-sun-times/api)

## Channel facts

- Endpoint: `https://api.sunrise-sunset.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-18.

- **Endpoint Security**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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.

## Install

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

### Claude

```bash
claude mcp add --transport http org-sunrise-sunset-sun-times 'https://api.sunrise-sunset.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-sunrise-sunset-sun-times": {
      "url": "https://api.sunrise-sunset.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-sunrise-sunset-sun-times": {
      "type": "http",
      "url": "https://api.sunrise-sunset.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-sunrise-sunset-sun-times]
url = "https://api.sunrise-sunset.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-sunrise-sunset-sun-times": {
      "type": "remote",
      "url": "https://api.sunrise-sunset.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-sunrise-sunset-sun-times --url 'https://api.sunrise-sunset.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-sunrise-sunset-sun-times:
    url: "https://api.sunrise-sunset.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-sunrise-sunset-sun-times": {
      "Transport": "http",
      "Url": "https://api.sunrise-sunset.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-sunrise-sunset-sun-times -t streamable-http -u 'https://api.sunrise-sunset.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-sunrise-sunset-sun-times": {
      "type": "http",
      "url": "https://api.sunrise-sunset.org/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-16 (score 67, +3)

- [security] 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
- [functional improvement] Schema quality: 279 → 249
- [functional improvement] MCP protocol: fail → pass
- [functional improvement] Tool “get_sun_times” now declares an output schema
- [functional improvement] 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

### 2026-10-15 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-14 (score 64)

First indexed and scored.

## MCP tools (2)

### `get_sun_times` (~200 tokens)

Sunrise & sunset times

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.

Input parameters:

- `date` (string): 'today' (default), 'tomorrow' or YYYY-MM-DD. Relative dates resolve in the local timezone of the coordinates.
- `lat` (number, required): Latitude in decimal degrees.
- `lng` (number, required): Longitude in decimal degrees.
- `tz` (string): IANA timezone like 'Europe/Madrid'. Omit to use the local timezone of the coordinates, resolved automatically (recommended).

Output parameters:

- `astronomical_twilight_begin` (string|null): Start of astronomical twilight, ISO 8601 with the local UTC offset; null if it does not happen that day.
- `astronomical_twilight_end` (string|null): End of astronomical twilight, ISO 8601 with the local UTC offset; null if it does not happen that day.
- `attribution` (string)
- `blue_hour` (object)
- `civil_twilight_begin` (string|null): Start of civil twilight, ISO 8601 with the local UTC offset; null if it does not happen that day.
- `civil_twilight_end` (string|null): End of civil twilight, ISO 8601 with the local UTC offset; null if it does not happen that day.
- `date` (string): Local date, YYYY-MM-DD.
- `dawn` (string|null): Dawn (start of civil twilight), ISO 8601 with the local UTC offset; null if it does not happen that day.
- `day_length` (integer|null): Seconds of daylight: 86400 with midnight sun, 0 with polar night, null on a day with only one of sunrise/sunset.
- `dusk` (string|null): Dusk (end of civil twilight), ISO 8601 with the local UTC offset; null if it does not happen that day.
- `first_light` (string|null): First light (start of astronomical twilight), ISO 8601 with the local UTC offset; null if it does not happen that day.
- `golden_hour` (object)
- `last_light` (string|null): Last light (end of astronomical twilight), ISO 8601 with the local UTC offset; null if it does not happen that day.
- `lat` (number)
- `lng` (number)
- `moon_illumination` (number): Illuminated fraction of the moon at local noon, in percent (0-100).
- `moon_phase` (string): Moon phase at local noon.
- `moonrise` (string|null): Moonrise, ISO 8601 with the local UTC offset; null if it does not happen that day.
- `moonset` (string|null): Moonset, ISO 8601 with the local UTC offset; null if it does not happen that day.
- `nautical_twilight_begin` (string|null): Start of nautical twilight, ISO 8601 with the local UTC offset; null if it does not happen that day.
- `nautical_twilight_end` (string|null): End of nautical twilight, ISO 8601 with the local UTC offset; null if it does not happen that day.
- `solar_noon` (string|null): Solar noon, ISO 8601 with the local UTC offset; null if it does not happen that day.
- `solar_position` (object)
- `sun_status` (string)
- `sunrise` (string|null): Sunrise, ISO 8601 with the local UTC offset; null if it does not happen that day.
- `sunset` (string|null): Sunset, ISO 8601 with the local UTC offset; null if it does not happen that day.
- `tzid` (string): IANA timezone used.
- `utc_offset` (string): UTC offset of the location at local noon, like +02:00.

### `get_sun_times_range` (~223 tokens)

Sunrise & sunset times for a date range

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.

Input parameters:

- `date_end` (string, required): 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, required): First day, YYYY-MM-DD.
- `lat` (number, required): Latitude in decimal degrees.
- `lng` (number, required): Longitude in decimal degrees.
- `tz` (string): IANA timezone like 'Europe/Madrid'. Omit to use the local timezone of the coordinates, resolved automatically (recommended).

Output parameters:

- `attribution` (string)
- `days` (array): One entry per local day that exists in that timezone, in order; match entries by their date field.
- `lat` (number)
- `lng` (number)
- `tzid` (string): IANA timezone used.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-sunrise-sunset-sun-times/api#diagnostics

## Score history

- 2026-10-18: 67
- 2026-10-17: 67
- 2026-10-16: 67
- 2026-10-15: 64
- 2026-10-14: 64

## Common questions

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

## Links

- Remote endpoint: https://api.sunrise-sunset.org/mcp
- Repository: https://github.com/sunrise-sunset-org/mcp
- Website: https://sunrise-sunset.org/mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-sunrise-sunset-sun-times/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-sunrise-sunset-sun-times/api.json
- HTML version of this page: https://verifymcp.io/servers/org-sunrise-sunset-sun-times/api