# Emissions API MCP

> Emissions API lets your AI agent audit air quality and track specific gas concentrations using satellite data. Query historical or real-time measurements for pollutants like methane, ozone, carbon monoxide, and nitrogen dioxide across any country or custom geographic area.

## Overview
- **Category:** data-analytics
- **Price:** Free
- **Tags:** environmental-monitoring, satellite-data, air-quality, carbon-emissions, climate-data, gas-tracking

## Description

This MCP gives your agent the ability to run an environmental analysis that used to require a dedicated GIS professional and hours of manual portal work. Instead of downloading messy CSVs from different governmental sites—one for CO, another for CH4, and a third just for coordinates—you talk to your AI client. Your agent handles the complex cross-referencing, pulling data points like carbon monoxide or methane levels for specific countries or defined regions instantly. Whether you're running climate research or checking local industrial impact, your agent acts as an environmental analyst on demand, ensuring every piece of data comes from precise, satellite-derived measurements. You access this full suite of tools through the Vinkius catalog and simply ask a question in natural language.

## Tools

### get_carbon_monoxide
Retrieves specific emission data points for carbon monoxide across different locations and times.

### get_geojson_emissions
Pulls emission measurements formatted in GeoJSON, which lets you maintain precise control over the geographic boundaries of your data.

### get_methane
Gathers specific emission readings for methane gas across specified regions or date ranges.

### get_nitrogen_dioxide
Provides data points tracking nitrogen dioxide emissions, useful for industrial impact assessments.

### get_ozone
Retrieves emission levels of ozone gas to track atmospheric composition changes.

### get_available_products
Lists every gas product the system tracks, helping you figure out what markers are available for research.

## Prompt Examples

**Prompt:** 
```
What is the latest carbon monoxide level in Germany (DE)?
```

**Response:** 
```
I've retrieved the measurement for Germany. The latest value is approximately 0.03 mol/m². The timestamp associated with this satellite reading is from yesterday. Would you like the data for other regions?
```

**Prompt:** 
```
List all available gas products in the Emissions API.
```

**Response:** 
```
I've scanned the catalog. Available products include carbonmonoxide, methane, ozone, and nitrogendioxide. I can retrieve emission data for any of these markers.
```

**Prompt:** 
```
Show methane emission trends for the last 30 days in the US.
```

**Response:** 
```
I've retrieved the methane levels for the US over the requested period. The values range from 1800 to 1900 ppb. I can provide a summary of the peak days if you'd like.
```

## Capabilities

### Query Specific Pollutants
Get real-time or historical emission data for designated gases like methane, ozone, or carbon monoxide.

### Define Geographic Boundaries
Retrieve gas measurements confined to specific country codes or custom GeoJSON coordinates.

### Track Changes Over Time
Check how pollutant concentrations shift over defined date ranges, spotting trends and spikes.

### Identify Available Markers
List all gas products the API tracks so you know what data points are available for analysis.

## Use Cases

### Monitoring Industrial Impact
A consultant needs to see if industrial activity in the Midwest changed ozone levels last quarter. They ask their agent, 'Show me Ozone and Carbon Monoxide data for this specific polygon from Q2.' The agent uses `get_ozone` and `get_carbon_monoxide` with GeoJSON boundaries, delivering a direct comparison.

### Comparative Climate Modeling
A scientist wants to compare the historical methane levels of two different countries. They ask their agent to run a time-series query for `get_methane`, allowing them to model regional differences without manual data exports.

### Policy Compliance Check
A policy maker needs to verify if nitrogen dioxide levels exceeded regional limits last year. They use the agent to pull historical data via `get_nitrogen_dioxide` for a specific country and date range, generating an immediate audit report.

### Initial Data Discovery
A student is starting research on atmospheric pollution. They first run `get_available_products` to see all markers (CO, CH4, etc.) before deciding which specific gases they need to track over time.

## Benefits

- Audit Pollutants Easily: Instead of running separate queries for every gas, you can check CO, CH4, and O3 levels in one conversational prompt.
- Pinpoint Geography: Use the `get_geojson_emissions` tool to constrain your data retrieval strictly to custom coordinates, bypassing whole-country averages.
- Spot Trends Over Time: Track how pollution shifts over years or months by querying specific date ranges for any gas, like methane levels.
- Know Your Scope First: Run `get_available_products` early on. This list tells you exactly which markers are available before you waste time trying to query non-existent gases.
- Centralized Data Access: You get satellite-derived measurements without ever needing an API key or touching a technical portal.

## How It Works

The bottom line is you stop managing APIs; you just ask your agent what environmental metrics you need to see.

1. First, ask your agent to identify which gases or geographic areas need auditing.
2. Next, your agent calls the necessary tools—for example, combining `get_methane` with a regional query for Ozone data.
3. You get back synthesized results: clean measurements and trends in natural language, ready for analysis.

## Frequently Asked Questions

**Is an API Key required for Emissions API?**
No. Emissions API is a free and open service. This server works out of the box without any static credentials required.

**What gases can be audited via the agent?**
You can query Carbon Monoxide (`carbonmonoxide`), Methane (`methane`), Ozone (`ozone`), and Nitrogen Dioxide (`nitrogendioxide`) using specialized tools.

**Is the data historical or real-time?**
The API provides historical measurement data collected by the Sentinel-5P satellite, typically updated daily with a short processing lag.

**When should I use the `get_geojson_emissions` tool for my research?**
Use this tool when you need precise geographic boundaries or spatial mapping. It returns emission measurements in GeoJSON format, which is ideal for plotting pollution data directly onto a map without manual conversion.

**How do I determine all the gas products available using `get_available_products`?**
The agent executes the `get_available_products` tool to pull a complete catalog of every measurable marker. This list lets you know exactly which gases, like ozone or methane, are ready for analysis.

**If I need to compare multiple pollutants, how do I structure the query between `get_methane` and `get_ozone`?**
You instruct your agent to run both tools sequentially within one request. The system handles coordinating parameters like date ranges or countries across different pollutant reads for comparison.

**What format should I provide coordinates when calling the `get_carbon_monoxide` tool?**
The tool expects specific geographic inputs, usually latitude and longitude pairs, or standard ISO country codes. Always confirm your location data type to get accurate readings.

**Are there rate limits I should be aware of when querying this MCP for large datasets?**
Because Emissions API is a public service, the focus is on efficient query design. Breaking complex requests into smaller, targeted calls generally ensures stable performance and successful data retrieval.