Atmy air quality
REMOTE · API.ATMY.AI · 2 COMPONENTS
PM2.5 of 300+ cities: now, history, forecast, rankings; 12 000 sensors with a quality rating.
Available components
Last scanned (2 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2019 tokens (~155/item across 13 items; 11 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.4.0 → 1.5.0 functional
- “find_sensors” reworded the description of “city” cosmetic
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 88% → 74% ▼ functional
- Schema quality: 1303 → 1980 ▼ functional
- Server version: 1.2.0 → 1.4.0 functional
- New tool “find_sensors” functional
- New tool “get_sensor” functional
- New tool “get_sensor_readings” functional
- New tool “get_sensors_average” functional
- New tool “list_sensor_networks” functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_air_quality” rewrote its description, which is the text the model reads security
- Tool “get_air_quality_history” rewrote its description, which is the text the model reads security
- Schema quality: 127 → 162 ▼ functional
- Server version: 1.0.0 → 1.2.0 functional
- New tool “get_air_quality_monthly” functional
- “get_air_quality_history” added an optional parameter “from” cosmetic
- “get_air_quality_history” added an optional parameter “to” cosmetic
- “get_air_quality_history” reworded the description of “days” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.atmy.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=atmy.ai | CN=YE2,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5dac9b0b0efcaf5308b9a06ad75d5460f21 |
| SANs: *.atmy.ai, atmy.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.atmy.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| atmy.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15768000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.atmy.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.atmy.ai/mcp | HTTPS enforced | 301 | https://api.atmy.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_sensors Find sensors ~251
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Any city or town: a name in any language, a slug like "serbia/belgrade" or the Atmy city id; also towns without an Atmy summary. |
| country | string | – | Country slug, the first part of a city slug, e.g. "serbia". |
| lat | number | – | With lon: sensors within radius_km of this point. |
| limit | integer | – | – |
| lon | number | – | – |
| min_rating | number | – | Only sensors with at least this rating on their last checked day. |
| network | string | – | – |
| page | integer | – | – |
| quality | string | – | passed: only sensors that pass the quality check. |
| radius_km | number | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
get_air_quality Current air quality ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name in any of the site languages, a slug like "russia/krasnoyarsk", or the Atmy city id. |
| country | string | – | Country name, to tell apart cities with the same name. |
| lang | string | – | Language of city and country names and of the page link; default en. |
| lat | number | – | Latitude; with lon, the nearest city with an Atmy summary within 50 km. |
| lon | number | – | Longitude. |
No output schema declared.
No examples provided.
get_air_quality_history Daily air quality history ~268
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name in any of the site languages, a slug like "russia/krasnoyarsk", or the Atmy city id. |
| country | string | – | Country name, to tell apart cities with the same name. |
| days | integer | – | How many days back from the last completed day; ignored with from/to. |
| from | string | – | First day YYYY-MM-DD (2017-01-01 or later). |
| lang | string | – | Language of city and country names and of the page link; default en. |
| lat | number | – | Latitude; with lon, the nearest city with an Atmy summary within 50 km. |
| lon | number | – | Longitude. |
| to | string | – | Last day YYYY-MM-DD; default the last completed day. |
No output schema declared.
No examples provided.
get_air_quality_monthly Monthly air quality history ~185
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".
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name in any of the site languages, a slug like "russia/krasnoyarsk", or the Atmy city id. |
| country | string | – | Country name, to tell apart cities with the same name. |
| lang | string | – | Language of city and country names and of the page link; default en. |
| lat | number | – | Latitude; with lon, the nearest city with an Atmy summary within 50 km. |
| lon | number | – | Longitude. |
No output schema declared.
No examples provided.
get_city_forecast Weather and pollution accumulation forecast ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name in any of the site languages, a slug like "russia/krasnoyarsk", or the Atmy city id. |
| country | string | – | Country name, to tell apart cities with the same name. |
| hours | integer | – | – |
| lang | string | – | Language of city and country names and of the page link; default en. |
| lat | number | – | Latitude; with lon, the nearest city with an Atmy summary within 50 km. |
| lon | number | – | Longitude. |
No output schema declared.
No examples provided.
get_country_ranking Country ranking ~122
Cities of a country ranked by daily PM2.5 for the last completed day (Atmy Data Hub), most polluted or cleanest first.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Country name in any site language or the ISO code, e.g. "Russia", "Сербия", "DE". |
| lang | string | – | Language of city and country names and of the page link; default en. |
| limit | integer | – | – |
| order | string | – | – |
| settlements | string | – | Large cities only, or every settlement with enough sensors. |
No output schema declared.
No examples provided.
get_sensor One sensor ~45
One sensor by its id: location, network, license, quality check with rating and reasons, and the latest reading.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Sensor id from find_sensors. |
No output schema declared.
No examples provided.
get_sensor_readings Sensor readings ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO 8601 date or time, UTC. |
| id | integer | yes | – |
| interval | string | – | – |
| to | string | – | ISO 8601 date or time, UTC; default now. |
No output schema declared.
No examples provided.
get_sensors_average Mean of a group of sensors ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO 8601 date or time, UTC. |
| ids | array | yes | – |
| interval | string | – | – |
| to | string | – | ISO 8601 date or time, UTC; default now. |
No output schema declared.
No examples provided.
list_sensor_networks Sensor networks ~44
The sensor networks in Atmy (Sensor.Community, AirGradient, Atmy) with their number of sensors, how many pass the quality check, and their license.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_cities Search cities ~94
Find the cities with an Atmy air-quality summary by name (any language) or country. Returns slugs to pass to the other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country name or ISO code. |
| lang | string | – | Language of city and country names and of the page link; default en. |
| limit | integer | – | – |
| query | string | – | Part of the city name in any site language. |
No output schema declared.
No examples provided.
How do I install the Atmy air quality MCP server?
Atmy air quality is a hosted endpoint at https://api.atmy.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.atmy.ai
claude mcp add --transport http ai-atmy-air-quality 'https://api.atmy.ai/mcp'
What is the Atmy air quality MCP server?
Atmy air quality is an MCP server listed in the public MCP registry as ai.atmy/air-quality. PM2.5 of 300+ cities: now, history, forecast, rankings; 12 000 sensors with a quality rating. This page covers its hosted endpoint (https://api.atmy.ai/mcp).
Is the Atmy air quality MCP server safe to use?
Atmy air quality scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Atmy air quality MCP server expose?
Atmy air quality exposes 11 tools: search_cities, get_air_quality, get_air_quality_history, get_air_quality_monthly, get_city_forecast, and 6 more. Their descriptions and schemas cost roughly 1,621 tokens of context every time the server is loaded.
Does the Atmy air quality MCP server require authentication?
No. We connected to Atmy air quality without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Atmy air quality MCP server still maintained?
Atmy air quality is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.