Binky
PYPI · BINKY
Isolated dev environments, one per git worktree: ports, env, and DB slices as agent tools.
Available components
Last scanned (8 hours ago)
Scores higher than 82% of PyPI servers
Category CI/CD and DevOps
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 3 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 99 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 896 tokens (~179/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 5 Nov 2026 · Analysed pypi/binky@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 18 packages
| Packages resolved | 18 |
|---|---|
| Stale | 3 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
down ~110
Stop a worktree's processes while keeping its files, ports, and data. A paused worktree resumes instantly with up(). Idempotent: if no daemon is running there is nothing to stop, and this reports that instead of failing. Args: worktree: the worktree to stop. root: the project directory (defaults to the current working directory). Returns a dict with the number of processes ``stopped``.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | – | – |
| worktree | string | yes | – |
No output schema declared.
No examples provided.
env ~117
A worktree's live coordinates — service URLs and adapter addresses. These are what you hand to a process, a test run, or your own HTTP calls to reach the worktree's services. The worktree must be up first (call up()). Args: worktree: the worktree whose coordinates to read. root: the project directory (defaults to the current working directory). Returns a dict with an ``env`` map of name → URL/address.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | – | – |
| worktree | string | yes | – |
No output schema declared.
No examples provided.
status ~101
List every worktree on this machine with its state, health, and ports. A read-only snapshot — never starts the daemon. When no daemon is running nothing is up, so this returns an empty ``worktrees`` list rather than failing. Returns a dict with a ``worktrees`` list; each entry carries its ``project``, ``worktree``, ``status``, whether it's ``running``, its ``health``, and ``ports``.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
up ~183
Bring a worktree's isolated world online, starting the daemon if needed. Creates or reuses the git worktree, allocates a port for every service, provisions each adapter's private slice (e.g. a per-worktree database), starts the services in dependency order, and routes them through the proxy. Args: worktree: the branch/worktree name to bring up. root: the project directory (defaults to the current working directory). group: an optional service group to start on its own instead of all services. Returns a dict with the ``worktree`` and its started ``services`` (each with its name, ``pid``, and ``port``), plus any ``warnings``. Call env() for the URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | – |
| root | string | – | – |
| worktree | string | yes | – |
No output schema declared.
No examples provided.
verify ~135
Run the project's agents.verify checks against a worktree. The project defines these checks in its binky.toml; this runs them against the live worktree and reports the verdict — use it to gate work before handing off. The worktree must be up first (call up()). Args: worktree: the worktree to verify. root: the project directory (defaults to the current working directory). Returns a dict with an overall ``passed`` boolean and a ``checks`` list (each with its ``command`` and ``passed``).
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | – | – |
| worktree | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Binky MCP server?
Binky runs locally as a PyPI package, launched with uvx binky. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · binky
claude mcp add andreisilva1-binky -- uvx binky
What is the Binky MCP server?
Binky is an MCP server listed in the public MCP registry as io.github.andreisilva1/binky. Isolated dev environments, one per git worktree: ports, env, and DB slices as agent tools. This page covers its PyPI package (binky).
Is the Binky MCP server safe to use?
Binky scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Binky MCP server expose?
Binky exposes 5 tools: up, down, status, env, verify. Their descriptions and schemas cost roughly 646 tokens of context every time the server is loaded.
Is the Binky MCP server still maintained?
Binky is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Binky MCP server under?
Binky declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.