# NASA Asteroids MCP

> NASA Asteroids — Near-Earth Objects & Planetary Defense connects your AI agent directly to NASA and JPL's astronomical databases. It lets you track known near-Earth asteroids, monitor upcoming close approaches, and analyze historical fireball impact data in real time. You can browse the complete catalog, check specific objects by ID, or filter for potential hazards based on date ranges.

## Overview
- **Category:** the-unthinkable
- **Price:** Free
- **Tags:** asteroid-tracking, near-earth-objects, space-weather, planetary-science, hazard-assessment

## Description

This server hooks your AI agent directly into NASA and JPL’s deep-cut astronomical databases. It lets you track everything about Near-Earth Objects (NEOs), monitor upcoming planetary hazards, and analyze historical impact data in real time. You're getting the full picture on cosmic threats.

To find a single asteroid's profile, run `get_neo_lookup` and supply its unique NASA SPK-ID; this instantly pulls comprehensive data for that specific near-Earth object.

Want to browse the whole shebang? Use `get_neo_browse` to check out the complete catalog of known NEOs. This tool returns results in paginated batches, keeping your request manageable even when dealing with massive datasets.

For monitoring immediate threats, you've got two tools. First, use `get_neo_feed` if you want a live stream of NEOs approaching within a specific date range; this feed details their hazard status and velocity right off the bat. If you need to focus on potential impacts in the future, deploy `get_close_approaches`. This function filters expected Earth encounters from JPL CNEOS based on required distance thresholds and minimum asteroid size parameters.

For historical analysis, check out `get_fireballs`. This tool retrieves detailed records of atmospheric bolide events—basically, fireballs—that the US government sensors detected. The results include precise location data and an estimate of the energy output, measured in kilotons of TNT equivalent. You can pull these past impact reports to gauge historical hazard rates.

## Tools

### get_close_approaches
Filters future close passes of asteroids using date ranges, distance thresholds, and minimum size for defense monitoring.

### get_fireballs
Retrieves detailed records of atmospheric bolide events detected by US government sensors, including energy and location.

### get_neo_browse
Browses the complete catalog of known near-Earth objects, returning results in paginated batches.

### get_neo_feed
Gets a feed of NEOs approaching within a specified date range, detailing hazard status and velocity.

### get_neo_lookup
Retrieves comprehensive data for one specific near-Earth object using its NASA SPK-ID.

## Prompt Examples

**Prompt:** 
```
What asteroids are passing near Earth this week?
```

**Response:** 
```
☄️ **Near-Earth Objects This Week**

| Asteroid | Size (m) | Distance (km) | Speed (km/s) | Hazardous |
|----------|----------|---------------|-------------|----------|
| 2024 AA1 | 45-100 | 4,200,000 | 12.3 | No |
| 2023 BX5 | 150-340 | 1,800,000 | 18.7 | ⚠️ Yes |
| 2024 CD2 | 22-50 | 6,500,000 | 8.1 | No |

14 NEOs this week, 1 potentially hazardous.
```

**Prompt:** 
```
Are there any large asteroids approaching Earth next month?
```

**Response:** 
```
Next month, the most significant close approach is by asteroid 2001 FO32, which has an estimated diameter of 550 meters. It will pass safely at a distance of 5 lunar distances (about 1.25 million miles).
```

**Prompt:** 
```
Tell me about the recent fireball detected over the Pacific.
```

**Response:** 
```
A significant fireball was detected by government sensors over the central Pacific Ocean yesterday. The calculated total radiated energy suggests it was a small bolide roughly 2 meters in size that burned up completely in the upper atmosphere.
```

## Capabilities

### Track asteroid hazard feeds
Retrieve a list of Near-Earth Objects approaching within your specified date range, including their estimated size and if they are flagged as hazardous.

### Identify future close passes
Filter for expected Earth encounters from JPL CNEOS based on required distance thresholds and minimum asteroid size.

### Search the full NEO catalog
Browse all known near-Earth objects, receiving results in batches of 20 records per request.

### Get detailed object profiles
Look up a single asteroid's complete data set using its unique NASA SPK-ID.

### Review atmospheric impact history
Pull records of recorded fireballs (bolides) detected by government sensors, including location and estimated energy output.

## Use Cases

### Investigating a specific orbital threat.
A risk analyst needs data on Asteroid 2014 AB. They don't want general results; they need specifics. The agent runs `get_neo_lookup` using the known SPK-ID, instantly pulling its full orbit, size metrics, and velocity details for a targeted report.

