mcp-registry/com.southlondonscientific/hermes · v1.30.0
As of 2026-10-22 12:34 UTC, the Southlondonscientific Hermes MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 6 minutes.
UK air quality MCP: live readings, historical trends, LAQM stats, WHO checks, knowledge base.
Claude Code
claude mcp add --transport http southlondonscientific-hermes-mcp-server https://hermes.southlondonscientific.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"southlondonscientific-hermes-mcp-server": {
"type": "http",
"url": "https://hermes.southlondonscientific.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
44 parameter(s) across 15 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
15 of 15 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~2,528 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 15 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.southlondonscientific%2Fhermes/fixes
{
"name": "compare_locations",
"description": "Compare current air quality across multiple locations side-by-side.\n\nReturns a ranked comparison by pollutant with DAQI bands and distance to\nnearest monitor. Useful for comparing development sites, school locations,\nor residential options.\n\nArgs:\n locations: List of 2–6 locations (postcodes, place names, or \"lat,lon\").\n pollutants: Optional filter, e.g. [\"NO2\", \"PM2.5\"]. Default: all available.\n",
"inputSchema": {
"type": "object",
"title": "compare_locationsArguments",
"required": [
"locations"
],
"properties": {
"locations": {
"type": "array",
"items": {
"type": "string"
},
"title": "Locations"
},
"pollutants": {
"anyOf": [
{
"type": "array",
"items": {
"type": "string"
}
},
{
"type": "null"
}
],
"title": "Pollutants",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_aqi_summary",
"description": "Get an AQI assessment with health advice and WHO compliance check.\n\nReturns a 'summary' with a plain-English health assessment, advice for\ngeneral and at-risk populations, and WHO guideline context. Present the\nsummary to users first. Also returns raw 'aqi' and 'who_compliance' data.\n\nArgs:\n location: Postcode, place name, or \"lat,lon\".\n index: AQI system — \"UK_DAQI\" (default), \"WHO\", or \"US_EPA\".\n period: \"current\", \"today\", \"this_week\", or \"this_month\".\n",
"inputSchema": {
"type": "object",
"title": "get_aqi_summaryArguments",
"required": [
"location"
],
"properties": {
"index": {
"type": "string",
"title": "Index",
"default": "UK_DAQI"
},
"period": {
"type": "string",
"title": "Period",
"default": "current"
},
"location": {
"type": "string",
"title": "Location"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_current_aq",
"description": "Get the most recent air quality readings near a location, with health context.\n\nReturns a 'summary' with a plain-English health assessment and advice\nfor general and at-risk populations. Present the summary to users first.\nAlso returns individual 'readings' from nearby monitors and 'metadata'\nabout data freshness and sources.\n\nArgs:\n location: Postcode, place name, or \"lat,lon\".\n radius_km: Search radius in kilometres (default 2.0).\n pollutants: Optional filter, e.g. [\"NO2\", \"PM2.5\"].\n ",
"inputSchema": {
"type": "object",
"title": "get_current_aqArguments",
"required": [
"location"
],
"properties": {
"sources": {
"anyOf": [
{
"type": "array",
"items": {
"type": "string"
}
},
{
"type": "null"
}
],
"title": "Sources",
"default": null
},
"location": {
"type": "string",
"title": "Location"
},
"radius_km": {
"type": "number",
"title": "Radius Km",
"default": 3.5
},
"pollutants": {
"anyOf": [
{
"type": "array",
"items": {
"type": "string"
}
},
{
"type": "null"
}
],
"title": "Pollutants",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.southlondonscientific/hermes"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.southlondonscientific/hermes"}) over MCP.
chart_aq_trend ~366 tokensget_historical_aq ~320 tokensget_current_aq ~281 tokensregulatory_stats ~235 tokenslist_monitors ~234 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.southlondonscientific%2Fhermes?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.southlondonscientific%2Fhermes?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.southlondonscientific%2Fhermes.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.southlondonscientific%2Fhermes.svg :target: https://glimind.com/server/mcp-registry%2Fcom.southlondonscientific%2Fhermes?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c835db94b89e37f9…, first seen 2026-10-17, included at leaf 661 of 45,935. Version history · verify what your client received.
Compare: most reliable data servers · most reliable media servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 12:34 UTC, the Southlondonscientific Hermes MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 6 minutes.
Southlondonscientific Hermes MCP server advertises 15 tools, including assess_location_aq, chart_aq_trend, compare_locations, get_aqi_summary, get_current_aq.
Point your MCP client at this streamable-http endpoint: https://hermes.southlondonscientific.com/mcp
Glimind scanned all 15 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.