Conning
PYPI · CONNING · 2 COMPONENTS
Run commands on your remote test machines over SSH without the agent ever seeing a secret.
Available components
Last scanned (22 hours ago)
Scores higher than 84% of PyPI servers
Category Cloud Infrastructure
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
- 4 of 42 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to EranYonai/Conning). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management60
- Stability observed for 18 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
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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 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.
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 4 Nov 2026 · Analysed pypi/conning@0.6.5
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | EranYonai/Conning |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/EranYonai/Conning/.github/workflows/release.yml@refs/tags/v0.6.5 |
| Rekor log index | 3522981194 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f80168b1ef105ef92ea35b0b524f3ab7a391a3b55137db866d61150defd42c79 |
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 42 packages
| Packages resolved | 42 |
|---|---|
| Stale | 3 |
| No linked repository | 1 |
| 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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| grep | – | – | – |
| id | string | yes | – |
| max_bytes | integer | – | – |
| range | – | – | – |
| signal | – | – | – |
| wait | integer | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| argv | – | – | – |
| cmd | – | – | – |
| cwd | – | – | – |
| grep | – | – | – |
| max_bytes | integer | – | – |
| target | string | yes | – |
| timeout | integer | – | – |
| wait | integer | – | – |
No output schema declared.
No examples provided.
targets ~48
List targets (name, os, shell, tags, mode). filter: 'tag:<tag>' or names. check: probe reachability.
| Name | Type | Req | Description |
|---|---|---|---|
| check | boolean | – | – |
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| dest | string | yes | – |
| source | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Conning MCP server?
Conning runs locally as a PyPI package, launched with uvx conning. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · conning
claude mcp add eranyonai-conning -- uvx conning
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 PyPI package (conning).
Is the Conning MCP server safe to use?
Conning scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 4 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.