Head to head · Vector search · October 2026 research run
LanceDB vs Upstash Vector API + MCP
Upstash Vector API + MCP and LanceDB score within a point of each other on agent readiness, 66.5 (B) and 66.3 (B). LanceDB leads on schema & documentation and maintenance & community. Both do vector search.
Best vector search and retrieval databases for AI agents · All 103 retrieval comparisons
Which one, for what
LanceDB B
Best for Agents whose code can import a library and keep retrieval data in object storage, from notebooks to multimodal datasets.
Ahead on
- Schema & documentation, 81 against 49
- Maintenance & community, 93 against 56
Also in its favour
- No key needed to call it
- Open source
Watch for
No self-serve hosted API. Enterprise is sold through a contact form
Best for Small to mid-sized agent memory and RAG where per-request pricing and zero setup matter more than search options.
Ahead on
- Agent ergonomics, 80 against 74
- Security & auth, 65 against 44
- Payments & pricing, 60 against 30
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
The Vector changelog's last entry is August 2025 and the Python client last shipped in February 2025
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community LanceDB +37
LanceDB 93
v0.41.0 on 29 October 2026 (30). v0.37.1 on 10 August, v0.38.0 on 31 August, v0.39.0 on 17 September, v0.40.0 on 7 October and v0.41.0, with daily betas between them, in the 90 days to 2 November (20). Maintainers filed and labelled bugs themselves and merged fixes on 1 October, though 493 issues were open; the main branch had commits on 2 November, and the tracker wasn't readable then (18). Python, TypeScript, Rust and Java clients ship from one version tag (15). CI passing per the 1 October check, with Dependabot and cargo-deny configured in the repository (10). Total 93.
Upstash Vector API + MCP 56
The Upstash MCP server package shipped v0.4.0 on 23 October 2026 (30). Besides declaring the stdio package no longer maintained and pointing to the hosted server, v0.4.0 is the first tag to carry the Box workspace tools merged on 31 August and a change to registry publishing, so it is read as a full release, as upstash-qstash read it on 1 November. v0.2.6 (7 August), v0.2.7 (13 August), v0.3.0 (24 August) and v0.4.0 fall in the 90 days from 4 August (20). None touched Vector. The npm package has no Vector tools, vector-js last shipped 1.2.3 on 9 March 2026 (its October commits bundle docs and fix JSDoc, untagged), vector-py 0.8.0 on 27 February 2025, and the Vector changelog's last entry is August 2025 (less 15). Public changelog and Discord support, with no reply data for the SDK repos (5). TypeScript client current, Python client 20 months old (8). CI on vector-js and the MCP server, which publishes to the official registry on release (8). 30 + 20 - 15 + 5 + 8 + 8 = 56.
Schema & documentation LanceDB +32
LanceDB 81
Typed Python, TypeScript and Rust APIs, and the Lance REST Namespace has an OpenAPI 3.1.1 spec in lance-format/lance-namespace. The docs' own Enterprise OpenAPI link, still listed in llms.txt, returned 404 again on 2 November (20 of 25). llms.txt indexes 235 links to Markdown pages (10). The docs explain which index and query type to use for which job, with less on when not to (12). Typed query builders and schemas, but filters are SQL strings (13). Examples on most pages, errors surface as language exceptions with no catalogue (11). Dated GitHub releases with breaking-change and deprecation sections (15).
Upstash Vector API + MCP 49
No OpenAPI file found for the Vector REST API. The hosted MCP server's 20 Vector and Search tools are listed by name and access on the docs page, but their input schemas aren't published (5 of 25). llms.txt and Markdown docs (10). Each REST endpoint page says what it does, with no when-not guidance (10). Typed request fields in the reference, but filters are a SQL-like string (10). curl and SDK examples on each page, and no error catalogue found (8). No API versioning, and the Vector changelog's last entry is August 2025 while the FAQ still says hybrid search isn't supported (6). The changelog was re-read on 2 November 2026 and still ends at August 2025. 5 + 10 + 10 + 10 + 8 + 6 = 49.
Payments & pricing Upstash Vector API + MCP +30
LanceDB 30
No x402, MPP or L402 (0). The only paid product, Enterprise, sits behind a contact form (0). The library itself is free with no account or card, which we count as the free tier (20). Getting the paid product needs a sales conversation (0). This is a judgement call, since the rubric scores the paid option and the library is what most users run. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Upstash Vector API + MCP 60
No x402, MPP or L402 (0). $0.40 per 100,000 requests, $0.25 per GB stored and $0.03 per GB of bandwidth over 200 GB, published without login and re-read on 2 November 2026 (20). Free plan with 10,000 queries and updates a day, no card per the 30 September check (20). A person signs up in the browser. The Developer API can create indexes, but only with an account key from a signed-up user (0). The Markdown pricing page's note to AI agents points to a no-signup Redis database, not a Vector index. 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Security & auth Upstash Vector API + MCP +21
LanceDB 44
The library has no auth of its own and uses the host's object-store credentials. Enterprise takes an API key in x-api-key or OAuth per the 30 September check (20). Least privilege depends on read-only bucket credentials. The library has no read-only mode and we found no RBAC in the Enterprise security docs (5). Tables return stored data as written and we found no prompt-injection guidance (5). No audit log found (0). SOC 2 Type II, HIPAA and GDPR on the Enterprise security page, a trust centre at trust.lancedb.com and a valid security.txt (security@lancedb.com, expires 31 July 2027, re-read on 2 November), but no SECURITY.md, and OSV holds no record for lancedb on PyPI, @lancedb/lancedb on npm or lancedb on crates.io (14). Total 44.
Upstash Vector API + MCP 65
Each index has its own REST token and a separate read-only token, the Developer API uses account API keys with a read-only option, and the hosted MCP server defaults to OAuth with a per-client, revocable grant (28). Read-only tokens, read-only MCP grants and destructive labels on tools; MCP management tools return credentials only with include_credentials: true (20). Stored text comes back as written and we found no prompt-injection guidance (5). No audit log found (0). Valid security.txt (Expires 29 September 2027) pointing to a vulnerability disclosure policy with safe harbour and rewards for critical findings, whose scope names Vector, plus third-party pen tests, as upstash-qstash was read on 1 November. SOC 2 still covers Redis on Pro and Enterprise only and ISO 27001 is in progress (12 of 20, up from 10). 28 + 20 + 5 + 0 + 12 = 65.
Agent ergonomics Upstash Vector API + MCP +6
LanceDB 74
No official MCP server, only a 3-tool reference example, so an agent needs code or its own wrapper (15). select(), limit(), offset(), where() and query types to size and filter results (20). Errors are typed exceptions without documented codes (12). merge_insert gives upserts, and writes create new table versions you can roll back to, but there are no tool annotations to read (12). Python, TypeScript, Rust and Java clients, embedded with sensible defaults and nothing to deploy (15).
Upstash Vector API + MCP 80
The hosted MCP server now lists 74 tools across Redis, QStash, Workflow, Vector, Search, Box, Blob and a console, of which 20 are for Vector and Search (5). ?features=vector_search scopes the server to those 20, and a read-only key or grant switches off every write tool (10 back, up from 5 when only the read-only mode was credited). topK, metadata filters, includeMetadata, includeVectors and includeData, namespaces, cursor-based range and resumable queries (20). Error responses aren't documented as a list (10). Upserts by ID are safe to repeat, and each MCP tool is labelled read, write or destructive (20). With hosted embedding, upsert-data and query-data take plain text. Official clients for TypeScript, Python and PHP (15). 15 + 20 + 10 + 20 + 15 = 80.
Score by category
| Category | Weight | LanceDB | Upstash Vector API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 75 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 49 | LanceDB +32 |
| Agent ergonomics | 13% | 74 | 80 | Upstash Vector API + MCP +6 |
| Security & auth | 14% | 44 | 65 | Upstash Vector API + MCP +21 |
| Payments & pricing | 10% | 30 | 60 | Upstash Vector API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 93 | 56 | LanceDB +37 |
| Transparency & trust | 7% | 75 | 77 | Upstash Vector API + MCP +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 66.3/100 | B 66.5/100 |
Facts side by side
| Fact | LanceDB | Upstash Vector API + MCP |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | LanceDB | Upstash |
| Hosted endpoint | no (local only) | https://api.upstash.com/v2 |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | none | 74 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.upstash/mcp-server |
| Last release | 2026-10-29 | 2026-10-23 |
| Popularity | 12k stars, 922k npm/wk, 1.9M PyPI/wk | 70 stars, 187k npm/wk, 34k PyPI/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | LanceDB | Upstash Vector API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 A breaking minor every few weeks, all flagged | 2/5 BGE closed to new indexes, no date given |
| LedgerCost analyst | 3/5 $0 for the library, and a contact form for everything else | 4/5 $0.004 per 1,000 requests, and a free plan with no card |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
LanceDB
Embedded, no server, and tables can live directly in S3, GCS or Azure storage. No self-serve hosted API. Enterprise is sold through a contact form.
Upstash Vector API + MCP
$0.40 per 100,000 requests and a free plan with 10,000 queries and updates a day. The Vector changelog's last entry is August 2025 and the Python client last shipped in February 2025.
Before you call either
LanceDB
- Use it through the Python or TypeScript library. There's no public endpoint an agent can call without an Enterprise deployment
- Build an FTS index before calling
query_type="hybrid", or hybrid search has no keyword side - When reopening a table in a new process, approve its embedding model or endpoint with
get_registry().allow_remote_code()orallow_endpoint(), since v0.41.0 refuses settings restored from table metadata - Use
select()to drop the vector column from results unless the task needs it - On object storage, set a read consistency interval if several processes write the same table
Upstash Vector API + MCP
- Connect to mcp.upstash.com/mcp for Vector tools.
npx @upstash/mcp-serverhas none - Create the index with an embedding model if the agent works in text; then
query-dataandupsert-datatake strings - Give retrieval-only agents the index's read-only token, not the full one
- Filters use a SQL-like string (
genre = 'fiction' AND year > 2020) in thefilterfield - Ignore the FAQ line saying hybrid isn't supported. Pass
queryModeHYBRID, DENSE or SPARSE on hybrid indexes
Questions
Which is better for AI agents, LanceDB or Upstash Vector API + MCP?
Upstash Vector API + MCP and LanceDB score within a point of each other on agent readiness, 66.5 (B) and 66.3 (B). LanceDB leads on schema & documentation and maintenance & community.
Can an agent call LanceDB and Upstash Vector API + MCP without installing anything?
No hosted endpoint is listed for LanceDB. Upstash Vector API + MCP has a hosted endpoint at https://api.upstash.com/v2.
Are LanceDB and Upstash Vector API + MCP open source?
LanceDB is open source (Apache-2.0). No open-source release is listed for Upstash Vector API + MCP.
Other comparisons with LanceDB or Upstash Vector API + MCP
- Chroma API + MCP vs LanceDB
- Chroma API + MCP vs Upstash Vector API + MCP
- Elasticsearch vs LanceDB
- Elasticsearch vs Upstash Vector API + MCP
- Epsilla Vector Database vs LanceDB
- Epsilla Vector Database vs Upstash Vector API + MCP
- LanceDB vs Meilisearch
- LanceDB vs Milvus and Zilliz Cloud API + MCP
- LanceDB vs OpenSearch
- LanceDB vs Pinecone API + MCP
- LanceDB vs Qdrant API + MCP
- LanceDB vs Typesense API + MCP
- LanceDB vs Vespa
- LanceDB vs Weaviate API + MCP
- Meilisearch vs Upstash Vector API + MCP
- Milvus and Zilliz Cloud API + MCP vs Upstash Vector API + MCP
- OpenSearch vs Upstash Vector API + MCP
- Pinecone API + MCP vs Upstash Vector API + MCP
- Qdrant API + MCP vs Upstash Vector API + MCP
- Typesense API + MCP vs Upstash Vector API + MCP
- Upstash Vector API + MCP vs Vespa
- Upstash Vector API + MCP vs Weaviate API + MCP
- Cloudflare AI Search vs LanceDB
- Cloudflare AI Search vs Upstash Vector API + MCP
Machine-readable
- This page as Markdown
/compare/lancedb-vs-upstash-vector.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lancedb.json·/api/v1/tools/upstash-vector.json - From a terminal
anchor compare lancedb upstash-vector(the CLI) - Over MCP
compare_tools {"a": "lancedb", "b": "upstash-vector"}at/mcp, no key