Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/june4432/thermo-control-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/june4432/thermo-control-mcp/thermo-control-mcp)<a href="https://agentmods.dev/mcp/june4432/thermo-control-mcp/thermo-control-mcp"><img src="https://agentmods.dev/badge/mcp/june4432/thermo-control-mcp/thermo-control-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/june4432/thermo-control-mcp/thermo-control-mcp"><img src="https://agentmods.dev/badge/mcp/june4432/thermo-control-mcp/thermo-control-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
thermo-control-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "thermo-control-mcp": { "command": "npx", "args": [ "-y", "thermo-control-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 9 lines scan A 4a738bbfe73e
thermo-control-mcp is an MCP server published in the GitHub repository june4432/thermo-control-mcp (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other mcp servers, from other repositories
fitllm
Will this LLM fit on your GPU, multi-GPU rig or Mac? Exact VRAM & KV-cache math. Read-only. Remote server at fitllm.run.
atomlane
MCP server "atomlane" as configured in cloudguo123/atomlane. Runs ./scripts/mcp_server.py with python3.
macos-mcp-server
Control macOS system settings, apps, windows, audio, displays, screenshots, and Focus mode via MCP. Runs locally from the @cyanheads/macos-mcp-server npm package. Needs 3 environment variables to run.
mcp-macos-toolkit
MCP server "mcp-macos-toolkit" as configured in ContractorKeith/mcp-macos-toolkit. Runs locally from the mcp-macos-toolkit npm package.
inferbench
Vendor-neutral local-LLM-inference benchmark and hardware-config advisor for omlx and llama.cpp -- measures real tokens/second on your own hardware, live. Runs locally from the inferbench-cli Python package.
msty-local-ops
MCP server "msty-local-ops" as configured in vega-llc/msty-local-ops. Runs locally from the msty-local-ops Python package.