Openaq
NPM · @PIPEWORX/MCP-OPENAQ · 2 COMPONENTS
OpenAQ MCP — global air-quality measurements via the OpenAQ v3 API.
Available components
Last scanned (9 hours ago)
Scores higher than 77% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-openaq). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 867 tokens (~216/item across 4 items; 4 tools + 0 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 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.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
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 · Analysed npm/@pipeworx/mcp-openaq@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-openaq |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-openaq/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3679842340 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cc4d89b3cafea7bf289ee618ae2ade3cbf8dbf64dccf588b27ba3c479bde1915802a4f239b4e81dded9b5c263ffefcea819d286e15b64542d7f1ffee3 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
air_quality_near ~181
Get the latest air-quality readings (PM2.5, PM10, O3, NO2, SO2, CO, etc.) at the monitoring station NEAREST to a latitude/longitude. PREFER for "air quality near me", "what is the air quality at <coordinates>", "is the air bad in <place> right now". Returns the nearest station with its most recent pollutant values, plus other nearby stations.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | OpenAQ API key (optional; the gateway supplies one). |
| latitude | number | yes | Latitude in decimal degrees (e.g., 40.785). |
| longitude | number | yes | Longitude in decimal degrees (e.g., -73.968). |
| radius_km | number | – | Search radius in km (default 12, max 25 — OpenAQ limit). |
No output schema declared.
No examples provided.
find_stations ~326
Find OpenAQ air-quality monitoring stations by location: a city or place name, coordinates+radius (nearest first), a country (ISO 3166-1 alpha-2 code), or a bounding box. Returns station id, name, country, coordinates, and the pollutants each measures (with sensor ids), plus resolved_place echoing the coordinates a city name resolved to. This is the first step for a historical series: find the station here, then pass its sensor_id to get_measurements. At least one location argument is required — the tool will not return an unfiltered global list.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | OpenAQ API key (optional; the gateway supplies one). |
| bbox | string | – | Bounding box "minLon,minLat,maxLon,maxLat" to search within. |
| city | string | – | City or place name, e.g. "Delhi", "Los Angeles", "Kraków". Geocoded to coordinates, then searched by radius. Add the country for ambiguous names ("Cambridge, UK"). |
| country | string | – | ISO 3166-1 alpha-2 country code (e.g. "US", "IN", "GB"). |
| latitude | number | – | Latitude for a radius search (use with longitude). |
| limit | number | – | Max stations to return (1-100, default 20). |
| longitude | number | – | Longitude for a radius search (use with latitude). |
| radius_km | number | – | Radius in km for a coordinate or city search (default 12, max 25). |
No output schema declared.
No examples provided.
get_latest ~102
Get the latest reading for every pollutant at a specific OpenAQ station (by location id from find_stations). Returns each parameter (PM2.5, O3, NO2, etc.) with its value, units, and measurement time.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | OpenAQ API key (optional; the gateway supplies one). |
| location_id | number | yes | OpenAQ location/station id (from find_stations or air_quality_near). |
No output schema declared.
No examples provided.
get_measurements ~205
Get the most recent time series (hourly or daily aggregates) for a single OpenAQ sensor (sensor id from find_stations), newest first. Use for pollutant trends over time at one station/parameter. Returns the sensor's LAST `limit` readings — note that many OpenAQ sensors are archived and stopped reporting years ago, so "most recent" can legitimately be several years old: always read the returned timestamps rather than assuming the data is current. Use find_stations or get_latest to pick a sensor that is still reporting.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | OpenAQ API key (optional; the gateway supplies one). |
| limit | number | – | How many of the most recent data points to return (1-1000, default 24). |
| period | string | – | Aggregation: "hours" (default) or "days". |
| sensor_id | number | yes | OpenAQ sensor id (a station+parameter pair, from find_stations). |
No output schema declared.
No examples provided.
How do I install the Openaq MCP server?
Openaq runs locally as an npm package, launched with npx -y @pipeworx/mcp-openaq. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-openaq
claude mcp add pipeworx-io-openaq -- npx -y @pipeworx/mcp-openaq
What is the Openaq MCP server?
Openaq is an MCP server listed in the public MCP registry as io.github.pipeworx-io/openaq. OpenAQ MCP, global air-quality measurements via the OpenAQ v3 API. This page covers its npm package (@pipeworx/mcp-openaq).
Is the Openaq MCP server safe to use?
Openaq scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Openaq MCP server expose?
Openaq exposes 4 tools: air_quality_near, find_stations, get_latest, get_measurements. Their descriptions and schemas cost roughly 814 tokens of context every time the server is loaded.
Is the Openaq MCP server still maintained?
Openaq 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.
What licence is the Openaq MCP server under?
Openaq declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Openaq MCP server?
VerifyMCP ran 15 checks on Openaq, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Openaq: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.