Vexor
PYPI · VEXOR · SCANNED SEP 21
A semantic search engine for files and code.
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 Security49
- 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 native-build step with no shell scripting around it. View diagnostics → Pass
- 8 of 66 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 733 tokens (~366/item across 2 items; 2 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 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 2 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Vexor MCP server?
Vexor runs locally as a PyPI package, launched with uvx vexor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · vexor
claude mcp add scarletkc-vexor -- uvx vexor
{
"mcpServers": {
"scarletkc-vexor": {
"command": "uvx",
"args": [
"vexor"
]
}
}
} {
"servers": {
"scarletkc-vexor": {
"command": "uvx",
"args": [
"vexor"
]
}
}
} codex mcp add scarletkc-vexor -- uvx vexor
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"scarletkc-vexor": {
"type": "local",
"command": [
"uvx",
"vexor"
],
"enabled": true
}
}
} openclaw mcp add scarletkc-vexor --command uvx --arg vexor
mcp_servers:
scarletkc-vexor:
command: "uvx"
args: ["vexor"] {
"McpServers": {
"scarletkc-vexor": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"vexor"
]
}
}
} assistant mcp add scarletkc-vexor -t stdio -c uvx -a vexor
{
"mcpServers": {
"scarletkc-vexor": {
"command": "uvx",
"args": [
"vexor"
]
}
}
} 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.
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 0
- Stability: pass → 0.97 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −2
- Stability: pass → 0.87 functional
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 13 Sept 26 +16
- Malware scan: unverified → pass ▲ security
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 21 Sept 2026 · Analysed pypi/vexor@0.29.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 | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 66 packages
| Packages resolved | 66 |
|---|---|
| Stale | 7 |
| No linked repository | 1 |
| 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 →
vexor_index ~235
Build or refresh the semantic index for a directory. Use it to warm the cache or when auto_index is disabled.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_patterns | array | – | Gitignore-style patterns to exclude. |
| extensions | array | – | Only include these file extensions, e.g. ['.py', '.md']. |
| include_hidden | boolean | – | Include dot-prefixed files and directories such as .github or .env (excluded by default). |
| local | boolean | – | Create <path>/.vexor and store this project's index there |
| mode | string | – | Index granularity: auto routes per file type; name embeds filenames only; head/full/brief cover content depth; code chunks by AST; outline chunks Markdown by headings. |
| path | string | – | Directory to operate on. Absolute, or relative to the server's default path (/workdir). |
| recursive | boolean | – | Recurse into subdirectories (default). Set false to scan only the top level of the directory. |
| respect_gitignore | boolean | – | Honor .gitignore rules (default). Set false to also scan ignored files such as build output. |
| Name | Type | Req | Description |
|---|---|---|---|
| files_indexed | integer | yes | – |
| mode | string | yes | – |
| path | string | yes | – |
| status | string | yes | – |
No examples provided.
vexor_search ~378
Find files or code from a natural-language description. Returns ranked matches with paths, relevance scores, line ranges, and the matching source text, so most results need no follow-up file read.
| Name | Type | Req | Description |
|---|---|---|---|
| content_budget | integer | – | Total characters of source text one response may return, spent on the highest-ranked matches first. |
| exclude_patterns | array | – | Gitignore-style patterns to exclude. |
| extensions | array | – | Only include these file extensions, e.g. ['.py', '.md']. |
| include_content | boolean | – | Return each match's source text alongside its path. Text is read from the file at search time. A result carries content_unavailable instead when the mode records no line range, the file changed since… |
| include_hidden | boolean | – | Include dot-prefixed files and directories such as .github or .env (excluded by default). |
| mode | string | – | Index granularity: auto routes per file type; name embeds filenames only; head/full/brief cover content depth; code chunks by AST; outline chunks Markdown by headings. |
| no_cache | boolean | – | Build a temporary in-memory index and disable all disk caches for this search. Slower and may regenerate embeddings. |
| path | string | – | Directory to operate on. Absolute, or relative to the server's default path (/workdir). |
| query | string | yes | Natural-language description of the file or code you are looking for, e.g. 'where API retries are configured'. |
| recursive | boolean | – | Recurse into subdirectories (default). Set false to scan only the top level of the directory. |
| respect_gitignore | boolean | – | Honor .gitignore rules (default). Set false to also scan ignored files such as build output. |
| top | integer | – | Number of results to return. |
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string|null | yes | – |
| content_budget | object|null | – | – |
| index_empty | boolean | yes | – |
| path | string | yes | – |
| query | string | yes | – |
| reranker | string|null | yes | – |
| results | array | yes | – |
| stale | boolean | yes | – |
No examples provided.
What is the Vexor MCP server?
Vexor is an MCP server listed in the public MCP registry as io.github.scarletkc/vexor. A semantic search engine for files and code. This page covers its PyPI package (vexor).
Is the Vexor MCP server safe to use?
Vexor scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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.
What tools does the Vexor MCP server expose?
Vexor exposes 2 tools: vexor_search, vexor_index. Their descriptions and schemas cost roughly 613 tokens of context every time the server is loaded.
Is the Vexor MCP server still maintained?
Vexor is still listed as active in the MCP registry. We last reached this channel on 21 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 Vexor MCP server under?
Vexor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.