Stellarhound — stargazing forecasts, dark-sky sites & aurora MCP server
com.stellarhound/stellarhound-mcpstellarhound.comstreamable-httpv0.1.0Scanned
Live stargazing forecasts: per-night sky scores, dark-sky sites, aurora & light pollution anywhere.
6 tools: 1 change things and 5 only read.
- Reads private data · 1
- Reads text others write · 6
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Stellarhound — stargazing forecasts, dark-sky sites & aurora MCP server can do
The Stellarhound — stargazing forecasts, dark-sky sites & aurora MCP server is published by stellarhound.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (1 tool: calculate_telescope_fov), but cannot delete data. 5 tools only read.
1 tool reads private data (find_dark_sky_sites); 6 tools bring in text other people can write (get_stargazing_conditions, get_tonight_agenda, find_dark_sky_sites and 3 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 1Claude Code: ask
calculate_telescope_fovCompute astrophotography field of view, image scale, diffraction limits, and seeing sampling (fov-v1).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Compute astrophotography field of view, image scale, diffraction limits, and seeing sampling (fov-v1). Use when the user asks "will M31 fit in my telescope + camera", "what is the image scale of an RedCat 51 / Askar SQA55 / EdgeHD 8 with an ASI2600MC", or "am I undersampled or oversampled". Uses Stellarhound's deterministic fov-v1 rules (exact 2*atan(s / 2f) field of view, 206.265*pixel_um/f_mm image scale, Dawes 116/D and Rayleigh 138/D limits, and Nyquist 2-3 px/FWHM sampling bands across 1.5", 2.0", 2.5", 3.0" seeing). Args: focal_length_mm: Effective focal length in mm (include reducer/barlow factor if used, >0). aperture_mm: Clear aperture diameter in mm (>0). sensor_w_mm: Sensor width in mm (>0). sensor_h_mm: Sensor height in mm (>0). pixel_um: Pixel pitch in micrometres (>0, optional). Returns {rules_version, fov_w_deg, fov_h_deg, fov_diag_deg, fov_w_arcmin, fov_h_arcmin, f_ratio, scale_arcsec_px, dawes_arcsec, rayleigh_arcsec, sampling:[{fwhm_arcsec, px_per_fwhm, verdict}], source_url, citation}.
Annotations the server declares
- title: Calculate telescope field of view & sampling
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
Only reads 5Show 5 read-only tools
find_dark_sky_sitesRecommend dark-sky sites near a location, ranked by whether the drive is worth it.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "find_dark_sky_sites" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "drive": it reads files.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.Reads text others writeNo findings
Why it is in this group
- The name "get_aurora_forecast" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.Reads text others writeNo findings
Why it is in this group
- The name "get_light_pollution" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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).Reads text others writeNo findings
Why it is in this group
- The name "get_stargazing_conditions" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.Reads text others writeNo findings
Why it is in this group
- The name "get_tonight_agenda" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:47 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://stellarhound.com/mcp: tools/list returned 6 tools to an anonymous client, including calculate_telescope_fov (write)
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 0 to 1
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
- Tools that change things, listed without credentials: 0 to 1
Tools1 added.+1 addedView diff
- Added:calculate_telescope_fovChanges things
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/mcpclaude mcp add --transport http stellarhound https://stellarhound.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, 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": [
"mcp__stellarhound__calculate_telescope_fov"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as stellarhound. Review it before you use it.
Capability tags behind 6 rules
- mcp__stellarhound__get_stargazing_conditions untrusted-input
- mcp__stellarhound__get_tonight_agenda untrusted-input
- mcp__stellarhound__find_dark_sky_sites private-data, untrusted-input
- mcp__stellarhound__get_aurora_forecast untrusted-input
- mcp__stellarhound__get_light_pollution untrusted-input
- mcp__stellarhound__calculate_telescope_fov untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.stellarhound/stellarhound-mcp/verify?hash=2dc8b28edb5fd984822bcb9979085a57dacdcab2e98128065811f91ce10a0162" | jq -e '.changed == false'Pinned hash 2dc8b28edb5f, from Nov 14, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.stellarhound/stellarhound-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.stellarhound/stellarhound-mcp)Source: MCP Registry. Synced Oct 21, 2026, 18:05 UTC.
Stellarhound — stargazing forecasts, dark-sky sites & aurora MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Stellarhound — stargazing forecasts, dark-sky sites & aurora MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Stellarhound — stargazing forecasts, dark-sky sites & aurora MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Stellarhound — stargazing forecasts, dark-sky sites & aurora MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Stellarhound — stargazing forecasts, dark-sky sites & aurora MCP server have?
- 6 tools: 1 write, 5 read. calculate_telescope_fov, get_stargazing_conditions, get_tonight_agenda, find_dark_sky_sites, get_aurora_forecast and get_light_pollution.
Does the Stellarhound — stargazing forecasts, dark-sky sites & aurora MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Stellarhound — stargazing forecasts, dark-sky sites & aurora MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Stellarhound — stargazing forecasts, dark-sky sites & aurora MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 1, 2026. Every change is on this page and in its Atom feed.