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.
Available components
Last scanned (19 minutes ago)
Scores higher than 66% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Health and Science
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 13 Oct 26 +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.
- 11 Oct 26 +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.
- 10 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.lambda-url.us-east-1.on.aws | CN=Amazon RSA 2048 S19,O=Amazon,C=US | 29 Sept 2026 | 15 Apr 2027 | RSA 2048 | SHA256-RSA | 40a712e3d40ea0ec186cb07d6b8eadd5 |
| SANs: *.lambda-url.us-east-1.on.aws | ||||||
| CN=Amazon RSA 2048 S19,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 8 Jul 2026 | 7 Jul 2029 | RSA 2048 | SHA256-RSA | 3e66530c008bab6b9a6d90c1f0d323dac30eeeca |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| aws. | present | 54182 | 8 | Verified |
| on.aws. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/ | Verified | 200 | |
| http (plaintext) | http://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/ | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_candidates ~243
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.
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | 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 |
No output schema declared.
No examples provided.
describe_model ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | – | – | project to describe. Default: described with the default project's model settings |
No output schema declared.
No examples provided.
evaluate ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_default_project ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_doc ~97
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".
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | document name to fetch |
No output schema declared.
No examples provided.
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.
remote · puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws
claude mcp add --transport http okajun35-cooling-planner 'https://puzxplbkg2qglia72tkhs2z7km0jrusa.lambda-url.us-east-1.on.aws/'
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.