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.

io.github.j7an/nexus-mcp

PYPI · NEXUS-MCP

Delegate tasks to coding agents (Claude, Codex, Antigravity) from any MCP client

Available components

−15 this week 80 Trust /100

Last scanned (20 hours ago)

Scores higher than 80% of PyPI servers

Category Developer Tools

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 Security50
  • Malware scan not yet available for this package.Unverified
  • 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
  • 1 of 18 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 j7an/nexus-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 218 tokens (~109/item across 2 items; 1 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
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.

  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 +28
    • Malware scan: unverified → pass ▲ security
    • Stability: fail → 0.97 functional
  • 24 Oct 26 −15
    • GHSA-vqqp-x5qm-5qp4 affects this package: medium ▼ security
    • GHSA-7xgj-8392-5q4r affects this package: medium ▼ security
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → fail ▼ security
    • Package version: 2.1.2 → 2.1.3 functional
  • 20 Oct 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 3.

  • 17 Oct 26 +1
    • Package version: 2.1.1 → 2.1.2 functional
  • 15 Oct 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 0.

  • 14 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
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 4 Nov 2026 · Analysed pypi/nexus-mcp@2.1.3

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 j7an/nexus-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/j7an/nexus-mcp/.github/workflows/release.yml@refs/tags/v2.1.3
Rekor log index 3442663928
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:0fd7f8c3fe55c2de2990f4b94a0057b15e3df7a5196e479c50dd7fd48fe9516c

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 18 packages
Packages resolved 18
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~126 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
prompt ~126

Run one turn with a coding agent and return its final answer.

NameTypeReqDescription
backendstringyesAgent to run.
cwdstringyesAbsolute path of the project directory.
forkboolean–Branch session_id into a new conversation instead of continuing it.
model––Model id or alias; the provider default when omitted.
profilestring–Permission profile for the agent.
promptstringyesTask for the agent.
session_id––Continue this conversation (from a previous result).
timeoutinteger–Seconds before the turn is cancelled.
NameTypeReqDescription
backendstringyes–
outputstringyes–
session_idstringyes–
usage–––

No examples provided.

Install

How do I install the io.github.j7an/nexus-mcp server?

io.github.j7an/nexus-mcp runs locally as a PyPI package, launched with uvx nexus-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · nexus-mcp

# add to Claude Code
claude mcp add j7an-nexus-mcp -- uvx nexus-mcp
Common questions

What is the io.github.j7an/nexus-mcp server?

io.github.j7an/nexus-mcp is listed in the public MCP registry as io.github.j7an/nexus-mcp. Delegate tasks to coding agents (Claude, Codex, Antigravity) from any MCP client. This page covers its PyPI package (nexus-mcp).

Is the io.github.j7an/nexus-mcp server safe to use?

io.github.j7an/nexus-mcp scores 80 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 io.github.j7an/nexus-mcp server expose?

io.github.j7an/nexus-mcp exposes 1 tool: prompt. Their descriptions and schemas cost roughly 126 tokens of context every time the server is loaded.

Is the io.github.j7an/nexus-mcp server still maintained?

io.github.j7an/nexus-mcp 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 io.github.j7an/nexus-mcp server under?

io.github.j7an/nexus-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.