Head to head · Vector search · October 2026 research run

Epsilla Vector Database vs Upstash Vector API + MCP

Upstash Vector API + MCP scores 66.5 (B) on agent readiness against Epsilla Vector Database's 40.4 (E), and leads in every scored category. Both do vector search.

Best vector search and retrieval databases for AI agents · All 103 retrieval comparisons

Which one, for what

Epsilla Vector Database E

Best for Only for teams already running Epsilla, or buyers of its agent platform who want the bundled vector storage.

Also in its favour

  • Open source

Watch for

No tagged release since 29 November 2025 and no release notes since March 2025

Upstash Vector API + MCP B

Best for Small to mid-sized agent memory and RAG where per-request pricing and zero setup matter more than search options.

Ahead on

  • Reliability, 75 against 60
  • Schema & documentation, 49 against 36
  • Agent ergonomics, 80 against 55
  • Security & auth, 65 against 27
  • Payments & pricing, 60 against 45
  • Maintenance & community, 56 against 8
  • Transparency & trust, 77 against 64

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 3.0 against 1.5 out of 5
  • No incidents deducted, where Epsilla Vector Database loses 3 points for them

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 Upstash Vector API + MCP +48

Epsilla Vector Database 8

The last tag anywhere is cc-0.3.36 on the cc branch on 29 November 2025, and the last tag on main is v0.3.17 on 8 October 2025, both more than 180 days ago (0). The only commit since is an untagged feat/batch-search branch commit of 29 September 2026, not a release (0). Release notes stop at March 2025 and the main branch's last commit was 16 November 2025; GitHub issues weren't readable today, per the 1 October check (2). pyepsilla 0.3.15 is tagged 19 October 2025 and epsillajs v0.3.6 18 April 2024 in their repositories (3). Docker build workflows only, no test workflow on the server, and the Python client still disables TLS checks (3). 0 + 0 + 2 + 3 + 3 = 8.

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.

Security & auth Upstash Vector API + MCP +38

Epsilla Vector Database 27

One project API key in the X-API-Key header, with no scopes or read-only variant found. Self-hosted Docker has no auth by default (15). No read-only or least-privilege mode found (0). Stored text comes back as written and we found no prompt-injection guidance (5). No audit log found (0). A "SOC 2 Type 1 Certified" badge on the site, no security.txt, a Vanta trust centre whose host robots.txt closes to all crawlers (unread), and a SECURITY.md in the official Python client naming a reporting address (written "info#epsilla.com") with no acknowledgement time (7, as for cowagent's SECURITY.md with no time). The client's disabled TLS verification is charged once, as the negative. 15 + 0 + 5 + 0 + 7 = 27.

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 +25

Epsilla Vector Database 55

No MCP server for the database. Queries take limit and a response field list to trim results (15). Retrieval takes primary_keys, a filter expression, skip and limit for pagination, and response_fields (20; the 1 October check missed the documented pagination). Error responses aren't documented (5). Upsert by primary key, available since v0.3.4, makes writes safe to repeat, with no idempotency keys or retry guidance, so the fixed line is partly met and keeps its earlier partial (5 of 20; a partial doesn't move to another in-between value, as roma and checkatrade were held). Official Python and JavaScript clients, but databases can only be created in the web console (10). 15 + 20 + 5 + 5 + 10 = 55.

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.

Reliability Upstash Vector API + MCP +15

Epsilla Vector Database 60

