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.

Nexus MCP

PYPI · NEXUS-MCP-NOTION-SUPABASE

Search Notion and Supabase through one safety-focused MCP server.

81 Trust /100

Last scanned (27 minutes ago)

Scores higher than 84% of PyPI servers

Category Search and Retrieval

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 Security100
  • 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
  • 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to madhvendrasinghsolanki/Nexus-MCP). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 127 tokens (~42/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

  • 14 Oct 26 +46
    • Injection markers: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
  • 12 Oct 26 35

    First indexed and scored.

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 17 Oct 2026 · Analysed pypi/nexus-mcp-notion-supabase@0.1.0

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 madhvendrasinghsolanki/Nexus-MCP
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/madhvendrasinghsolanki/Nexus-MCP/.github/workflows/release.yml@refs/tags/v0.1.0
Rekor log index 3229716449
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:3f51c9b334ba69bf8f4f74e8aa7be64ff2665c1973b02221a7e185095eeb05fa

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 34 packages
Packages resolved 34
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~74 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
health_check ~19

Probe every data source concurrently and report status and latency.

Input schema present but exposes no named parameters.

NameTypeReqDescription
okbooleanyesTrue only if every registered source is healthy
sourcesarrayyes–

No examples provided.

list_sources ~19

List the configured data sources and what each one supports.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

server_info ~36

Describe this server: version, non-secret configuration (including whether writes/deletes are enabled) and the connected data sources. Call this first.

Input schema present but exposes no named parameters.

NameTypeReqDescription
configobjectyesNon-secret runtime configuration
namestringyes–
sourcesarrayyes–
versionstringyes–

No examples provided.

Install

How do I install the Nexus MCP server?

Nexus MCP runs locally as a PyPI package, launched with uvx nexus-mcp-notion-supabase. 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-notion-supabase

# add to Claude Code
claude mcp add madhvendrasinghsolanki-nexus-mcp -- uvx nexus-mcp-notion-supabase
Common questions

What is the Nexus MCP server?

Nexus MCP is listed in the public MCP registry as io.github.madhvendrasinghsolanki/nexus-mcp. Search Notion and Supabase through one safety-focused MCP server. This page covers its PyPI package (nexus-mcp-notion-supabase).

Is the Nexus MCP server safe to use?

Nexus MCP scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 Nexus MCP server expose?

Nexus MCP exposes 3 tools: server_info, list_sources, health_check. Their descriptions and schemas cost roughly 74 tokens of context every time the server is loaded.

Is the Nexus MCP server still maintained?

Nexus MCP is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Nexus MCP server under?

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.