Ext Ops Panel
Open dashboard
Comparison

Vector Search API vs Local Vector Search MCP

Vector Search API is an MCP server published by Br0ski777. Marketplaces we read that list it: 1 (Official MCP Registry). Local Vector Search MCP is an MCP server published by DimonSmart. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceVector Search APILocal Vector Search MCP
Official MCP Registry Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.3
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Vector Search API vs Local Vector Search MCP
FactVector Search APILocal Vector Search MCP
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-12
Where it runs (differs)Remote server (vector-search.api.klymax402.com/mcp)On your machine (DimonSmart.LocalVectorSearchMcp)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/br0ski777/vector-search-x402github.com/dimonsmart/localvectorsearchmcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)No HTTP response at the last check (10 h ago)no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Vector Search API

In its own words, on Official MCP Registry:

In-memory vector search with TF-IDF and cosine similarity. x402 micropayment.

Local Vector Search MCP

In its own words, on Official MCP Registry:

Local Markdown search, navigation and editing via MCP, with optional vector embeddings.

How to run each

Vector Search API As a remote MCP server

Claude Code
claude mcp add --transport sse vector-search https://vector-search.api.klymax402.com/mcp

Local Vector Search MCP

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Vector Search API has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Vector Search API · What it can do: Local Vector Search MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built