Hermes — Air Quality Intelligence
REMOTE · HERMES.SOUTHLONDONSCIENTIFIC.COM · SCANNED SEP 25
UK air quality MCP: live readings, historical trends, LAQM stats, WHO checks, knowledge base.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3040 tokens (~202/item across 15 items; 15 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
How do I install the Hermes — Air Quality Intelligence MCP server?
Hermes — Air Quality Intelligence is a hosted endpoint at https://hermes.southlondonscientific.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 · hermes.southlondonscientific.com
claude mcp add --transport http com-southlondonscientific-hermes 'https://hermes.southlondonscientific.com/mcp'
{
"mcpServers": {
"com-southlondonscientific-hermes": {
"url": "https://hermes.southlondonscientific.com/mcp"
}
}
} {
"servers": {
"com-southlondonscientific-hermes": {
"type": "http",
"url": "https://hermes.southlondonscientific.com/mcp"
}
}
} [mcp_servers.com-southlondonscientific-hermes] url = "https://hermes.southlondonscientific.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-southlondonscientific-hermes": {
"type": "remote",
"url": "https://hermes.southlondonscientific.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-southlondonscientific-hermes --url 'https://hermes.southlondonscientific.com/mcp' --transport streamable-http
mcp_servers:
com-southlondonscientific-hermes:
url: "https://hermes.southlondonscientific.com/mcp" {
"McpServers": {
"com-southlondonscientific-hermes": {
"Transport": "http",
"Url": "https://hermes.southlondonscientific.com/mcp"
}
}
} assistant mcp add com-southlondonscientific-hermes -t streamable-http -u 'https://hermes.southlondonscientific.com/mcp'
{
"mcpServers": {
"com-southlondonscientific-hermes": {
"type": "http",
"url": "https://hermes.southlondonscientific.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Server version: 1.27.1 → 1.30.0 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 25 Sept 2026 · Probed https://hermes.southlondonscientific.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hermes.southlondonscientific.com | CN=YE1,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 517432cbe1c7d81113f46269eaba008ec97 |
| SANs: hermes.southlondonscientific.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 hermes.southlondonscientific.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| southlondonscientific.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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hermes.southlondonscientific.com/mcp | Verified | 200 | |
| http (plaintext) | http://hermes.southlondonscientific.com/mcp | HTTPS enforced | 308 | https://hermes.southlondonscientific.com/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 →
assess_location_aq ~170
Comprehensive air quality assessment for a location in one call. Combines nearby monitor discovery and current readings with DAQI into a single response. Use this as the first tool call for any air quality question about a location. For long-term trend analysis, use the dedicated `trend_analysis` tool. Returns a structured 'summary' dict with purpose-appropriate sections. Present the summary description to users first. Args: location: Postcode, place name, or "lat,lon". purpose: What the user needs — "general" (default), "health" (safety/worry), "exercise" (outdoor activity), or "planning" (homebuying/school assessment/long-term).
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | – |
| purpose | string | – | – |
No output schema declared.
No examples provided.
chart_aq_trend ~276
Generate a time series chart of air quality data. Returns a PNG chart image with a brief text summary. Use this when users ask about trends, patterns, or want to visualise air quality over time. Args: start_date: Start date (ISO format, e.g. "2025-01-01"). end_date: End date (ISO format). location: Postcode, place name, or "lat,lon". Provide this or site_code. site_code: Direct site code. Provide this or location. pollutants: Optional filter, e.g. ["NO2", "PM2.5"]. Defaults to NO2, PM2.5, PM10, O3 if not specified. frequency: "hourly", "daily", or "monthly" (default "daily"). show_who_guidelines: Show WHO guideline reference lines (default True). show_daqi_bands: Show DAQI band background shading (default True).
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| frequency | string | – | – |
| location | – | – | – |
| pollutants | – | – | – |
| show_daqi_bands | boolean | – | – |
| show_who_guidelines | boolean | – | – |
| site_code | – | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
compare_locations ~111
Compare current air quality across multiple locations side-by-side. Returns a ranked comparison by pollutant with DAQI bands and distance to nearest monitor. Useful for comparing development sites, school locations, or residential options. Args: locations: List of 2–6 locations (postcodes, place names, or "lat,lon"). pollutants: Optional filter, e.g. ["NO2", "PM2.5"]. Default: all available.
| Name | Type | Req | Description |
|---|---|---|---|
| locations | array | yes | – |
| pollutants | – | – | – |
No output schema declared.
No examples provided.
get_aqi_summary ~153
Get an AQI assessment with health advice and WHO compliance check. Returns a 'summary' with a plain-English health assessment, advice for general and at-risk populations, and WHO guideline context. Present the summary to users first. Also returns raw 'aqi' and 'who_compliance' data. Args: location: Postcode, place name, or "lat,lon". index: AQI system — "UK_DAQI" (default), "WHO", or "US_EPA". period: "current", "today", "this_week", or "this_month".
| Name | Type | Req | Description |
|---|---|---|---|
| index | string | – | – |
| location | string | yes | – |
| period | string | – | – |
No output schema declared.
No examples provided.
get_current_aq ~173
Get the most recent air quality readings near a location, with health context. Returns a 'summary' with a plain-English health assessment and advice for general and at-risk populations. Present the summary to users first. Also returns individual 'readings' from nearby monitors and 'metadata' about data freshness and sources. Args: location: Postcode, place name, or "lat,lon". radius_km: Search radius in kilometres (default 2.0). pollutants: Optional filter, e.g. ["NO2", "PM2.5"]. sources: Optional filter, e.g. ["AURN", "BREATHE_LONDON"].
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | – |
| pollutants | – | – | – |
| radius_km | number | – | – |
| sources | – | – | – |
No output schema declared.
No examples provided.
get_historical_aq ~216
Get historical air quality data for a site or location, with health context. Returns a 'narrative' with plain-English interpretation of trends, WHO guideline exceedances, and guideline comparisons. Present the narrative to users first. Also returns raw 'data' and 'summary' statistics. Args: start_date: Start date (ISO format, e.g. "2025-01-01"). end_date: End date (ISO format). location: Postcode, place name, or "lat,lon". Provide this or site_code. site_code: Direct site code. Provide this or location. pollutants: Optional filter, e.g. ["NO2", "PM2.5"]. frequency: "hourly", "daily", or "monthly" (default "daily").
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| frequency | string | – | – |
| location | – | – | – |
| pollutants | – | – | – |
| site_code | – | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
kb_get_guidelines ~73
Get current air quality guideline and target values. Args: framework: "WHO", "UK", "EU", or "all" (default). pollutant: Optional filter for a specific pollutant. Returns the full guidelines document (markdown).
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | – |
| pollutant | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
kb_get_health_effects ~106
Get health evidence summaries for a pollutant and population group. Args: pollutant: "NO2", "PM2.5", "PM10", or "O3". population_group: "general", "children", "elderly", "respiratory", "cardiovascular", or "pregnant" (default "general"). Returns health effects document (markdown).
| Name | Type | Req | Description |
|---|---|---|---|
| pollutant | string | yes | – |
| population_group | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
kb_get_local_context ~49
Get area-specific contextual information. Args: area: "southwark", "london", or a specific neighbourhood. Returns local context document (markdown).
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
kb_get_monitoring_explainer ~87
Get plain-language explanations of monitoring methods and limitations. Args: topic: One of "how_monitors_work", "regulatory_vs_lowcost", "what_readings_mean", "why_numbers_differ", "representativeness", "data_quality", "what_monitors_measure". Returns monitoring explainer document (markdown).
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
kb_get_practical_advice ~179
Generic protective-action guidance for a category of situation (NOT keyed to an individual user's context). For *personalised* advice that takes the user's specific health situation into account (asthma, pregnancy, gas cooker, tube commute, indoor sources), prefer the Clara MCP server's `contextual_advice` tool — it composes Hermes live readings with personal context to give an answer keyed to *this* user, *now*. Use this KB tool only as a fallback or when Clara is not available. Args: situation: One of "high_pollution_day", "commuting", "exercise", "school_run", "indoor_air", "planning_objection", "pregnancy", "child_asthma". Returns practical advice document (markdown).
| Name | Type | Req | Description |
|---|---|---|---|
| situation | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_monitors ~141
List air quality monitoring sites near a location, with context. Returns a 'summary' explaining how many monitors were found, their operational status, and what each monitor type represents. Present the summary to users first. Also returns a 'monitors' list with full metadata. Args: location: Postcode, place name, or "lat,lon". radius_km: Search radius in kilometres (default 5.0). sources: Optional filter, e.g. ["AURN", "BREATHE_LONDON"].
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | – |
| radius_km | number | – | – |
| sources | – | – | – |
No output schema declared.
No examples provided.
regulatory_stats ~123
Get LAQM Annual Status Report-style statistics for a location. Returns annual means, percentiles, exceedance counts, data capture percentages, and compliance assessment against UK legal limits and WHO guidelines. Args: location: Postcode, place name, or "lat,lon". year: Calendar year to report on (default: most recent complete year). pollutants: Optional filter, e.g. ["NO2", "PM2.5"]. Default: all available.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | – |
| pollutants | – | – | – |
| year | – | – | – |
No output schema declared.
No examples provided.
time_patterns ~155
Analyse when pollution is highest — hour of day, day of week, and month. Returns temporal profiles showing typical patterns. Useful for advising on best times for outdoor exercise, school runs, or commuting. Args: location: Postcode, place name, or "lat,lon". pollutant: Pollutant to analyse — "NO2", "PM2.5", "PM10", "O3" (default "NO2"). period: Time window — "last_month", "last_3_months", "last_6_months", or "last_year" (default).
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | – |
| period | string | – | – |
| pollutant | string | – | – |
No output schema declared.
No examples provided.
trend_analysis ~205
Analyse the long-term trend in a pollutant near a location. Uses Theil-Sen slope estimation with Mann-Kendall significance testing to determine whether air quality is improving, worsening, or stable. Robust to outliers and missing data. Returns a 'summary' with plain-English trend description and statistical details. Present the summary to users first. Args: location: Postcode, place name, or "lat,lon". pollutant: Pollutant to analyse — "NO2", "PM2.5", "PM10", "O3" (default "NO2"). years: Number of years of data to analyse (default 5, range 2–5). Requests outside this range are clamped; the response includes ``metadata.years_clamped`` and a note in ``summary`` when so.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | – |
| pollutant | string | – | – |
| years | integer | – | – |
No output schema declared.
No examples provided.
What is the Hermes — Air Quality Intelligence MCP server?
Hermes — Air Quality Intelligence is an MCP server listed in the public MCP registry as com.southlondonscientific/hermes. UK air quality MCP: live readings, historical trends, LAQM stats, WHO checks, knowledge base. This page covers its hosted endpoint (https://hermes.southlondonscientific.com/mcp).
Is the Hermes — Air Quality Intelligence MCP server safe to use?
Hermes — Air Quality Intelligence scores 75 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 Hermes — Air Quality Intelligence MCP server expose?
Hermes — Air Quality Intelligence exposes 15 tools: assess_location_aq, get_current_aq, get_historical_aq, get_aqi_summary, list_monitors, and 10 more. Their descriptions and schemas cost roughly 2,217 tokens of context every time the server is loaded.
Does the Hermes — Air Quality Intelligence MCP server require authentication?
No. We connected to Hermes — Air Quality Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Hermes — Air Quality Intelligence MCP server still maintained?
Hermes — Air Quality Intelligence is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.