South London Scientific MCP server

Which MCP servers are South London Scientific's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to South London Scientific

Whose server it is

Registry namecom.southlondonscientific/claraverified in the MCP registry

The registry name sits under southlondonscientific.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20

Stateanswerschecked 2026-10-20
Tools2
Server calls itselfclara
Server version1.27.0
Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 733 ms.

Should an agent connect itSkip it

Its tools do none of the product's use cases we checked: monitor borough-level air quality on live dashboards; evaluate whether an air quality intervention actually worked.

Once connected

Parameters are untyped or undescribed in 2 of 2 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 9, the first on 2026-10-20

INITE MCP score65 of 100answers 100 · does the job 0 · definitions 67 · context 100 · connects 100
What an agent can do with it0 of 2 use cases
Answered100% of days9 of 9 daily checks
Median first answer738 ms
Space in an agent's context≈ 1,064 tokensthe definitions of all its tools (2), which an agent carries on every turn
Tool definitionsC · 67 of 100
Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once

Parameters without a description: in 2 of 2
Not saying whether it only reads or can destroy: 2 of 2

What an agent can do with it

not sure · estimate personal pm2.5 and no2 exposure by location
cannot · monitor borough-level air quality on live dashboards
cannot · evaluate whether an air quality intervention actually worked

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-20

contextual_advice
Personalised air quality advice for a UK location and a specific user context. Use this tool whenever the user asks an air-quality question that depends on *who they are* or *what they're about to do*: e.g. asthma, pregnancy, school-age…
exposure_assessment
Estimate personal daily air pollution exposure across home, work, and commute. Uses time-weighted modelling across environments: home (with indoor source adjustments), work, and commute (with route-based pollution and transport mode…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

claude mcp add --transport http southlondonscientific https://clara-mcp.southlondonscientific.com/mcp

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://clara-mcp.southlondonscientific.com/mcp as a custom connector in the settings.

Other servers listed as South London Scientific's

com.southlondonscientific/hermesanswers, 15 toolsverified in the MCP registry

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.