mcpbeat Sign in

Atmy air quality MCP Server

answering

Atmy air quality is answering right now. Last checked 3 min ago. 673 installs a week from npm. It exposes 11 tools.

PM2.5 of 300+ cities: now, history, forecast, rankings; 12 000 sensors with a quality rating.

Installs per day peak 250 · avg 12
a month agotoday
Uptime history 10 days of history · worst day 0%
10 days agonow
100.0%
Uptime 24h
91 of 91 checks
11
Tools
read from the server
215 ms
Response time
average over 24h
673
Installs / week
npm and PyPI

What changed 13

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 October 2026. No other catalogue keeps this.

31 Oct a tool changed the parameters it asks for find_sensors
31 Oct a tool changed version
27 Oct 5 tools appeared find_sensors, get_sensor, get_sensor_readings and 2 more
27 Oct 2 tool descriptions were rewritten get_sensor_readings, get_sensors_average
27 Oct 2 tools changed the parameters they ask for get_sensor_readings, get_sensors_average
27 Oct a tool changed version2 times that day
and 1 more, back to 27 October 2026

Nothing serious here today

Today is the operative word: we check Atmy air quality every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add air-quality --transport http https://api.atmy.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.atmy.ai/mcp
~/.codex/config.toml
[mcp_servers.air-quality]
url = "https://api.atmy.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "air-quality": {
      "url": "https://api.atmy.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "air-quality": {
      "type": "http",
      "url": "https://api.atmy.ai/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

air
get_air_quality
PM2.5 now in a city (mean of the latest reading of each eligible sensor, at most 60 minutes old) with its US EPA category and the weather now (temperature, humidity, pressure, wind, clouds, precipitation), plus the last completed day from the Atmy Data Hub with its weather. Pass city or lat/lon.
get_air_quality_history
Daily PM2.5 of a city from the Atmy Data Hub (UTC days, sensors after the quality check) with the day's weather from 2026-01-19 (mean, lowest and highest temperature, humidity, pressure, wind, strongest gust, clouds): the last days, or any period since 2017 with from/to, at most 400 days per call. For the whole history or records use get_air_quality_monthly first.
get_air_quality_monthly
The whole measurement history of a city from the Atmy Data Hub: PM2.5 per month with the month's weather from 2026-01, yearly means (complete years marked), the dirtiest and cleanest months and days. For questions like "how has the air changed" or "the most polluted month on record".
sensor
get_sensor
One sensor by its id: location, network, license, quality check with rating and reasons, and the latest reading.
get_sensor_readings
Readings of one sensor: raw (the last 31 days, at most 7 days a call), 5-minute means (the same windows), hourly means (the last 366 days, at most 92 days a call) or daily means (UTC days of the last 366 days, with the quality check of each day). Default: the last 24 hours, or 30 days by day. Times are UTC.
list_sensor_networks
The sensor networks in Atmy (Sensor.Community, AirGradient, Atmy) with their number of sensors, how many pass the quality check, and their license.
sensors
find_sensors
Single sensors with their latest reading (PM1, PM2.5, PM10, temperature, humidity, pressure), network and quality check: status, rating 0–10 of the last checked day, the mean rating of the last 7 days and the reasons. Filter by city, country, or a point with a radius; sort=rating puts the most reliable sensors first.
get_sensors_average
The mean of up to 100 sensors per 5 minutes, hour or UTC day, each sensor counted once per bucket, with the number of sensors in each bucket. Windows as in get_sensor_readings; by day at most 92 days a call.
cities
search_cities
Find the cities with an Atmy air-quality summary by name (any language) or country. Returns slugs to pass to the other tools.
city
get_city_forecast
The next hours of a city: temperature, wind, humidity, precipitation and the pollution accumulation index 0–100 (how strongly the weather keeps particles near the ground). A weather estimate, not a PM2.5 forecast.
country
get_country_ranking
Cities of a country ranked by daily PM2.5 for the last completed day (Atmy Data Hub), most polluted or cleanest first.

Endpoints

URLTransportStateLatencyChecked
https://api.atmy.ai/mcp streamable-http answering 189 ms 3 min ago

Alternatives to Atmy air quality

same job, measured the same way
SmogRank
by burettosofuto

PM2.5 air pollution by city: worst-first rankings, current air and daily history.

4 tools answering
air-Q
by corantgmbh

MCP server for direct HTTP communication with air-Q air quality sensor devices

123 installs/wk local only
CleanAirData
by chenweilie

Historical PM2.5 and Clean Air Score for US cities; copied records name their source city.

3 tools answering
Open Meteo MCP Server
by cyanheads

Global weather via Open-Meteo: forecast, historical, marine, air quality, geocoding, elevation.

984 installs/wk 11 tools answering
Fermi
by kromatic-innovation

Calibrated probability ranges for forecasting questions, with the assumptions behind them.

6 tools answering
EM Snow
by co-extreme-media-snow

Ski resort conditions, forecasts, avalanche danger, sun, routes and snow history for 5,000+ resorts.

21 tools answering
Live weather and air quality (GAIA)
by modelmarket

Weather, air quality and nearest live sensors anywhere, each with a signed receipt. Free, no key.

3 tools answering
Dim Hour
by dimhour

Search 19,000+ verified places to eat and drink across 24 cities, each with a 0-100 quality score.

9 tools answering

Atmy air quality — questions

Answers built from our own checks of this server.

What can Atmy air quality do?
It exposes 11 tools, read directly from the server on our last check. Among them: find_sensors, get_air_quality, get_air_quality_history, get_air_quality_monthly, get_city_forecast, get_country_ranking and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Atmy air quality mostly used for?
Its tools cluster around air, sensor and sensors. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Atmy air quality working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 215 ms. The bar chart above shows every period we have measured.
How do I connect Atmy air quality?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Atmy air quality need an API key?
No. Atmy air quality completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Atmy air quality?
It answers our handshake in 215 ms on average, which is faster than 66% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Atmy air quality?
The npm package atmy-mcp was installed 673 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.