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.

vecscope

PYPI · VECSCOPE

Deterministic evidence about embedding spaces and vector indexes: hubness, collapse, ANN recall

Available components

76 Trust /100

Last scanned (23 hours ago)

Scores higher than 73% of PyPI servers

Category Testing and QA

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 29 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 076923/vecscope). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability50
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2146 tokens (~536/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 2 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 1 Nov 26 59

    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 4 Nov 2026 · Analysed pypi/vecscope@0.11.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 076923/vecscope
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/076923/vecscope/.github/workflows/release.yml@refs/tags/v0.11.0
Rekor log index 3629221367
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:7d4af08f1edbb929e6890895b22934d59317a474be00222ec30d0e84e24355ca

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

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~1,844 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
audit_embeddings ~1,074

Audit an embedding file: hubness, anisotropy, collapse, rogue dimensions, norms, metric mismatch, distance concentration, outliers, k-NN graph islands, and optionally ANN recall and query-side findings. Read-only; the file never leaves the machine. `path`: local .npy/.npz/.parquet/.jsonl/.json/.csv with one vector per row, a faiss index file, or a vector store URI (qdrant://, chroma://, milvus://, weaviate://, or their +local forms with a directory). When the server was started with --allow-dir or VECSCOPE_ALLOWED_DIRS, paths outside those directories are refused; network stores need the server started with --allow-network. Store rows are in ascending id order and findings carry `sample_source_ids` next to `sample_ids`. `ann_from_source`: query the store's own index for every stored vector and score it as `ann_path` (needs `sample=0` above the sample size). `qrels_path`: relevance judgments for the queries (.json/.jsonl/.tsv of query row, corpus row, grade); adds `retrieval` with nDCG, recall, MRR and duplicate share of exact search. `ranked_path`: (m x k) corpus row ids per query from the production index, scored with `qrels_path` next to exact search. `ann_path`: optional (n x k) integer array of neighbor ids from an ANN index (requires `sample=0` so row ids line up). `queries_path`: optional (m x dim) file of query embeddings; adds query_gap, query_hubness and the deprecated ood_queries. `query_baseline_path`: optional JSON evidence (this tool's response or `vecscope audit --json`) from an earlier audit of the same corpus with healthy queries; with `queries_path` it adds query_shift, the share of queries farther from the corpus than that reference's median + 3 MAD. `clusters` > 0 attaches a per-cluster map with sample ids (no verdicts); capped at one cluster per 10 rows. `sample`: rows above this are audited on a seeded random subset (0 = audit every row; exact k-NN is quadratic, minutes for 100k rows on a laptop; peak memory about 2 GiB). `sample_repeats`: whe…

NameTypeReqDescription
ann_from_sourceboolean––
ann_path–––
baseline–––
clustersinteger––
kinteger––
near_dup_cosnumber––
pathstringyes–
qrels_path–––
queries_path–––
query_baseline_path–––
ranked_path–––
sampleinteger––
sample_repeatsinteger––
thresholds–––
tolerances–––
verboseboolean––

No output schema declared.

No examples provided.

compare_embeddings ~301

Compare two embedding files whose rows are the same items in the same order (two models, or one model before and after a transform). Reports how often the nearest neighbor and the top-k lists agree, the near-duplicate share in each space and in both, whether both spaces pick the same duplicate partner, and the rows that disagree most. No verdicts: duplicates flagged by both spaces with the same partner belong to the items; duplicates flagged by one space only point at that model. Above `sample` rows a seeded subset is compared (0 = all rows). Read `neighbor_scope` before quoting the agreement: "sample" means the neighbors were recomputed inside the sampled rows, so the numbers describe the sample's own neighbor graph and are usually higher than the full corpus's. To compare full-corpus rankings, pass `neighbors_a_path` and `neighbors_b_path` (both): (n x >= k) neighbor ids per row computed on the full corpus in each space, exact or from the production index; the rows may still be sampled but their neighbors are not (`neighbor_scope` = "full", `neighbor_source` = "supplied").

NameTypeReqDescription
kinteger––
near_dup_cosnumber––
neighbors_a_path–––
neighbors_b_path–––
path_astringyes–
path_bstringyes–
sampleinteger––

No output schema declared.

No examples provided.

describe_findings ~59

List every finding vecscope can report with its metric key, default (warn, fail) thresholds and direction, likely causes, suggested first action and verification step. Use it to explain a verdict to the user or to decide which thresholds to override.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sweep_index ~410

Sweep HNSW (M, ef_search) and IVF (nprobe) parameters on an embedding file and report recall@k against exact k-NN, build time, queries per second, single-query latency percentiles (p50/p95/p99 ms) and the serialized index size for each setting, plus the fastest configuration that reaches `target_recall`. The recommendation carries `margin` (recall minus target) and is marked `tight` with a `safer_alternative` when the margin is under `margin`, because recall at fixed parameters falls as the corpus grows; relay `caveats` to the user. qps is the median of `timing_repeats` runs. Needs the faiss extra (`pip install "vecscope[index]"`). Read-only; timings are relative to this machine and process, not a serving latency. `device` is "auto" (GPU when the faiss build has one), "cpu" or "gpu"; HNSW is CPU-only. `n_queries` caps the queries timed (sampled from the corpus, or from `queries_path`); pass real query traffic as `queries_path` whenever it exists, because the best setting on corpus-drawn queries can differ. `latency_queries` are searched one at a time per setting for the percentiles (0 = skip). `nlist` fixes the IVF list count; pass the production index's nlist when tuning its nprobe, since the default follows the row count (4*sqrt(n)) and gives other lists.

NameTypeReqDescription
devicestring––
kinteger––
latency_queriesinteger––
marginnumber––
n_queriesinteger––
nlist–––
pathstringyes–
queries_path–––
target_recallnumber––
timing_repeatsinteger––

No output schema declared.

No examples provided.

Install

How do I install the vecscope MCP server?

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

pypi · vecscope

# add to Claude Code
claude mcp add 076923-vecscope -- uvx vecscope
Common questions

What is the vecscope MCP server?

vecscope is an MCP server listed in the public MCP registry as io.github.076923/vecscope. Deterministic evidence about embedding spaces and vector indexes: hubness, collapse, ANN recall. This page covers its PyPI package (vecscope).

Is the vecscope MCP server safe to use?

vecscope scores 76 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 vecscope MCP server expose?

vecscope exposes 4 tools: audit_embeddings, sweep_index, compare_embeddings, describe_findings. Their descriptions and schemas cost roughly 1,844 tokens of context every time the server is loaded.

Is the vecscope MCP server still maintained?

vecscope 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 vecscope MCP server under?

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