← Registry

Data Collection

southlondonscientific.com

Provides air quality data and personalized health advice for UK locations.

2 endpoints17 known toolsFirst detected July 25, 2026Last detected July 25, 2026

ENDPOINT 1

https://clara-mcp.southlondonscientific.com/mcp

No auth detected

MCP server metadata

Name
clara
Version
1.27.0
Capabilities
experimentalpromptsresourcestools
Server instructions

Clara — Personal Clean Air Planner. Built by South London Scientific. Provides personalised UK air quality advice and personal exposure assessment, drawing on the Hestia exposure library for evidence-based health context and intervention data. ## Tool catalogue - `contextual_advice` — personalised air quality advice for a location and personal context - `exposure_assessment` — personal daily exposure estimate across home, work, and commute ## Usage patterns ### contextual_advice **Standalone:** Provide a postcode or coordinates to get advice based on annual average pollution estimates: PM2.5 from the London Atmospheric Emissions Inventory (LAEI) and the UK Pollution Climate Mapping (PCM) model; NO2 from a custom land-use regression (LUR) model. **Composed with Hermes:** Pass live pm25/no2 values from Hermes `get_current_aq` to get advice based on current conditions rather than annual averages. Example flow: 1. Hermes `get_current_aq("SE17")` → get pm25, no2 values 2. Clara `contextual_advice(pm25=..., no2=..., postcode="SE17 1RL")` → contextualised advice ### exposure_assessment Estimates time-weighted personal exposure across home, work, and commute environments. Uses annual average pollution data with indoor source adjustments and transport mode factors. Example: `exposure_assessment(home_postcode="SE17 1RL", work_postcode="EC2R 8AH", transport_mode="tube", cooker_type="gas")` → daily PM2.5/NO2 exposure with breakdown by environment, commute details, and health context. **When to use which:** - `contextual_advice` — "what's the air quality HERE?" Single location, optionally live data. - `exposure_assessment` — "what's my ACTUAL daily exposure?" Multi-environment, time-weighted. ## Personal context ### contextual_advice parameters - `setting`: residential, school, workplace, outdoor_exercise, commute - `has_gas_cooker`: triggers specific indoor ventilation advice - `commute_mode`: walk, cycle, bus, car, train, tube (tube triggers underground-specific advice) - `has_indoor_sources`: smoking, woodstove, incense, candles - `audience`: general, children, elderly, respiratory, pregnant ### exposure_assessment parameters - `home_postcode`: required — home location - `work_postcode`: optional — work/school location (omit if not commuting) - `transport_mode`: walk, cycle, bus, car, train, tube - `work_frequency`: most_days, some_days, less_often, never - `commute_hour`: 0-23, enables time-of-day pollution adjustment - `cooker_type`: gas, electric, induction, unknown (gas adds ~60 µg/m³ NO2 indoors) - `smoking_at_home`: true/false (smoking adds ~35 µg/m³ PM2.5 indoors) - `tube_line`: specific Underground line (auto-inferred if omitted) ## Response structure and presentation Both tools return a `presentation` field containing pre-formatted markdown with exact values, gauge bars, tables, and advice. **Always present the `presentation` field to the user as-is.** Do not paraphrase, round, or restate the numbers — the presentation text is authoritative. You may add brief introductory or follow-up commentary around it, but the core content must come from `presentation`. The raw data fields (`exposure`, `breakdown`, `pollution`, `health_context`, etc.) are available for answering follow-up questions or making comparisons across calls. ## Scope - **Can do:** Personal exposure context, health advice, indoor source advice, commute exposure estimation, ULEZ/LTN intervention evidence for London. - **Cannot do:** Ambient monitoring data (use Hermes MCP server), forecasting, intervention evaluation. ## Attribution Built by South London Scientific (southlondonscientific.com). Health evidence from the Hestia exposure library. Pollution data: PM2.5 from LAEI and UK PCM; NO2 from a custom LUR model.

Known tools 2

contextual_advice

Personalised air quality advice for a UK location and a specific user context.

Inferred read-only
exposure_assessment

Estimate personal daily air pollution exposure across home, work, and commute.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.clara]
url = "https://clara-mcp.southlondonscientific.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "clara": {
      "type": "http",
      "url": "https://clara-mcp.southlondonscientific.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: clara
Remote MCP URL: https://clara-mcp.southlondonscientific.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "clara": {
      "url": "https://clara-mcp.southlondonscientific.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "clara": {
      "type": "http",
      "url": "https://clara-mcp.southlondonscientific.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "clara",
  "transport": "streamable-http",
  "url": "https://clara-mcp.southlondonscientific.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://hermes.southlondonscientific.com/mcp

No auth detected

MCP server metadata

Name
hermes
Version
1.27.1
Capabilities
experimentalpromptsresourcestools
Server instructions

