MCP.Market

Atmy air quality MCP server

online · 96% uptime
by atmy.ai·ai.atmy/air-quality·v1.1.0

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

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Atmy air quality yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Atmy air quality tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Atmy air quality compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Uptime
96%
of our recent checks; the typical remote server answers 100%
Response time
736 ms
faster than 18% of 30,031 servers

Release history: 2 versions in the registry since 2026-10-23, latest 2026-10-27, typically one every 4 days.

Install Atmy air quality in Claude Code, Cursor or VS Code

claude mcp add --transport http air-quality https://api.atmy.ai/mcp
Add to Cursor

Atmy air quality: common questions

Is Atmy air quality MCP server safe?
Mostly: it is graded B (78/100). Read the Atmy air quality safety report
How do I install Atmy air quality?
It runs remotely at api.atmy.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Atmy air quality need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Atmy air quality maintained?
The latest release is v1.1.0.
Is Atmy air quality up?
96% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Atmy air quality compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); uptime 96% (of our recent checks; the typical remote server answers 100%); response time 736 ms (faster than 18% of 30,031 servers). Full comparison.