selvo
PYPI · SELVO
Linux CVE prioritisation: 16 MCP tools for scan, fleet, runtime, and PR-able fix discovery.
Available components
Last scanned (3 months ago)
Scores higher than 0% of PyPI servers
Category Security
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security50
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: we could not find this package in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency0
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: the registry has no such package, so there's no artefact to verify. See how to fix → View diagnostics → Fail
- License check failed: the registry has no such package, so no license can be read. See how to fix → Fail
- Maintenance check failed: the registry has no such package, so there's no release history to read. See how to fix → Fail
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety–
Not scored yet: our latest scan of this package recorded no findings here. That is usually because the category is newer than the scan, or because we have not captured the MCP schema this package serves yet. It fills in the next time we score it.
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
Checks we ran (5)
- Malware scan
- Source repository
- Provenance
- License
- Maintenance
Checks we could not complete (9)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Known CVEs in Supply Chain SecurityKnown CVEs could not be checked: we could not find this package in its registry.
- Install scripts in Supply Chain SecurityInstall-script risk not yet assessed.
- Dependency health in Supply Chain SecurityDependency health could not be checked: we could not find this package in its registry.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- Tool Safety in Tool SafetyNot scored yet: our latest scan of this package recorded no findings here. That is usually because the category is newer than the scan, or because we have not captured the MCP schema this package serves yet. It fills in the next time we score it.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 7 Aug 26 0
- Malware scan: unverified → pass ▲ security
- 5 Aug 26 −15
- Malware scan: pass → unverified ▼ security
- 4 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Aug 26 0
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 0
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
- Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
- 26 Jul 26 18
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 7 Aug 2026 · Analysed pypi/selvo@2.1.1
Provenance Package not found
The registry answered that no such package exists, so no provenance could be looked up.
| Result | Package not found |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
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 →
Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
How do I install the selvo MCP server?
selvo runs locally as a PyPI package, launched with uvx selvo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · selvo
claude mcp add cope-labs-selvo -- uvx selvo
What is the selvo MCP server?
selvo is an MCP server listed in the public MCP registry as io.github.Cope-Labs/selvo. Linux CVE prioritisation: 16 MCP tools for scan, fleet, runtime, and PR-able fix discovery. This page covers its PyPI package (selvo).
Is the selvo MCP server safe to use?
selvo scores 0 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.
Is the selvo MCP server still maintained?
selvo has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the selvo MCP server?
VerifyMCP ran 5 checks on selvo, covering Malware scan, Source repository, Provenance, License and 1 more. 9 items could not be completed, a gap on our side rather than a finding about selvo: Known CVEs, Install scripts, Dependency health, Security disclosure and 5 more. 4 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.