# Cooling Planner (remote · puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws)

MCP simulator for dairy barn cooling: evaluate equipment, roof and weather on heat, water and milk.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws`: 74/100 (this document), [markdown](https://verifymcp.io/servers/okajun35-cooling-planner/puzxplbkg2qglia72tkhs2z7km0jrusa.md), [page](https://verifymcp.io/servers/okajun35-cooling-planner/puzxplbkg2qglia72tkhs2z7km0jrusa)

## Channel facts

- Endpoint: `https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.10.0-preview.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1011 tokens (~202/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Cooling Planner MCP server?

Cooling Planner is a hosted endpoint at https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/, 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.

### Claude

```bash
claude mcp add --transport http okajun35-cooling-planner 'https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/'
```

### Cursor

```json
{
  "mcpServers": {
    "okajun35-cooling-planner": {
      "url": "https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "okajun35-cooling-planner": {
      "type": "http",
      "url": "https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.okajun35-cooling-planner]
url = "https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "okajun35-cooling-planner": {
      "type": "remote",
      "url": "https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add okajun35-cooling-planner --url 'https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  okajun35-cooling-planner:
    url: "https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/"
```

### Netclaw

```json
{
  "McpServers": {
    "okajun35-cooling-planner": {
      "Transport": "http",
      "Url": "https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add okajun35-cooling-planner -t streamable-http -u 'https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/'
```

### Other

```json
{
  "mcpServers": {
    "okajun35-cooling-planner": {
      "type": "http",
      "url": "https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-11 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `get_default_project` (~45 tokens)

Returns the default Project JSON and the scenario/device/point/area ID list used by operations. The starting point for building inputs. The returned project can be passed straight to evaluate.

### `evaluate` (~190 tokens)

Applies the operation list to a clone of project, computes it, and returns per-area aggregates, resources, roof, (with includeDaily) dailyMilk and dailyThermal (evaluation-day 24h per-point/area mean deficit) and the baseline. Without project, the default is used; without operations, it is computed as-is. Feeding the returned project back enables sequential editing.

Input parameters:

- `includeDaily` (boolean): true also computes the daily-milk hypothesis model (takes tens of seconds. Default: 60-min thermal only)
- `operations` (array): operation list applied in order to the clone. An empty array computes it as-is
- `project`: target Project JSON (the get_default_project return value or a previous evaluate result). Default: the default project
- `scenarioId` (string): scenario ID to apply operations to. Default: the project's current scenario. The baseline is read-only

### `compare_candidates` (~243 tokens)

Constrained candidate comparison. Applies 1-3 candidate operation lists separately to the same starting project and returns daily results (daily mean deficit, cooling water, power, worsened point count, milk), constraint verdicts and ranks. Candidate operations are only update_device (enabled/position/direction/daily schedule), update_system (onoff/daily schedule) and update_roof. Coefficients, weather, scenario switching and device add/remove are not allowed as candidates. Ranks hold only within the call. Takes tens of seconds to minutes as each candidate includes the daily computation.

Input parameters:

- `candidates` (array, required): candidates to compare. Each applies to a fresh clone of the start project (not cumulative)
- `constraints` (object)
- `project`: starting Project JSON. Default: the default project
- `ranking` (string): ranking rule: deficit = priority-area deficit, then max deficit, water, power / water = water-saving first (limited to candidates that improve the priority area) / worst = max-deficit first
- `scenarioId` (string): editable scenario ID to apply candidates to. Default: the project's current scenario. Baseline is not allowed

### `describe_model` (~87 tokens)

Returns what this model computes, what it assumes and what it ignores: the computation structure (roof/wind/spray/mist/cow balance/daily aggregate), input/output meanings, key assumed constants, limits and validation status. Call before interpreting results. get_doc fetches the documents in the docs list.

Input parameters:

- `project`: project to describe. Default: described with the default project's model settings

### `get_doc` (~97 tokens)

Returns the Markdown source of documents backing the model theory and coefficients. Corresponds to the docs list in describe_model: thermal_model = heat/spray model spec (MODEL.md), milk_model = daily-milk hypothesis model (MILK_HEAT_MODEL_V0_1.md), decisions_v08/decisions_v06 = design decision logs. Use to explain "why this formula or coefficient".

Input parameters:

- `name` (string, required): document name to fetch

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/okajun35-cooling-planner/puzxplbkg2qglia72tkhs2z7km0jrusa#diagnostics

## Score history

- 2026-10-24: 74
- 2026-10-23: 73
- 2026-10-22: 73
- 2026-10-21: 72
- 2026-10-20: 72
- 2026-10-19: 71
- 2026-10-18: 71
- 2026-10-17: 71
- 2026-10-16: 70
- 2026-10-15: 70
- 2026-10-14: 69
- 2026-10-13: 69
- 2026-10-12: 68
- 2026-10-11: 68
- 2026-10-10: 67
- 2026-10-08: 66
- 2026-10-05: 65
- 2026-10-04: 64
- 2026-10-03: 64
- 2026-10-02: 64
- 2026-10-01: 62
- 2026-09-30: 63

## Common questions

### What is the Cooling Planner MCP server?

Cooling Planner is an MCP server listed in the public MCP registry as io.github.okajun35/cooling-planner. MCP simulator for dairy barn cooling: evaluate equipment, roof and weather on heat, water and milk. This page covers its hosted endpoint (https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/).

### Is the Cooling Planner MCP server safe to use?

Cooling Planner scores 74 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 Cooling Planner MCP server expose?

Cooling Planner exposes 5 tools: get_default_project, evaluate, compare_candidates, describe_model, get_doc. Their descriptions and schemas cost roughly 662 tokens of context every time the server is loaded.

### Does the Cooling Planner MCP server require authentication?

Its publisher declares no required credentials for Cooling Planner. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Cooling Planner MCP server still maintained?

Cooling Planner is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/
- Repository: https://github.com/okajun35/cooling-planner
- Website: https://main.da05znjm47ziu.amplifyapp.com/
- Changelog RSS feed: https://verifymcp.io/servers/okajun35-cooling-planner/puzxplbkg2qglia72tkhs2z7km0jrusa.xml
- Changelog JSON feed: https://verifymcp.io/servers/okajun35-cooling-planner/puzxplbkg2qglia72tkhs2z7km0jrusa.json
- HTML version of this page: https://verifymcp.io/servers/okajun35-cooling-planner/puzxplbkg2qglia72tkhs2z7km0jrusa