Is Openaq MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highRemote endpoint did not respond — TypeError: fetch failed
How Openaq compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 64/100
- higher than 19% of 48,255 servers
- Uptime
- 0%
- of our recent checks; the typical remote server answers 100%
Release history: 5 versions in the registry since 2026-08-25, latest 2026-09-26, typically one every 3 days.
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
1 high
- Code scan40 source files scanned; 40 source files scanned25/25
- Live reliabilityremote unreachable: TypeError: fetch failed0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 5 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableTypeError: fetch failed
Overall 64/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON