Ruvector — Watchlist | MCP100 Index

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to RuVector memory, routing and code-analysis MCP tools: Do memory hooks and the documented MCP tools remain aligned with the vector-engine release and configuration?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Local vector storage, semantic/hybrid retrieval and optional MCP code intelligence.

What we know

Local vector-database SDK with persistence, embeddings, Graph RAG, hooks and a bundled MCP server with configurable tool profiles.

Maintenance / activity evidence

ruvector 0.3.3 published 2026-09-23T16:10:20.901Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Local DB plus configured MCP profile. Writes: Vector insert/delete; Persistent memory updates; Optional local config/file outputs.
Authentication not yet verified.
Sensitive access: Embeddings, Local code/data

Local-first but broad tool profiles can expose more than simple vector CRUD; readonly profile is safer.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 290.5k package downloads / 30 days

Downloads observed Sep 25, 2026.

Do not overwrite existing reviewed stars/download metrics with nulls from this enrichment batch.

All limitations / Review context

Do memory hooks and the documented MCP tools remain aligned with the vector-engine release and configuration?

The bounded review of the publisher's documented RuVector memory, routing and code-analysis MCP tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Local-first but broad tool profiles can expose more than simple vector CRUD; readonly profile is safer.
Local DB plus configured MCP profile.
Designed for local storage; hooks can inspect code/files.
Reviewed write actions: Vector insert/delete; Persistent memory updates; Optional local config/file outputs
Sensitive access: Embeddings, Local code/data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Native/WASM performance differs by platform.
MCP surface can be broad outside readonly profile.
Docs span multiple feature/version generations.

Original activity observations

ruvector 0.3.3 published 2026-09-23T16:10:20.901Z

Technical identity

npm/ruvector

Exact implementation source: https://www.npmjs.com/package/ruvector ↗
Reviewed resource type: SDK
Repository identity: ruvnet/ruvector
Package identity: ruvector

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 7, 2026

Package registry ↗
ruvector
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
ruvnet/ruvector
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

SDK setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

No runtime server process, Docker setup, OAuth or credentials were executed during this research.
Conditional grade denotes multi-surface SDK and access controls, NOT absence of an MCP start command.
Install documentation is not a guarantee of current package/runtime compatibility.
RuVector is SDK/CLI with an explicitly documented MCP subcommand; not a pure standalone MCP product.
2026-10-13 targeted publisher npm README plus official repository/docs where specified; static research, not runtime test.
Inspect the permitted MCP tool catalog and ruvector mcp tools after registration; do not exercise write tools. (Documentation review only, not runtime verified.)
Never paste real credentials into a documentation example.
No live install, OAuth, paid calls, third-party mutation or credential revocation executed.
Some host removal commands are MCP100-composed based on chosen registration name, not publisher-authored.

Install SDK / CLI integration
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Claude Code only · Publisher instructions
claude mcp add ruvector -- npx ruvector mcp start
Configure / authenticate
MCP100 setup guide
Run Ruvector server in repository and restrict tool profile for safe operation: RUVECTOR_MCP_PROFILE=readonly when appropriate.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Previously reviewed configuration / prerequisites: For reduced privileges set RUVECTOR_MCP_PROFILE=readonly in client environment and review tool allow/deny policy. The SDK/CLI has broader capabilities beyond the MCP subset.
Check connection
Suggested check
npx ruvector mcp tools; npx ruvector harness doctor --json.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `ruvector` in Claude Code, remove its exact client entry with `claude mcp remove ruvector`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove ruvector

Official Documentation & Sources

What it does

Local vector-database SDK with persistence, embeddings, Graph RAG, hooks and a bundled MCP server with configurable tool profiles.

Capability: Data & Databases
Resource type: SDK
Best fit: Local vector storage, semantic/hybrid retrieval and optional MCP code intelligence.

Representative uses

Store/search vectors
Run local RAG
Use code-intelligence hooks
Expose MCP tools with readonly/allow/deny profiles

Limitations

Native/WASM performance differs by platform.
MCP surface can be broad outside readonly profile.
Docs span multiple feature/version generations.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Local DB plus configured MCP profile.
Data handling: Designed for local storage; hooks can inspect code/files.
Cost: free
Risk and cautions: Local-first but broad tool profiles can expose more than simple vector CRUD; readonly profile is safer.

Access scope and cautions

Write actions: Vector insert/delete Persistent memory updates Optional local config/file outputs
Sensitive access: Embeddings Local code/data
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-07. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Store/search vectors; Run local RAG; Use code-intelligence hooks; Expose MCP tools with readonly/allow/deny profiles.

What setup information is documented?

Recorded installation/entrypoint step: npm install ruvector; npx ruvector mcp start. Recorded transport: stdio. Recorded environment-variable notes: RUVECTOR_MCP_ALLOW optional; RUVECTOR_MCP_DENY optional; RUVECTOR_MCP_PROFILE optional. No configuration values are supplied here. Prerequisites: Node/npm. These are the documented setup details, not a claim that installation or client compatibility was independently tested.

Can it modify data or perform write operations?

Documented write actions include: Vector insert/delete; Persistent memory updates; Optional local config/file outputs. Recorded permission boundary: Local DB plus configured MCP profile.

What data-handling boundary should I consider?

Designed for local storage; hooks can inspect code/files. Recorded sensitive-access context: Embeddings; Local code/data.

What limitations and risks should I check before use?

Local-first but broad tool profiles can expose more than simple vector CRUD; readonly profile is safer. Native/WASM performance differs by platform. MCP surface can be broad outside readonly profile. Docs span multiple feature/version generations. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

RUV / ruvnet is listed as First-party MCP in MCP100’s current evidence.