Hermes is an air quality information server for London, built by South London Scientific. It provides ambient monitoring data with detailed coverage of Southwark and London-wide capability. ## Tool catalogue **Start here** — comprehensive single-call assessment: - `assess_location_aq` — one-call AQ assessment: current readings, trends, and monitor context **Live data tools** — use these for specific queries or follow-up: - `get_current_aq` — most recent readings near a location, with DAQI and health advice - `get_aqi_summary` — AQI assessment with WHO compliance check - `compare_locations` — side-by-side AQ comparison across multiple locations **Historical & trend tools** — use these for analysis over time: - `get_historical_aq` — historical data for a date range, with summary statistics - `trend_analysis` — long-term trend with statistical significance (Theil-Sen + Mann-Kendall) - `regulatory_stats` — LAQM-style annual statistics (means, percentiles, exceedances) - `time_patterns` — diurnal, day-of-week, and monthly pollution profiles **Visualisation:** - `chart_aq_trend` — time series chart as inline PNG image **Monitor discovery:** - `list_monitors` — find monitoring sites near a location with operational status **Knowledge base** — curated, evidence-based reference documents: - `kb_get_guidelines` — DAQI bands, WHO guidelines, UK legal limits - `kb_get_health_effects` — pollutant-specific health evidence by population group - `kb_get_local_context` — area-specific AQ context (Southwark, London boroughs) - `kb_get_practical_advice` — generic protective actions (e.g. "should anyone exercise on a high-pollution day?"). For *personalised* advice keyed to the user's own context (asthma, pregnancy, gas cooker, tube commute), call Clara's `contextual_advice` instead. - `kb_get_monitoring_explainer` — how monitors work, data interpretation ## Scope - **Can do:** Ambient air quality data for London and UK regulatory monitoring networks. Historical trends, regulatory compliance, temporal patterns, health context. - **Cannot do:** Personalised health advice and personal exposure assessment (use the Clara MCP server), forecasting, indoor air quality. ## Composition with Clara (personal-health questions) When the user asks a question that ties air quality to their own situation — e.g. "I have asthma, is it safe to run outside?", "should I cycle today with my kid?", "my child has a cough, is the air bad?" — Hermes alone is the wrong shape. The right pattern is: 1. Call Hermes `get_current_aq` (or `assess_location_aq`) for the user's location to get live pm25 and no2 numbers. 2. Pass those numbers + the user's context (audience, setting, indoor sources) to Clara's `contextual_advice` tool. 3. Present Clara's advice, attributing the live data to Hermes and the personalised context to Clara. Hermes' own `kb_get_practical_advice` is a **fallback** for when Clara is unavailable or the user wants only generic guidance, not a substitute for the composition above. ## Key principle A monitor reading is NOT personal exposure. Always contextualise with distance, monitor type, and the difference between ambient monitoring and what people actually breathe. ## Response structure All tools return structured JSON with a `summary` or `narrative` field containing plain-English interpretation. Present this to users first, then use the raw data fields for detail. Error responses use `{"error": {"type": "...", "message": "..."}}`. ## Attribution Built by South London Scientific (southlondonscientific.com). Data from UK regulatory networks (AURN, AQE, LMAM, SAQN) and Breathe London via Aeolus.

Known tools 15

assess_location_aq

Comprehensive air quality assessment for a location in one call.

Inferred read-only
get_current_aq

Get the most recent air quality readings near a location, with health context.

Inferred read-only
get_historical_aq

Get historical air quality data for a site or location, with health context.

Inferred read-only
get_aqi_summary

Get an AQI assessment with health advice and WHO compliance check.

Inferred read-only
list_monitors

List air quality monitoring sites near a location, with context.

Inferred read-only
chart_aq_trend

Generate a time series chart of air quality data.

Inferred read-only
trend_analysis

Analyse the long-term trend in a pollutant near a location.

Inferred read-only
compare_locations

Compare current air quality across multiple locations side-by-side.

Inferred read-only
regulatory_stats

Get LAQM Annual Status Report-style statistics for a location.

Inferred read-only
time_patterns

Analyse when pollution is highest — hour of day, day of week, and month.

Inferred read-only
kb_get_guidelines

Get current air quality guideline and target values.

Inferred read-only
kb_get_health_effects

Get health evidence summaries for a pollutant and population group.

Inferred read-only
kb_get_local_context

Get area-specific contextual information.

Inferred read-only
kb_get_practical_advice

Generic protective-action guidance for a category of situation (NOT keyed to an individual user's context).

Inferred read-only
kb_get_monitoring_explainer

Get plain-language explanations of monitoring methods and limitations.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.hermes]
url = "https://hermes.southlondonscientific.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "hermes": {
      "type": "http",
      "url": "https://hermes.southlondonscientific.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: hermes
Remote MCP URL: https://hermes.southlondonscientific.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "hermes": {
      "url": "https://hermes.southlondonscientific.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "hermes": {
      "type": "http",
      "url": "https://hermes.southlondonscientific.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "hermes",
  "transport": "streamable-http",
  "url": "https://hermes.southlondonscientific.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.