# plonk-mcp

MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.4.0
- **Author:** io.github.ostapondo
- **License:** MIT
- **npm:** plonk-mcp
- **Source:** https://github.com/ostapondo/plonk
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 10 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-18T14:49:54.665Z
- **Version scanned:** 0.3.0
- **CVEs:** none found by OSV at scan time

## Tools

21 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `set_active`
- `select_agent`
- `annotate_screenshot`
- `set_awake`
- `apply_layout`
- `save_layout`
- `apply_saved_layout`
- `snap_window`
- `delete_layout`
- `measure_screen`
- `take_screenshot`
- `get_state`
- `extract_text`
- `check_for_update`
- `install_update`
- `save_workspace`
- `launch_workspace`
- `delete_workspace`
- `save_zone_set`
- `assign_zone_set`
- `delete_zone_set`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"plonk\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"plonk-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on your machine.
- Floor 39, ceiling 63 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/plonk-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/plonk-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/plonk-mcp
- HTML page: https://forgeregistry.com/registry/plonk-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.