### Preparing for quarterly hazard reviews.
The defense team must know what's coming in Q3. They instruct their agent to run `get_neo_feed` for the next three months. The agent processes the list, flagging all objects that meet a minimum size threshold and are marked as potentially hazardous.

### Modeling meteor strike risk.
A geophysicist wants to analyze regional vulnerability based on past events. They use `get_fireballs` to pull records of recent bolides over the Pacific, analyzing the energy (kilotons) and location data to refine impact models.

### Getting an overview of all known objects.
A researcher needs a broad dataset. They use `get_neo_browse` to pull the first 20 records, then prompt the agent to iterate through pages until they hit the limit, building a full inventory list for comparison.

## Benefits

- You get immediate hazard status checks. Instead of manually reading pages, running `get_neo_feed` provides a direct list of approaching NEOs with their estimated diameter and if they are potentially hazardous.
- Deep dive into specific objects is simple. Use `get_neo_lookup` with an SPK-ID to pull every data point on one asteroid without leaving your agent's context.
- Planetary defense planning is streamlined by `get_close_approaches`. You set the parameters—distance, date range—and it filters only the most relevant future encounters from JPL CNEOS.
- Historical event analysis moves fast. Running `get_fireballs` pulls documented atmospheric impacts (bolides) worldwide, giving you immediate data on energy and location for modeling purposes.
- You never get lost in the catalog. Instead of browsing hundreds of pages, `get_neo_browse` lets your agent pull records efficiently, page by page, to build a comprehensive inventory.

## How It Works

The bottom line is: you pass criteria (date range, size, ID), and it returns verified orbital and impact data from global space agencies.

1. You tell your agent exactly what you're looking for—for instance, 'show me all asteroids between 2025-1 and 2025-3 that are bigger than 1km.'
2. The agent selects the appropriate tool (`get_close_approaches` or `get_neo_feed`) and passes the specific parameters (dates, sizes) to the server.
3. The server executes the request against NASA/JPL databases and returns a structured list of asteroid data, detailing size, velocity, and hazard status.

## Frequently Asked Questions

**How do I find out about asteroids passing Earth next year using get_close_approaches?**
You call `get_close_approaches` and pass the start and end dates for the required time frame. You can also filter by a minimum size threshold to focus only on larger, more relevant objects.

**What data does get_fireballs provide about past impacts?**
`get_fireballs` gives you records of atmospheric bolides detected worldwide. The results include the location, velocity, and estimated energy (kilotons of TNT equivalent) from US government sensors.

**If I know an asteroid's ID, which tool should I use? Should I use get_neo_lookup?**
Yes, if you have the specific NASA SPK-ID, always use `get_neo_lookup`. It gives the most comprehensive profile for that single object and is more direct than browsing the general catalog.

**How do I get a list of all known asteroids to start my research?**
Use `get_neo_browse` to access the full, paginated catalog of near-Earth objects. It returns 20 records at a time, so your agent will need to loop through pages to see everything.

**How do I handle rate limits when using get_neo_browse for large data sets?**
You must respect the API's established request quotas. If you hit a limit, implement an exponential backoff strategy and pause calls to avoid errors. The server handles pagination automatically if you manage your requests within the allowed window.

**Can I use get_neo_feed to filter for asteroids that meet both a specific size threshold and date range?**
Yes, you can combine filtering parameters in the `get_neo_feed` call. Specify both the minimum estimated diameter and the required start/end dates. This narrows down potential hazards quickly.

**If I use get_neo_lookup with an expired or incorrect SPK-ID, what response should I expect?**
You will receive a standard API error, typically indicating that the requested ID was not found. Check the documentation for specific HTTP status codes (like 404) to confirm data validity.

**What is the practical difference between using get_neo_feed and getting details via get_neo_lookup?**
The `get_neo_feed` returns a summary list of many objects, including general hazard assessments. The `get_neo_lookup`, however, gives you deep, comprehensive data points for one specific asteroid ID.

**What does 'potentially hazardous' mean?**
A Potentially Hazardous Asteroid (PHA) passes within 0.05 AU (~7.5 million km) and is larger than 140 meters. This doesn't mean it will hit Earth — just that its orbit warrants monitoring.

**How frequently is the asteroid data updated?**
The NeoWs API is updated daily with the latest orbital calculations and close approach tracking data from JPL's Center for Near Earth Object Studies.

**Does this API include data on historical asteroid impacts?**
Yes, the API provides access to fireball and bolide data, which tracks bright atmospheric meteor events detected by government sensors, including historical records.