No user-submitted related servers found.
Scored across 2 tools
cloudpin_status reports current cloud account/environment/hook context, while cloudpin_check evaluates a proposed shell command. They are mostly distinct, though both discuss per-CLI account usage and could be momentarily confused as a preflight vs. status check.
Both tools consistently use the cloudpin_ prefix followed by a short lowercase identifier. The pattern is predictable and readable despite status being a noun and check being noun/verb-like.
The server has only two tools, which feels thin even for a narrow guardrail/inspection purpose. Each earns its place, but the surface could reasonably support more operations such as managing pins or hooks.
The pair covers inspecting context and checking commands, but there are notable gaps: no tool to modify .cloudpin.yml pins, manage environment selection, or install/configure the agent hooks mentioned in cloudpin_status. The core read/check workflow exists but lifecycle operations are missing.
