Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.thirdtrail/thirdtrail

REMOTE · THIRDTRAIL.LIFE

Elevation-corrected sun, moon, twilight, solar and tide data for any point on Earth

Available components

−1 this week 89 Trust /100

Last scanned (19 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security89
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2312 tokens (~289/item across 8 items; 8 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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 Nov 26 −1
    • Schema quality: 250 → 289 ▼ functional
    • “get_daily_light_integral” reworded the description of “elevation” cosmetic
    • “get_prayer_times” reworded the description of “elevation” cosmetic
    • “get_solar_path” reworded the description of “elevation” cosmetic
    • “get_solar_position” reworded the description of “elevation” cosmetic
    • “get_sun_moon_times” reworded the description of “elevation” cosmetic
    • “get_tide_window” reworded the description of “elevation” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 +1
    • Stability: fail → pass ▲ security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90.

Diagnostics

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 21 Nov 2026 · Probed https://thirdtrail.life/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thirdtrail.life CN=WE1,O=Google Trust Services,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA256 daacde16681a78e2130f078dac70fff6
SANs: thirdtrail.life, *.thirdtrail.life
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 thirdtrail.life. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
life. DS published 1831 8 Verified
thirdtrail.life. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy same-origin

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://thirdtrail.life/mcp Verified 200
http (plaintext) http://thirdtrail.life/mcp HTTPS enforced 301 https://thirdtrail.life/mcp
MCP tools · 8 exposed · ~2,207 tokens

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 →

Tool Tokens
get_daily_light_integral ~243

Clear-sky Daily Light Integral in mol/m²/day for each day in a range: photosynthetically active radiation integrated from sunrise to sunset. Use it to plan crop growth or supplemental greenhouse lighting; it assumes cloudless skies, so treat it as the ceiling for the site. Pass from and to together for a range of UTC days, or neither for today. Requires an API key on a paid Solar plan.

NameTypeReqDescription
elevationnumber–Metres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zer…
fromstring–First UTC day, YYYY-MM-DD. Requires to.
latnumberyesLatitude in decimal degrees.
lonnumberyesLongitude in decimal degrees.
tostring–Last UTC day, YYYY-MM-DD. Requires from.

No output schema declared.

No examples provided.

get_prayer_times ~356

Fajr, sunrise, dhuhr, asr, maghrib and isha for one date at a location, elevation-corrected. Use it for Islamic prayer schedules; for general sunrise, sunset and twilight use get_sun_moon_times. school is required and sets the fajr and isha rules; asr_method picks the shadow rule and defaults to shafi. date defaults to today. Requires an API key on a paid Ephemerides plan.

NameTypeReqDescription
asr_methodstring–Asr shadow rule: shafi (default; also Maliki and Hanbali) or hanafi, which gives a later Asr.
datestring–Day as YYYY-MM-DD. Defaults to today.
elevationnumber–Metres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zer…
latnumberyesLatitude in decimal degrees.
lonnumberyesLongitude in decimal degrees.
schoolstringyesCalculation school: mwl (Muslim World League), isna (Islamic Society of North America), egyptian (Egyptian General Authority of Survey), karachi (University of Islamic Sciences, Karachi), uaq (Umm al…
tzstring–IANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC.

No output schema declared.

No examples provided.

get_solar_path ~225

The sun's azimuth and altitude through one UTC day, sampled every interval: a list of timestamped positions. Use it for shading studies, PV siting and panel-angle planning; for a single instant use get_solar_position. date defaults to today and interval to 15m. Requires an API key on a paid Solar plan.

NameTypeReqDescription
datestring–UTC day as YYYY-MM-DD. Defaults to today.
elevationnumber–Metres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zer…
intervalstring–Sampling step. Defaults to 15m.
latnumberyesLatitude in decimal degrees.
lonnumberyesLongitude in decimal degrees.

No output schema declared.

No examples provided.

get_solar_position ~334

The sun's position at one instant: azimuth, altitude, zenith, declination, hour angle and equation of time, plus clear-sky irradiance (GHI, DNI and DHI in W/m²) when include asks for it and the plan covers it. Use it for where the sun is at a given moment; for its track through a whole day use get_solar_path, and for rise and set times use get_sun_moon_times. timestamp defaults to now. Positions are NREL SPA-equivalent on JPL DE421; irradiance comes from the Bird clear-sky model. Requires an API key on a paid Solar plan.

NameTypeReqDescription
elevationnumber–Metres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zer…
includestring–position (default) or position,irradiance.
latnumberyesLatitude in decimal degrees.
lonnumberyesLongitude in decimal degrees.
timestampstring–ISO 8601 instant, e.g. 2026-06-21T12:00:00Z. Defaults to now.
tzstring–IANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC.

No output schema declared.

No examples provided.

get_sun_moon_times ~311

Sunrise, sunset, solar noon, civil, nautical and astronomical twilight, golden and blue hour, moonrise, moonset and moon phase for a location, one entry per day. Use it for any question about when the sun or moon rises, sets or gets dark; for the sun's angle at a given moment use get_solar_position, and for tides alongside the sun use get_tide_window. Pass elevation whenever you know it: it shifts sunrise and sunset at altitude. Defaults: from today, 7 days or the plan's limit if lower. Requires an API key on a paid Ephemerides plan.

NameTypeReqDescription
daysinteger–Number of days to return. The ceiling is plan-dependent.
elevationnumber–Metres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zer…
latnumberyesLatitude in decimal degrees.
lonnumberyesLongitude in decimal degrees.
start_datestring–First day as YYYY-MM-DD. Defaults to today.
tzstring–IANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC.

No output schema declared.

No examples provided.

get_tide_extremes ~219

High and low water times and heights at any coastal point, from the FES2022 global tide atlas: a list of events, each with type (high or low), time and height_m. Use it for when high or low tide is; for a continuous curve use get_tide_heights, and for tides together with sunrise, golden hour and moon phase use get_tide_window. Heights are metres relative to MEAN SEA LEVEL, not chart datum — never use for navigation. Defaults: from today, 2 days or the plan's limit if lower. Requires an API key on a paid Tides plan.

NameTypeReqDescription
daysinteger–Number of days to return. The ceiling is plan-dependent.
latnumberyesLatitude in decimal degrees.
lonnumberyesLongitude in decimal degrees.
start_datestring–First day as YYYY-MM-DD. Defaults to today.
tzstring–IANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC.

No output schema declared.

No examples provided.

get_tide_heights ~208

Water height at a coastal point at a fixed step: a list of time and height_m pairs. Use it to plot a tide curve or read the height at a particular time; for just the highs and lows use get_tide_extremes. Metres relative to mean sea level, not chart datum. Defaults: from today, 2 days, and the finest step the plan allows, but no finer than 10m. Requires an API key on a paid Tides plan.

NameTypeReqDescription
daysinteger–Number of days to return. The ceiling is plan-dependent.
latnumberyesLatitude in decimal degrees.
lonnumberyesLongitude in decimal degrees.
start_datestring–First day as YYYY-MM-DD. Defaults to today.
stepstring–Sampling interval. Finer steps need a higher plan.
tzstring–IANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC.

No output schema declared.

No examples provided.

get_tide_window ~311

Per day: high and low waters together with sunrise, sunset, golden and blue hour, twilight and moon phase in a single call. The planning tool for coastal photography, fishing and shore work; use it instead of calling get_tide_extremes and get_sun_moon_times separately. Pass elevation when you know it: it shifts the sun and moon times — roughly three minutes at clifftop height — but never the tide heights, which do not depend on where the observer stands. Defaults: from today, 2 days or the plan's limit if lower. Requires an API key on a paid Tides plan.

NameTypeReqDescription
daysinteger–Number of days to return. The ceiling is plan-dependent.
elevationnumber–Metres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zer…
latnumberyesLatitude in decimal degrees.
lonnumberyesLongitude in decimal degrees.
start_datestring–First day as YYYY-MM-DD. Defaults to today.
tzstring–IANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC.

No output schema declared.

No examples provided.

Install

How do I install the io.github.thirdtrail/thirdtrail MCP server?

io.github.thirdtrail/thirdtrail is a hosted endpoint at https://thirdtrail.life/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 · thirdtrail.life

# add to Claude Code
claude mcp add --transport http thirdtrail-thirdtrail 'https://thirdtrail.life/mcp'
Common questions

What is the io.github.thirdtrail/thirdtrail MCP server?

io.github.thirdtrail/thirdtrail is an MCP server listed in the public MCP registry as io.github.thirdtrail/thirdtrail. Elevation-corrected sun, moon, twilight, solar and tide data for any point on Earth. This page covers its hosted endpoint (https://thirdtrail.life/mcp).

Is the io.github.thirdtrail/thirdtrail MCP server safe to use?

io.github.thirdtrail/thirdtrail scores 89 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 io.github.thirdtrail/thirdtrail MCP server expose?

io.github.thirdtrail/thirdtrail exposes 8 tools: get_sun_moon_times, get_prayer_times, get_solar_position, get_solar_path, get_daily_light_integral, and 3 more. Their descriptions and schemas cost roughly 2,207 tokens of context every time the server is loaded.

Does the io.github.thirdtrail/thirdtrail MCP server require authentication?

Yes. io.github.thirdtrail/thirdtrail asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the io.github.thirdtrail/thirdtrail MCP server still maintained?

io.github.thirdtrail/thirdtrail is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.thirdtrail/thirdtrail MCP server?

VerifyMCP ran 13 checks on io.github.thirdtrail/thirdtrail, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.