oddsky
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@oddsky Open case OS-0001 and run the skeptic on the leading hypothesis"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
oddsky
The universe is an open question.
An open observatory your AI agent can use. Point Claude Code, Codex, Cursor or a local model at real telescope data on strange stars. What comes back is an investigation you can check: every claim is tagged with how we know it, every number has a receipt you can replay, and every prediction is sealed and then graded by the sky.
Oddsky ships the observatory, not the AI. It costs nothing to run, needs no account or API key, and works with whatever agent you already have.
Live at oddsky.ai. The fastest way in is the hosted observatory:
claude mcp add --transport http oddsky https://oddsky.ai/mcpThe first time your agent uses it, your browser opens to sign in (GitHub, Google or a passkey) and choose an observer code. No key to copy.
Predictions sealed there go on the public, hash-chained Sky Ledger and are graded by the archives. Or run everything locally:
claude mcp add oddsky -- uvx --from git+https://github.com/AlanShortz/oddsky oddsky mcp
# or from a clone:
claude mcp add oddsky -- uv run --directory /path/to/oddsky oddsky mcpThen ask: "Open Oddsky case OS-0001. Run the skeptic first, then try to break the leading hypothesis. Tag every claim honestly."
The first case: the star that glowed before it dimmed
ASASSN-21qj is a Sun-like star 1,850 light-years away. NEOWISE shows its infrared switching on between November 2017 and April 2018: W2 brightened 0.8 mag, and the excess has a colour temperature of about 1,000 K. Three years later the visible star began to flicker and fade by up to 2 magnitudes, more in blue than in red, which is what small dust grains do. The first Oddsky investigation (write-up) was done entirely through Oddsky tools: 95 logged tool calls, 17 tagged claims, 6 competing hypotheses. It also found two things no paper has reported, because they happened after the papers were written:
the star has been back at its pre-event brightness, and flat to 0.005 mag, since early 2025;
an apparent 2025 "recovery" in the I and R bands is a step change on one night, a calibration artifact in the only optical record.
It then sealed three predictions for 2027 with probabilities attached. The sky will grade them.
The optical light curve is 7,115 measurements by one amateur astronomer, Franz-Josef Hambsch (AAVSO code HMB). Oddsky credits observers by name, and the Skeptic warns that a single observer is a single point of failure.
Related MCP server: aqc-mcp
What's in the box
The observatory | 25 MCP tools: case overview, light curves, changepoints, excursions (dips and flares), Lomb-Scargle with spectral-window alias flags, microlensing fits (point lens with annual parallax, profile ranges), cross-band colour slopes, WISE colour and infrared-excess temperature, Gaia neighbours, and tools for recording claims, hypotheses and predictions. |
Archives | Gaia DR3 (context, neighbours, variability), NEOWISE 2014-2024 (quality-cut, visit-binned), AAVSO (a century of amateur photometry), TESS (SPOC/QLP), ZTF, ATLAS (whole-sky forced photometry, 2015-), ASAS-SN. Every cut is written to provenance. |
The Skeptic | Deterministic artifact checks: blends inside each survey's beam, saturation, single-observer data, series that start mid-event (against Gaia's baseline), colour coherence across bands, survey-rhythm aliases, unobserved onsets, TESS dips on momentum dumps and sector edges, RUWE. It is code, so it cannot be talked out of a warning. |
Cases | A case is a directory ( |
Trials | Blind (identity, coordinates and dates scrubbed; name the explanation), hindsight (data cut at a date; forecast what happens next, graded against what actually happened), and salted (real data with planted spacecraft artifacts). Answers are sha256-sealed before anyone runs. |
The viewer |
|
First hunts: what Oddsky found, and what it got wrong
We pointed Oddsky at the whole Gaia DR3 sky and asked for Sun-like stars that faded (hunt H-0001). 22,125 stars → 2,020 not already eclipsing binaries → 18 with deep, confirmed dips → 3 not explained by any catalogue.
Two new eclipsing binaries. OS-0011 (P = 2.52961 d, an Algol-type pair) and OS-0012 (P = 11.9008 d, two K dwarfs). Gaia and ZTF agree on both over an 11-year baseline. Gaia's pipeline had given them periods of 53 and 36 minutes, VSX inherited those, and nobody checked again. Small and new: a VSX submission, not a press release.
The invisible companion that wasn't. We first folded OS-0012 at 2.38 days, a fifth of its true period. That stacked the secondary eclipse onto the primary, so it looked as if a Sun-sized, perfectly dark object blocked 58% of the star every 2.38 days. We had written it up as a candidate opaque disk. An Oddsky referee agent was told to break it. It counted which cycles actually showed eclipses, found that only every fifth one did, pulled TESS sector 80 to confirm, and fitted an ordinary two-star model (reduced chi² 1.16). It took 30 minutes, and nothing was announced. The tool that fooled us now runs a missing-eclipse test automatically.
EE Cep's 2025 eclipse (OS-0003) was 1.44 ± 0.03 mag deep in V, twice 2014's depth (73% of the light blocked against 48%), measured by eight independent AAVSO observers. The referee corrected five overstatements, including the novelty claim: professional-led AAVSO campaigns observed it and plan to publish. Ours is an early independent measurement, labelled as such.
NSV 1302 (OS-0010): a "suspected variable" since the photographic era, characterised as an irregular young-star dipper in Per OB2.
The whole infrared sky, then a star that vanished (hunt H-0002). We read all 146.6 billion NEOWISE detections (2014-2024) for 164.7 million stars (Galactic latitude ≥ 10°) on Google Cloud in under two hours, for a few dollars. The question was which Sun-like stars suddenly grew hot dust, as ASASSN-21qj did. The pipeline recovered ASASSN-21qj blind at 46σ. After Skeptic and referee vetting, two of the 314 flags survive. In OS-0014, a G dwarf 420 pc away vanished for ~95 days in 2017, more than 99% of its light blocked at the deepest, nearly grey across four optical filters. ASAS-SN, SkyMapper and NEOWISE saw it independently, and comparison stars stayed steady. Afterwards a warm infrared glow appeared, and it was still there in 2024. As far as SIMBAD, VSX, the alert streams and the literature show, nobody has reported it. In OS-0013, a K dwarf grew ~1000 K dust between two visits in 2018.
Hunt H-0004, stars that go dark (hunts/H-0004): the 2,356 WISE-selected R CrB candidates of Tisserand+2020, re-examined in 2018-2026 ZTF and ATLAS data for their first recorded decline. The classifier was calibrated on real R CrB stars first (14 of 14 that declined, 0 of 12 that never do). In the north every star that fades like an R CrB star and is bright enough for ZTF was already in a catalogue, which is a result. What nobody had reported: OS-0015, a dust-shrouded star near a star-forming region that goes dark for two to three weeks every 385.7 days, four times in four years, deeper in blue, with no secondary eclipse: a translucent dust structure on a one-year orbit. Periodogram-based classifiers never saw it because each eclipse lasts 4% of the orbit. The referee found a fourth eclipse we had missed and removed our "red giant" framing before it went anywhere. ATLAS then showed the same eclipses on the same ephemeris, including a 2023 one ZTF had missed, so the case stands at "reproduced". Two predictions are sealed for 2027-2028. The southern half of the candidate list is still queued on the ATLAS server.
One night in the infrared (hunt H-0007): which of 79,191 bright stars were dramatically brighter or fainter on just one of NEOWISE's day-long visits, equally at 3.4 and 4.6 µm? Blind, the search found OS-0014, a dozen dwarf novae in outburst and two microlensing events Gaia had already caught. New: OS-0016, a red giant 3 kpc away toward the Galactic anticentre that brightened sevenfold for a few weeks in 2017. NEOWISE and ATLAS saw it on the same night. It is a gravitational microlensing event: a foreground star, probably a faint M dwarf, passed almost exactly in front of it. Two referees checked it. The second cut our parallax claim down: the light curve is lopsided as parallax predicts, but the lens mass is not measured. Gaia DR4 (December 2026) scanned the star three times during the event, and a sealed prediction says what it will show. A second pass over fainter stars found another: OS-0017, a halo giant more than 6 kpc away that brightened at least 2.4 times in March 2020, seen by NEOWISE, ATLAS and ZTF.
The lensing sky (hunt H-0008): the same question for every star in the sky, the Galactic plane included. The search read 106.7 billion NEOWISE detections of 195 million stars on Google Cloud in about three hours. Without being told where to look, it recovered 64 microlensing events that KMTNet, OGLE, Gaia and ZTF had already found. Our first draft claimed four new events; the referee found three of them in an online-only ZTF table and on TNS. Of the two that survived, ATLAS caught one whole: OS-0018, a reddened giant beyond 5 kpc that brightened 5.4 times on 2022 Sep 19 over about four months, a textbook microlensing event that nobody seems to have reported. The other, OS-0019, brightened once by 60% but no simple lens fits it, so it stays a candidate. Fitting these events by hand became a tool any agent can call:
lens_fit.The long lenses (hunt H-0009): the lensing-sky search again, without its blind spots (saturated peaks, multi-visit events, stars beside bright neighbours or blended with others). It finds 118 known microlensing events instead of 64; most of the gain comes from stars the first pass never searched. Its 122 strong unexplained brightenings, where a black-hole lens would hide, are not yet followed up.
One hunt parked: new R CrB stars (H-0003). Gaia DR3 has already been mined by the experts, and our candidates were a VY Scl binary, a Mira, an S star and a T Tauri star.
OS-0014 is the first result here that a professional might call a discovery, pending their check, spectra and Gaia DR4. The pipeline also caught our own false positive before the internet did. Feynman would have liked that part best.
Strange Stars Trial 001
Ten packets of real archive data with names, coordinates and dates removed, including one ordinary
star and one quiet star with planted spacecraft artifacts. Two are hindsight packets, cut at a
date. The answers were sealed (sha256 4608af90…, committed in eac42b3) before any investigator
ran, then revealed and verified (oddsky trial verify trials/strange-stars-001). Two agents used
the same tools and the same prompt:
top-1 | Brier (lower is better) | mean p(truth) | hindsight forecasts | |
claude-opus-5.5 | 10/10 | 0.10 | 0.77 | 7 of 8 true (the miss was rated 8%); Brier 0.09 |
claude-haiku-5.5 | 5/10 | 0.71 | 0.38 | 2 of 3 resolved true; 3 still pending |
claude-fable-5.2 (run 2026-11-10, after the reveal) | 9/10 | 0.20 | 0.75 | 5 of 8 true; Brier 0.11 |
uniform guessing | 0.9/10 | 0.91 | 0.09 |
What's worth knowing, including the parts that don't flatter anyone:
Opus recognised 8 of the 10 packets (self-reported, tagged as speculation): R CrB, SS Cyg, EE Cep, ASASSN-21qj and others. Blinding hides names, not physics. On the two packets it did not recognise (the ordinary star and the salted one) it went 2/2. Trial 002 (below) was built to have no famous stars.
EE Cep, from data cut a year before its 2025 eclipse: Opus timed the next eclipse from the previous six (period 2048 d) and registered four forecasts. All four came true, including the one it had rated at 45%. Haiku called the star a pulsator.
The salted packet nearly fooled Opus: artifact 0.33 against dust 0.30. Its reason is a fair criticism of us: our planted dips were smoother and longer than real momentum-dump glitches. Haiku missed them entirely and called the star normal.
We found a bug in our own grader. "Brightest" was the 2nd percentile of all points, so dense quiescent sampling hid real SS Cyg outbursts and two correct forecasts were graded false. v2 uses nightly medians. Because the change came after the reveal, both gradings are published in the scorecards.
Fable 5.2, two weeks later: same packets, prompt and tool version. It said it recognised the same eight packets and missed one: it saw that every dip in the salted packet sat on a momentum dump and then called the star normal (0.80) instead of an instrumental artifact (0.10).
Every claim, hypothesis and prediction the agents made is in trials/strange-stars-001/runs/, and
every tool call in it replays.
Strange Stars Trial 002
Trial 001 could not tell skill from memory, so Trial 002 uses eight stars from Oddsky's own casebook:
none famous, several catalogued, none with a paper describing what it does. Five have a scored answer
(Oddsky's own, and Opus 5.5 contributed to the casebook it comes from); three are open questions where
only the forecasts are graded, against held-back data. Sealed sha256 acd28697… in 00d4310.
matched the key | Brier | forecasts true | forecast Brier | |
claude-haiku-5.5 | 2/5 | 0.71 | 2 of 7 | 0.25 |
claude-opus-5.5 | 5/5 | 0.06 | 8 of 10 | 0.23 |
claude-fable-5.2 | 5/5 | 0.08 | 13 of 15 | 0.17 |
One run each, forecasts on the same star are not independent, Fable's run was interrupted by a full
disk, and two grader rules changed after the reveal. All of that, and every number above, is on the
Trials page and recomputed by oddsky paper-check trials/page_claims.py.
Run it locally
git clone https://github.com/AlanShortz/oddsky && cd oddsky
uv sync --all-extras # Python 3.11-3.14
uv run oddsky skeptic OS-0001 # the Skeptic's report on the first case
uv run oddsky call ir_excess '{"case":"OS-0001","baseline_start":"2014-01-01","baseline_end":"2017-12-31","start":"2018-03-01","end":"2020-12-31"}'
uv run oddsky open "V838 Mon" --hook "..." # open a new case on any star and fetch its data
uv run oddsky export-web && python -m http.server -d web 8765Blind trial over MCP: claude mcp add oddsky-trial -- uv run oddsky mcp --blind trials/strange-stars-001/packets/T03.
Seed cases
case | star | status |
ASASSN-21qj: the star that glowed before it dimmed | reproduced | |
KIC 8462852 (Boyajian's Star) | observation | |
EE Cep: the 2025 eclipse, twice as deep | reproduced | |
R CrB: the star that smokes | observation | |
R Cyg: a Mira, strange to the eye and ordinary to astrophysics | observation | |
SS Cyg: the prototype dwarf nova | observation | |
AA Tau: the young star that went dark in 2011 | observation | |
OS-0008/9 | two quiet control stars in the TESS continuous viewing zone | trial controls |
NSV 1302: the young star nobody classified | interpreted | |
a new Algol-type binary, P = 2.52961 d | interpreted | |
the invisible companion that wasn't: a new K+K binary, P = 11.9008 d | closed | |
an infrared excess that appeared in 2018 (K dwarf) | anomaly | |
the star that vanished for three months (G dwarf, 2017) | anomaly | |
a dust-shrouded star that goes dark for two to three weeks every 385.7 days | reproduced |
Each one is an open invitation to investigate.
Philosophy
"The first principle is that you must not fool yourself, and you are the easiest person to fool." — Richard Feynman, Cargo Cult Science (1974)
"There must be no barriers to freedom of inquiry." — J. Robert Oppenheimer (1949)
AI agents are tireless and fluent, and that makes them dangerous in science, because they produce convincing nonsense without effort. Oddsky's answer is structural rather than a matter of tone: epistemic tags, receipts, a Skeptic that is code, predictions sealed in advance, and trials with sealed answers. Read the manifesto and how Oddsky keeps itself honest.
Credits
Built by Alan Shortz, with Claude. The data come from ESA Gaia, NASA/IPAC NEOWISE, the AAVSO International Database and its observers worldwide, NASA TESS via MAST, ZTF, and ASAS-SN. MIT licensed. See CONTRIBUTING and, for the scientific defaults that are still open questions, docs/OPEN_QUESTIONS.md.
Available Tools
26 toolsadd_claimA
Record a claim. tag must be observed | computed | inferred | speculated. Cite the call_id(s) of the tool results it rests on (computed and observed claims without calls are weak).
Inputs: tag (required), case (required), text (required), calls.
add_hypothesisB
Propose an explanation. klass from list_classes(). List claim ids that support it and that are in tension with it, and say what observation would falsify it.
Inputs: case (required), klass (required), statement (required), supports, +3 more.
case_overviewA
Start here. What the case is, what data exist (per series: span, points, brightness range), the stellar context from Gaia, and the claims and hypotheses recorded so far.
Inputs: case (required).
check_predictionA
Grade a registered prediction against the data now in the case. Predictions whose window has not closed yet are reported as pending and not graded. dry_run=True never writes. (Not available in blind trials, where the future is held back.)
Inputs: case (required), prediction (required), dry_run.
compare_windowsC
Median brightness of a series in window A vs window B, with the significance of the difference.
Inputs: case (required), a_end (required), b_end (required), series (required), +2 more.
cross_bandC
How series A changes when series B changes (near-simultaneous pairs): correlation and slope dA/dB, with the interstellar-dust expectation for comparison.
Inputs: case (required), series_a (required), series_b (required), end, +2 more.
describe_seriesB
Summary statistics, long-term slope, and the single most significant change in level (a changepoint: when, how big, which direction) for one series.
Inputs: case (required), series (required).
eclipse_periodA
Period of short, deep, rare events (eclipses) that Lomb-Scargle misses: find the period at which
every point more than depth mag below its series median falls at one phase, and no quiet point
does. Combine instruments (e.g. ["ZTF:ZTF_r", "GAIA:G"]) for a long-baseline ephemeris.
Inputs: case (required), series (required), depth, p_max, +1 more.
find_excursionsB
Find dips (fainter) and brightenings against a running baseline: start, end, depth, ingress/egress durations, asymmetry, and whether the start or end fell in a data gap. Restrict to a window (start/end) to get a local noise level, e.g. for quiet years.
Inputs: case (required), series (required), end, start, +3 more.
foldC
Fold a series on a period: phase-binned medians, primary depth (phase 0) and secondary depth (phase 0.5) within +/- window_phase, the faintest bin away from the primary (a secondary at any phase, for eccentric orbits), and primary depth on even vs odd cycles (catches period halving).
Inputs: t0 (required), case (required), period (required), series (required), +2 more.
get_lightcurveC
Points of one series, e.g. series='NEOWISE:W1' or 'AAVSO:V'. Optional time window and binning (median per bin_days). Long series are binned automatically to max_points.
Inputs: case (required), series (required), end, start, +2 more.
ir_excessC
Infrared excess in NEOWISE over a baseline (photosphere) epoch: excess flux in each band as a fraction of the star, and the blackbody temperature of the excess from its W1/W2 ratio.
Inputs: end (required), case (required), start (required), baseline_end (required), +1 more.
lens_fitA
Fit a gravitational microlensing event: a point source magnified by a point lens, without and (by default) with annual parallax, to one or more series at once (e.g. ["ATLAS:ATLAS_o", "ATLAS:ATLAS_c", "NEOWISE:W1"]). Each series is binned per night and turned into flux / its own baseline (median outside [start, end], or over the baseline window). Errors include that series' baseline night-to-night scatter and 1% of flux. Returns t0, tE, u0, A_max (and piE, fs), 95% ranges for t0 and tE from chi-square profiles (not covariance), how well the peak and wings are sampled, and how much the parallax model improves on the static one. A static fit much worse than the parallax fit means the light curve is asymmetric; a peak with no points means t0 and A_max rest on the wings. Microlensing is achromatic: fit the bands together and compare their residuals.
Inputs: end (required), case (required), start (required), series (required), +4 more.
list_casesB
List the cases you can investigate, with their status on the discovery ladder.
Inputs: no named parameters.
list_classesB
The Strange Stars explanation classes. Hypotheses must use one of these names.
Inputs: case.
literatureB
Recent papers mentioning the target (SIMBAD bibliography). Open mode only. Read them after forming your own view, not before, if you want your investigation to count as independent.
Inputs: case (required).
neighborsC
Gaia DR3 sources near the target: separation, brightness difference, and fraction of the target's flux. In blind mode, identities are removed.
Inputs: case (required), radius_arcsec.
observer_agreementB
Does every independent observer see the same thing? For each AAVSO observer (or camera) with data in both windows: their own baseline median, their faintest and median point in the event window, and the depth relative to their own baseline. Observer zero points cancel.
Inputs: end (required), case (required), start (required), series (required), +3 more.
open_caseB
Open a new case on any star by name (SIMBAD/AAVSO resolvable) and fetch its data from Gaia, NEOWISE, AAVSO, ZTF, ASAS-SN and TESS. Takes a minute or two.
Inputs: name (required), title, fetch_data.
periodogramC
Lomb-Scargle periodogram with the survey's spectral window, flagging peaks that match Earth/spacecraft rhythms (day, lunar month, TESS orbit, year) or window aliases.
Inputs: case (required), series (required), end, start, +2 more.
prior_artA
Run the Librarian: is it new? For a sky position (ra, dec in degrees; or give a case to use its target), look up the objects in SIMBAD and NED, merge the papers SIMBAD and ADS attach to them, ask the big catalogues (VSX, VarWISE, Milliquas, WISE AGN) and check the shelves of published samples. verdict: unlisted (no object anywhere) | catalogued (an object, but no paper title matches the topics; not evidence that nothing is published) | mentioned (titles match, but only in papers that list more than 500 objects) | studied (a title matches in a paper about the object, a shelf holds it, SIMBAD types it as a transient, or a catalogue of variables lists it: read those before calling anything new). An AGN-catalogue entry is reported and does not change the verdict. complete = false means a source could not be queried, or ADS held more papers than were read, and the verdict is not final. topics: transient, dimming, infrared_excess, binary (default all). epoch: the date of the position as a decimal year (2010.5 for AllWISE); give it for anything that may be a nearby star, so that SIMBAD's stars are moved to that date by their proper motion (default: no motion). Open mode only. Logged to the ledger when a case is given.
Inputs: ra, dec, case, epoch, +3 more.
register_predictionB
Register a falsifiable, machine-checkable prediction. Example: 'the median of AAVSO:V between start and end will be more than 0.3 mag fainter (op '>', value 0.3) than its median over the baseline window'. Without a baseline, value is an absolute magnitude. probability = your stated chance the check comes out true. The registration time is sealed by the ledger and git.
Inputs: op (required), end (required), case (required), start (required), +9 more.
retract_claimA
Retract a claim you no longer stand behind (a mistake, a probe, a superseded number). It stays in the record, struck through, with your reason. Nothing in Oddsky is silently deleted.
Inputs: case (required), claim (required), reason (required).
skeptic_reportB
Run the Skeptic: deterministic checks for blends, saturation, quality cuts, single-observer data, survey-rhythm aliases, unobserved onsets, TESS spacecraft systematics and more.
Inputs: case (required).
update_hypothesisC
Change a hypothesis's status (live | favored | disfavored | rejected) and confidence, with a reason.
Inputs: case (required), status (required), hypothesis (required), reason, +1 more.
wise_colorC
NEOWISE W1-W2 colour per visit and whether it tracks W1 brightness (warm dust signature).
Inputs: case (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 26 tools
Most tools target clearly distinct operations: data retrieval (get_lightcurve, describe_series), specialised analyses (lens_fit, eclipse_period, fold, periodogram), and the claim/hypothesis/prediction ledger are well separated. Only mild overlap exists in the time-domain group (periodogram vs eclipse_period vs fold, describe_series vs find_excursions vs compare_windows) and in the literature group (literature vs prior_art), but descriptions draw clear boundaries.
All names are consistent snake_case, but the verb convention is mixed: action tools use verb_noun (add_claim, update_hypothesis, register_prediction, open_case, list_cases), while many analysis tools are bare nouns (fold, periodogram, neighbors, literature, prior_art, lens_fit, ir_excess). Readable but not a single predictable pattern.
26 tools is on the heavy side, though the domain is genuinely broad (data ingestion, several independent astrophysical analyses, a provenance ledger, and a novelty check). It is borderline: a few tools (cross_band, wise_color, ir_excess) could arguably be folded into a single band/colour comparison tool without losing capability.
Coverage is strong: case creation, multi-survey data access, a full claim/hypothesis/prediction lifecycle with retraction and grading, plus blend/skeptic and prior-art checks. Minor gaps: no dedicated list_claims or list_hypotheses tool (only case_overview aggregates them) and no way to close/archive or delete a case.
Maintenance
Related MCP Connectors
Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP
214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.
Provenance and metadata tools for AI agents. Paid tools use x402 (USDC) at /mcp/<tool>.
Agent MCP: 65 tools — 5-chain verification, risk, prediction & crypto trends, 17 web tools.
Related MCP Servers
- AlicenseAqualityDmaintenanceA local MCP server for SkyPortal and Fritz that exposes astronomical transient data (photometry, spectra, classifications, observability) as tools for AI coding assistants.23BSD 3-Clause
- AlicenseBqualityDmaintenanceMCP server that provides tools to query 17+ astronomical databases (e.g., SIMBAD, VizieR, Gaia) via HTTP/TAP APIs, enabling AI applications to access astronomical data through natural language.2322 npm2BSD 3-Clause
- AlicenseNot gradedqualityBmaintenanceAn MCP server exposing IVOA-compliant astronomical archives (NOIRLab Astro Data Lab, NRAO/ALMA, CADC, ESO, Gaia, …) to LLM clients.34 PyPI5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query live NOAA and NASA solar storm feeds, compute deterministic geomagnetic risk scores, and verify hash-chained data seals through MCP tools.MIT