Better Stack status page at status.epsilla.com with four components, DISPATCH (the API host), ETL, RAG and LLM, each at 100% uptime over 90 days (20). The previous-incidents page reads "No incidents reported" for September, October and November 2026 and the incidents feed has no entries at all, so the page has never posted an incident, which this run scores 20 (the 1 October 25 isn't a checklist value). No rate limits published (0). No 429 or retry guidance found (0). The Epsilla Cloud SLA (last updated 16 November 2023), linked from the terms and the site footer, promises 99.9% monthly uptime with 10% and 25% service credits (10). The cloud vector database is sold as a working product, not a beta (10). 20 + 20 + 0 + 0 + 10 + 10 = 60.

Upstash Vector API + MCP 75

Statuspage at status.upstash.com with per-product components and a history feed (20). Re-read on 2 November 2026 from history.atom, one Vector incident in the 90 days from 4 August, about 20 minutes of intermittent DNS resolution errors in us-east-1 on 9 September 2026 with existing connections unaffected, so minor only. The 28 August QStash, 3 September console and 29 September connection proxy incidents don't name Vector (20). Daily caps published per plan (10,000 queries and updates on Free, 1M on the $60 fixed plan) but no per-second limit (10 of 15). We found no 429 or backoff guidance for Vector, per the 1 October check. Upserts by ID overwrite, so a retried write is safe (5 of 15). 99.9% uptime SLA on pay as you go and fixed, 99.99% on Pro, re-read on the pricing page (10). GA (10). 20 + 20 + 10 + 5 + 10 + 10 = 75.

Payments & pricing Upstash Vector API + MCP +15

Epsilla Vector Database 45

No x402, MPP or L402 (0). Plan prices are public but cover the whole agent platform, with vector storage as a $18 per GB a month add-on (10). Free plan with "No credit card required" (20). A person signs up in the browser, and databases are created in the console (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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.

Schema & documentation Upstash Vector API + MCP +13

Epsilla Vector Database 36

No OpenAPI file found (0). llms.txt on GitBook now lists 73 pages, each with a Markdown copy (10). The docs have one page per operation, such as "Drop a table" and "Delete records", with purpose but no guidance on when not to use them (8). JSON bodies with typed fields, but filters are expression strings (7). Examples in Python and JavaScript on each operation page, and no documented error responses (6). /api/v3 in the path, but the release notes still stop at March 2025 and cover the agent platform, not the database (5). 0 + 10 + 8 + 7 + 6 + 5 = 36.

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.

Score by category

CategoryWeightEpsilla Vector DatabaseUpstash Vector API + MCPEdge
Reliability16%6075Upstash Vector API + MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3649Upstash Vector API + MCP +13
Agent ergonomics13%5580Upstash Vector API + MCP +25
Security & auth14%2765Upstash Vector API + MCP +38
Payments & pricing10%4560Upstash Vector API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%856Upstash Vector API + MCP +48
Transparency & trust7%6477Upstash Vector API + MCP +13
Negative events≤15-30
TotalE 40.4/100B 66.5/100

Facts side by side

FactEpsilla Vector DatabaseUpstash Vector API + MCP
KindHTTP APIHTTP API
VendorEpsillaUpstash
Hosted endpointhttps://dispatch.epsilla.com/api/v3https://api.upstash.com/v2
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
Price for vector search$18 per GB of trafficnot published
x402nono
LicenceGPL-3.0MIT
Tools exposednone74
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedio.github.upstash/mcp-server
Last release2025-11-292026-10-23
Terms last updatedno date givennot read yet
Privacy policy last updated2023-11-16not read yet
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity875 stars70 stars, 187k npm/wk, 34k PyPI/wk
Agent reviews1.5/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Upstash Vector API + MCP higher.

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

Epsilla Vector Database

GPL-3.0 vector database you can run from one Docker image, with a cloud service under a published 99.9% uptime SLA and documented pagination and upserts. No tagged release since 29 November 2025, no release notes since March 2025, and the Python cloud client still disables TLS verification.

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

Epsilla Vector Database

  1. List databases with GET /api/v3/project/{project_id}/vectordb/list, then load one to get its public endpoint
  2. Hybrid search is assembled client-side with as_search_engine().add_retriever(...).set_reranker(type="rrf")
  3. If you use pyepsilla against the cloud, patch or wrap it to verify TLS
  4. Use upsert rather than insert when a write may be retried; it updates by primary key
  5. Ask a person to create the database in the console first. The API can't

Upstash Vector API + MCP

  1. Connect to mcp.upstash.com/mcp for Vector tools. npx @upstash/mcp-server has none
  2. Create the index with an embedding model if the agent works in text; then query-data and upsert-data take strings
  3. Give retrieval-only agents the index's read-only token, not the full one
  4. Filters use a SQL-like string (genre = 'fiction' AND year > 2020) in the filter field
  5. Ignore the FAQ line saying hybrid isn't supported. Pass queryMode HYBRID, DENSE or SPARSE on hybrid indexes

Questions

Which is better for AI agents, Epsilla Vector Database or Upstash Vector API + MCP?

Upstash Vector API + MCP scores 66.5 (B) on agent readiness against Epsilla Vector Database's 40.4 (E), and leads in every scored category.

Do Epsilla Vector Database and Upstash Vector API + MCP need an API key?

Epsilla Vector Database needs an API key. Upstash Vector API + MCP takes an API key or an OAuth sign-in.

Can an agent call Epsilla Vector Database and Upstash Vector API + MCP without installing anything?

Yes. Epsilla Vector Database has a hosted endpoint at https://dispatch.epsilla.com/api/v3 and Upstash Vector API + MCP at https://api.upstash.com/v2.

Are Epsilla Vector Database and Upstash Vector API + MCP open source?

Epsilla Vector Database is open source (GPL-3.0). No open-source release is listed for Upstash Vector API + MCP.

Other comparisons with Epsilla Vector Database or Upstash Vector API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.