Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Conning

OCI · GHCR.IO/ERANYONAI/CONNING · 2 COMPONENTS

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

+3 this week 42 Trust /100

Last scanned (1 hour ago)

Scores higher than 55% of OCI servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

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 Security0
  • 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.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability58
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 451 tokens (~112/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 5 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

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.

Changelog

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.

  • 4 Nov 26 +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.

  • 2 Nov 26 +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.

  • 31 Oct 26 +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.

  • 29 Oct 26 +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.

  • 27 Oct 26 0
    • Package version: 0.6.4 → 0.6.5 functional
  • 26 Oct 26 +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.

  • 24 Oct 26 +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.

  • 22 Oct 26 +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.

Diagnostics

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 oci/ghcr.io/eranyonai/conning@0.6.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 4 exposed · ~296 tokens

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 →

Tool Tokens
read ~93

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.

NameTypeReqDescription
grep–––
idstringyes–
max_bytesinteger––
range–––
signal–––
waitinteger––

No output schema declared.

No examples provided.

run ~110

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.

NameTypeReqDescription
argv–––
cmd–––
cwd–––
grep–––
max_bytesinteger––
targetstringyes–
timeoutinteger––
waitinteger––

No output schema declared.

No examples provided.

targets ~48

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

NameTypeReqDescription
checkboolean––
filter–––

No output schema declared.

No examples provided.

transfer ~45

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

NameTypeReqDescription
deststringyes–
sourcestringyes–

No output schema declared.

No examples provided.

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.

oci · ghcr.io/eranyonai/conning

# add to Claude Code
claude mcp add eranyonai-conning -- docker run --rm -i ghcr.io/eranyonai/conning:0.6.5
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.