eNSP Nexus
PYPI · ENSP-NEXUS · SCANNED SEP 20
MCP server and web terminal for Huawei eNSP network simulation.
Available components
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 Security88
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 0 of 34 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (BSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 23 days ago).Pass
- 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 run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox run of this package did not complete, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need 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 the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the eNSP Nexus MCP server?
eNSP Nexus runs locally as a PyPI package, launched with uvx ensp-nexus. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · ensp-nexus
claude mcp add quwentao2005-ensp-nexus -- uvx ensp-nexus
{
"mcpServers": {
"quwentao2005-ensp-nexus": {
"command": "uvx",
"args": [
"ensp-nexus"
]
}
}
} {
"servers": {
"quwentao2005-ensp-nexus": {
"command": "uvx",
"args": [
"ensp-nexus"
]
}
}
} codex mcp add quwentao2005-ensp-nexus -- uvx ensp-nexus
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"quwentao2005-ensp-nexus": {
"type": "local",
"command": [
"uvx",
"ensp-nexus"
],
"enabled": true
}
}
} openclaw mcp add quwentao2005-ensp-nexus --command uvx --arg ensp-nexus
mcp_servers:
quwentao2005-ensp-nexus:
command: "uvx"
args: ["ensp-nexus"] {
"McpServers": {
"quwentao2005-ensp-nexus": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"ensp-nexus"
]
}
}
} assistant mcp add quwentao2005-ensp-nexus -t stdio -c uvx -a ensp-nexus
{
"mcpServers": {
"quwentao2005-ensp-nexus": {
"command": "uvx",
"args": [
"ensp-nexus"
]
}
}
} 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.
- 28 Aug 26 0
- Source repository: Repository check failed: the declared repository URL returned HTTP 404. security
- Package version: 0.2.6 → 0.2.8 functional
- Package version: 0.2.6 → 0.2.7 functional
- 27 Aug 26 +1
No change was recorded against any check on this day. Supply Chain Security went from 87 to 88.
- 26 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
- 23 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 22 Aug 26 12
- Malware scan: pass → unverified ▼ security
- 21 Aug 26 0
- Malware scan: unverified → pass ▲ security
- 20 Aug 26 0
- Malware scan: pass → unverified ▼ security
- Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. 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
- 19 Aug 26 0
- Malware scan: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.2.4 → 0.2.6 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 20 Sept 2026 · Analysed pypi/ensp-nexus@0.2.8
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 34 packages
| Packages resolved | 34 |
|---|---|
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the eNSP Nexus MCP server?
eNSP Nexus is an MCP server listed in the public MCP registry as io.github.quwentao2005/ensp-nexus. MCP server and web terminal for Huawei eNSP network simulation. This page covers its PyPI package (ensp-nexus).
Is the eNSP Nexus MCP server safe to use?
eNSP Nexus scores 28 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.
Is the eNSP Nexus MCP server still maintained?
eNSP Nexus is still listed as active in the MCP registry. We last reached this channel on 20 September 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 eNSP Nexus MCP server under?
eNSP Nexus declares the BSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.