Atlas Scientific EZO Sensors MCP Server

What the code does

We read the source, 6 d ago · rules ccca72095570

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

            subprocess.run(  # noqa: S603, S607

            data = yaml.load(text, Loader=_strict_yaml_loader())  # noqa: S506 - a SafeLoader subclass

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add labmcp-atlas-ezo -- uvx labmcp-atlas-ezo

{
  "mcpServers": {
    "labmcp-atlas-ezo": {
      "args": [
        "labmcp-atlas-ezo"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.labmcp-atlas-ezo]
command = "uvx"
args = ["labmcp-atlas-ezo"]

{
  "mcpServers": {
    "labmcp-atlas-ezo": {
      "args": [
        "labmcp-atlas-ezo"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "labmcp-atlas-ezo": {
      "args": [
        "labmcp-atlas-ezo"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: LABMCP_ADDRESS (Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025), LABMCP_SIMULATE (Set to 1 to use the built-in simulator (no hardware)), LABMCP_READ_ONLY (Set to 1 to disable all state-changing tools), LABMCP_LIMITS (Safety limit overrides, e.g. max_temperature_c=80). The author declared them in the registry entry; get the values from the project itself.