Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SmogRank

REMOTE · SMOGRANK.COM

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

Available components

+3 this week 68 Trust /100

Last scanned (18 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 680 tokens (~170/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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 62% 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 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
Changelog

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.

  • 17 Oct 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.

  • 15 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.

  • 14 Oct 26 0
    • Tool “city_air” rewrote its description, which is the text the model reads security
    • Server version: 1.1.0 → 1.2.0 functional
  • 13 Oct 26 0
    • Judged manipulation: unverified → pass ▲ security
    • Tool “city_air” rewrote its description, which is the text the model reads security
    • Server version: 1.0.0 → 1.1.0 functional
  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 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.

  • 9 Oct 26 64

    First indexed and scored.

Diagnostics

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 18 Oct 2026 · Probed https://smogrank.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=smogrank.com CN=WE1,O=Google Trust Services,C=US 30 Sept 2026 30 Dec 2026 ECDSA 256 ECDSA-SHA256 111e555bc01142df13fc5a87730e1735
SANs: smogrank.com, *.smogrank.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of smogrank.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
smogrank.com. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://smogrank.com/mcp Verified 200
http (plaintext) http://smogrank.com/mcp Inconclusive 405
MCP tools · 4 exposed · ~596 tokens

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 →

Tool Tokens
city_air ~223

PM2.5 now in a city: the latest hourly value, its 24-hour, 7-day, 30-day and year-to-date averages with its rank among all measured cities, the US EPA category, how it compares with the WHO guideline, and the "why it ranks here" notes (patterns in its own history and nearby fire, smoke and volcano evidence, named as likely causes, never confirmed), and the local hours its air was usually worst and cleanest over the last 30 days. Each measured city's trust says what stands behind it: checked (reference monitors at 2+ sites), one (a single reference site) or low (3+ low-cost sensors). Cities without a monitor get a model estimate, labelled as one, plus few_sensors when one or two low-cost sensors measure there (not ranked). No forecasts.

NameTypeReqDescription
citystringyesCity as its page path ("us/los-angeles"), a SmogRank URL, or a name ("Lahore", "Delhi, India"). find_city lists the paths.

No output schema declared.

No examples provided.

city_history ~119

A measured city's daily mean PM2.5 (its local calendar days, µg/m³) and its daily rank, between two dates (up to 400 days; default the last 30), with monthly means.

NameTypeReqDescription
citystringyesCity as its page path ("us/los-angeles"), a SmogRank URL, or a name ("Lahore", "Delhi, India"). find_city lists the paths.
fromstring–YYYY-MM-DD
tostring–YYYY-MM-DD, default yesterday

No output schema declared.

No examples provided.

find_city ~108

Search SmogRank's cities by name, or find the nearest ones to a point. Returns each city's path for the other tools, whether it is measured by ground monitors (ranked) or only estimated from a model, and its page.

NameTypeReqDescription
latnumber–Latitude, with lon, instead of a name.
limitinteger––
lonnumber––
querystring–City name, optionally with region or country: "Springfield, Illinois".

No output schema declared.

No examples provided.

rankings ~146

The ranking of measured cities by average PM2.5, worst first: a rolling window (24h, 7d, 30d, year to date) or a past period (a day 2026-09-30, a week 2026-W40, a month 2026-09, a year 2025). Optionally one country.

NameTypeReqDescription
countrystring–ISO country code, e.g. IN.
limitinteger––
orderstring––
periodstring–A past period instead of a window: YYYY-MM-DD, YYYY-Www, YYYY-MM or YYYY.
windowstring––

No output schema declared.

No examples provided.

Install

How do I install the SmogRank MCP server?

SmogRank is a hosted endpoint at https://smogrank.com/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 · smogrank.com

# add to Claude Code
claude mcp add --transport http burettosofuto-smogrank 'https://smogrank.com/mcp'
Common questions

What is the SmogRank MCP server?

SmogRank is an MCP server listed in the public MCP registry as io.github.BurettoSofuto/smogrank. PM2.5 air pollution by city: worst-first rankings, current air and daily history. This page covers its hosted endpoint (https://smogrank.com/mcp).

Is the SmogRank MCP server safe to use?

SmogRank scores 68 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 SmogRank MCP server expose?

SmogRank exposes 4 tools: find_city, city_air, city_history, rankings. Their descriptions and schemas cost roughly 596 tokens of context every time the server is loaded.

Does the SmogRank MCP server require authentication?

No. We connected to SmogRank without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SmogRank MCP server still maintained?

SmogRank is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.