# Conning (oci · ghcr.io/eranyonai/conning)

Run commands on your remote test machines over SSH without the agent ever seeing a secret.

- Trust score: 42/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/eranyonai/conning`: 42/100 (this document), [markdown](https://verifymcp.io/servers/eranyonai-conning/ghcr-io-eranyonai-conning.md), [page](https://verifymcp.io/servers/eranyonai-conning/ghcr-io-eranyonai-conning)
- pypi · `conning`: 82/100, [markdown](https://verifymcp.io/servers/eranyonai-conning/conning.md), [page](https://verifymcp.io/servers/eranyonai-conning/conning)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/eranyonai/conning`
- Version: `0.6.5`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 451 tokens (~112/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "transfer" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Conning MCP server?

Conning runs locally as a container image, launched with docker run --rm -i ghcr.io/eranyonai/conning:0.6.5. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add eranyonai-conning -- docker run --rm -i ghcr.io/eranyonai/conning:0.6.5
```

### Cursor

```json
{
  "mcpServers": {
    "eranyonai-conning": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/eranyonai/conning:0.6.5"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "eranyonai-conning": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/eranyonai/conning:0.6.5"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add eranyonai-conning -- docker run --rm -i ghcr.io/eranyonai/conning:0.6.5
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eranyonai-conning": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/eranyonai/conning:0.6.5"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  eranyonai-conning:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/eranyonai/conning:0.6.5"]
```

### Netclaw

```json
{
  "McpServers": {
    "eranyonai-conning": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/eranyonai/conning:0.6.5"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "eranyonai-conning": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/eranyonai/conning:0.6.5"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 38, 0)

- [functional] Package version: 0.6.4 → 0.6.5

### 2026-10-26 (score 38, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 37, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 36, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `targets` (~48 tokens)

List targets (name, os, shell, tags, mode). filter: 'tag:<tag>' or names. check: probe reachability.

Input parameters:

- `check` (boolean)
- `filter`

### `run` (~110 tokens)

Run cmd (string) or argv on a target, a comma list, or tag:<tag>. Returns exit code first.
Still running after `wait` s (0 = return at once) -> a job id to `read`. Raise max_bytes only when needed.

Input parameters:

- `argv`
- `cmd`
- `cwd`
- `grep`
- `max_bytes` (integer)
- `target` (string, required)
- `timeout` (integer)
- `wait` (integer)

### `read` (~93 tokens)

Page j:<job> (only new lines; wait = long-poll seconds), o:<output> by range/grep, a:<approval>,
or <target>:<path>. signal: INT|TERM|KILL stops a job.

Input parameters:

- `grep`
- `id` (string, required)
- `max_bytes` (integer)
- `range`
- `signal`
- `wait` (integer)

### `transfer` (~45 tokens)

Copy a file or directory between local:<path> and <target>:<path>. Files are verified by sha256.

Input parameters:

- `dest` (string, required)
- `source` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/eranyonai-conning/ghcr-io-eranyonai-conning#diagnostics

## Score history

- 2026-11-05: 42
- 2026-11-04: 42
- 2026-11-03: 41
- 2026-11-02: 41
- 2026-11-01: 40
- 2026-10-31: 40
- 2026-10-30: 39
- 2026-10-29: 39
- 2026-10-28: 38
- 2026-10-27: 38
- 2026-10-26: 38
- 2026-10-25: 37
- 2026-10-24: 37
- 2026-10-23: 36
- 2026-10-22: 36
- 2026-10-21: 35
- 2026-10-20: 35
- 2026-10-19: 34
- 2026-10-18: 34
- 2026-10-17: 33

## Common questions

### What is the Conning MCP server?

Conning is an MCP server listed in the public MCP registry as io.github.EranYonai/conning. Run commands on your remote test machines over SSH without the agent ever seeing a secret. This page covers its container image (ghcr.io/eranyonai/conning).

### Is the Conning MCP server safe to use?

Conning scores 42 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 Conning MCP server expose?

Conning exposes 4 tools: targets, run, read, transfer. Their descriptions and schemas cost roughly 296 tokens of context every time the server is loaded.

### Is the Conning MCP server still maintained?

Conning 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 Conning MCP server under?

Conning 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.

## Links

- GitHub Container Registry: https://ghcr.io/eranyonai/conning
- Repository: https://github.com/EranYonai/Conning
- Changelog RSS feed: https://verifymcp.io/servers/eranyonai-conning/ghcr-io-eranyonai-conning.xml
- Changelog JSON feed: https://verifymcp.io/servers/eranyonai-conning/ghcr-io-eranyonai-conning.json
- HTML version of this page: https://verifymcp.io/servers/eranyonai-conning/ghcr-io-eranyonai-conning