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.

Vectr

PYPI · VECTR · SCANNED SEP 24

Semantic codebase search + persistent working memory for AI code editors. Local, no API key.

Available components

pypi · vectr 30
+15 this week 30 Trust /100
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 Security71
  • No malware found by supply-chain analysis.Pass
  • A critical CVE affects chromadb, and no fixed version has been published yet. View diagnostics → Fail
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • Dependency health was assessed across the 129 of 188 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
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 →

Install

How do I install the Vectr MCP server?

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

pypi · vectr

# add to Claude Code
claude mcp add swapnanil-vectr -- uvx vectr
// .cursor/mcp.json
{
  "mcpServers": {
    "swapnanil-vectr": {
      "command": "uvx",
      "args": [
        "vectr"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "swapnanil-vectr": {
      "command": "uvx",
      "args": [
        "vectr"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add swapnanil-vectr -- uvx vectr
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "swapnanil-vectr": {
      "type": "local",
      "command": [
        "uvx",
        "vectr"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add swapnanil-vectr --command uvx --arg vectr
# ~/.hermes/config.yaml
mcp_servers:
  swapnanil-vectr:
    command: "uvx"
    args: ["vectr"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "swapnanil-vectr": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "vectr"
      ]
    }
  }
}
# add to Vellum
assistant mcp add swapnanil-vectr -t stdio -c uvx -a vectr
// mcp.json
{
  "mcpServers": {
    "swapnanil-vectr": {
      "command": "uvx",
      "args": [
        "vectr"
      ]
    }
  }
}
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.

  • 18 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Sept 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Sept 26 −15
    • 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
    • Tool safety: Tool safety not yet verified: our sandbox run of this package did not complete, so we have no tool text to scan. 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
  • 2 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. 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: 1.11.0 → 1.12.0 functional
  • 1 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 31 Aug 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: fail → unverified ▼ functional
  • 30 Aug 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 24 Sept 2026 · Analysed pypi/vectr@1.12.0

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 →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 8 findings
ID CVE Severity Vector Fix available
GHSA-2wm9-hf6c-p5cr CVE-2026-45830 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no
GHSA-36p7-vc44-83pf CVE-2026-45833 critical no
GHSA-f4j7-r4q5-qw2c CVE-2026-45829 critical no
GHSA-xph7-9rjv-w5fr CVE-2026-45831 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no
PYSEC-2026-311 CVE-2026-45829 none no
PYSEC-2026-3813 CVE-2026-45830 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no
PYSEC-2026-3814 CVE-2026-45833 none no
PYSEC-2026-3815 CVE-2026-45831 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no

Background: What a vulnerability scan can and cannot prove →

Dependencies 129 packages
Packages resolved 129
Stale 9
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

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.

Common questions

What is the Vectr MCP server?

Vectr is an MCP server listed in the public MCP registry as io.github.swapnanil/vectr. Semantic codebase search + persistent working memory for AI code editors. Local, no API key. This page covers its PyPI package (vectr).

Is the Vectr MCP server safe to use?

Vectr scores 30 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 24 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 Vectr MCP server still maintained?

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

Vectr declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.