Stellarhound — stargazing forecasts, dark-sky sites & aurora
by stellarhound.com · remote · no sign-in to list tools · v0.1.0 · published by com.stellarhound
Live stargazing forecasts: per-night sky scores, dark-sky sites, aurora & light pollution anywhere.
5 tools: 5 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things0Claude Code: ask
- Only reads5Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http stellarhound https://stellarhound.com/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
5 tools
Only reads 5Claude Code: allow
find_dark_sky_sitesRecommend dark-sky sites near a location, ranked by whether the drive is worth it.No findings
Why it is in this group
- The name "find_dark_sky_sites" says "find": a word for reading.
Description, as the server wrote it Recommend dark-sky sites near a location, ranked by whether the drive is worth it. Use for "where should I drive to stargaze near X". Sites are grouped by drivability (how far), then ranked by a drive-worth score combining the best weather window over the next 7 nights, how much darker the site is than the user's location, and drive time. Drive times are approximate (straight-line x 1.3), not routed. Args: lat: Latitude in decimal degrees (-90..90). lon: Longitude in decimal degrees (-180..180). limit: Max sites to return, 1-12 (default 5). Returns {ranking (methodology note), tiers:[{tier, label, hint, sites:[...]}], nearest_km, uncertainty_note, attribution} — sites grouped into drivability tiers. Include the methodology note when presenting — it explains the ordering honestly.
Annotations the server declares
- title: Find dark-sky sites nearby
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_aurora_forecastGet the aurora (northern/southern lights) outlook for a location.No findings
Why it is in this group
- The name "get_aurora_forecast" says "get": a word for reading.
Description, as the server wrote it Get the aurora (northern/southern lights) outlook for a location. Use for "any chance of aurora tonight near X". Combines the Kp-index forecast with the location's geomagnetic latitude to say whether aurora could be visible there, and when. Args: lat: Latitude in decimal degrees (-90..90). lon: Longitude in decimal degrees (-180..180). Returns {kp_forecast:[{time, kp, flag: observed|estimated|predicted}, ...], visibility assessment fields, attribution}. Kp entries are flagged by how firm they are — keep those labels when presenting.
Annotations the server declares
- title: Aurora outlook for a location
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_light_pollutionEstimate light pollution at any point: approximate Bortle class and what's visible there.No findings
Why it is in this group
- The name "get_light_pollution" says "get": a word for reading.
Description, as the server wrote it Estimate light pollution at any point: approximate Bortle class and what's visible there. Use for "how dark is the sky at X" / "can I see the Milky Way from X". Returns the zenith-brightness-derived estimate (mpsas, approximate Bortle class) and a plain-language ceiling: what the Milky Way, naked-eye and telescope views are like under that sky. This is a satellite-data estimate, not a field measurement — say so. Args: lat: Latitude in decimal degrees (-90..90). lon: Longitude in decimal degrees (-180..180). Returns {light_pollution:{bortle_approx, mpsas, ceiling:{label, milky_way, naked_eye, telescope}, note}, attribution}.
Annotations the server declares
- title: Light pollution at a point
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_stargazing_conditionsScore the next nights for stargazing at a location (0-100 per night).No findings
Why it is in this group
- The name "get_stargazing_conditions" says "get": a word for reading.
Description, as the server wrote it Score the next nights for stargazing at a location (0-100 per night). Use for "when should I stargaze this week near X", "is Saturday any good for the Milky Way", trip planning. Each night combines the three-layer cloud-cover forecast, moon illumination and up-fraction, and the astronomical-darkness window; `best_window` names the best upcoming night. Also returns the location's light-pollution estimate (approximate Bortle class + what's visible at that darkness). Args: lat: Latitude in decimal degrees (-90..90). You know city coordinates — pass them. lon: Longitude in decimal degrees (-180..180). nights: How many nights ahead to score, 1-16 (default 7; forecasts beyond ~7 nights are increasingly uncertain). Returns {timezone, light_pollution, nights:[{date, darkness, moon, cloud, score:{value, band, summary}}], best_window, uncertainty_note, attribution}. Present scores/verdicts verbatim; skies beyond ~7 days are provisional.
Annotations the server declares
- title: Stargazing forecast (per-night sky scores)
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_tonight_agendaGet tonight's stargazing plan for a location: score, darkness window, and what to observe.No findings
Why it is in this group
- The name "get_tonight_agenda" says "get": a word for reading.
Description, as the server wrote it Get tonight's stargazing plan for a location: score, darkness window, and what to observe. Use when the user asks "what can I see tonight" / "is tonight worth going out". Returns tonight's sky score and darkness window plus a ranked agenda of observing targets appropriate for the location's sky darkness. Args: lat: Latitude in decimal degrees (-90..90). lon: Longitude in decimal degrees (-180..180). Returns {timezone, light_pollution, tonight:{date, darkness, weather,...}, targets/agenda entries, attribution}. Report as returned.
Annotations the server declares
- title: Tonight's observing agenda
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http stellarhound https://stellarhound.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__stellarhound__get_stargazing_conditions",
"mcp__stellarhound__get_tonight_agenda",
"mcp__stellarhound__find_dark_sky_sites",
"mcp__stellarhound__get_aurora_forecast",
"mcp__stellarhound__get_light_pollution"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as stellarhound. Review it before you use it.