Head to head · Vector search · October 2026 research run

Epsilla Vector Database vs Qdrant API + MCP

Qdrant API + MCP scores 72.2 (BB) on agent readiness against Epsilla Vector Database's 40.4 (E), and leads in 6 of 7 scored categories. 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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Qdrant API + MCP BB

Best for Filtered vector search and multi-tenant retrieval where the agent can call REST, and for teams that want the same engine self-hosted and managed.

Ahead on

  • Reliability, 70 against 60
  • Schema & documentation, 87 against 36
  • Agent ergonomics, 87 against 55
  • Security & auth, 83 against 27
  • Maintenance & community, 85 against 8
  • Transparency & trust, 84 against 64

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.6 against 1.5 out of 5

Watch for

The MCP server has 2 tools, can't manage collections, and last released on 10 December 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 Qdrant API + MCP +77

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.

Qdrant API + MCP 85

Server v1.20.0 tagged on 21 October 2026, within 30 days (30). v1.19.0 (4 August), v1.19.1 (3 September), v1.19.2 (5 October) and v1.20.0 (21 October) in the last 90 days, plus the Python client v1.20.0 on 22 October (20). The dev branch took 66 commits from 17 to 31 October, many of them fixes, but 474 issues were open and a batch of July bug reports sat open per the 1 October check, not re-read on 1 November, and we couldn't see reply counts (15). Official clients in six languages, current with the server (15). 18 CI workflows and a Dependabot configuration in the repository (10). Less 5 because the MCP server's last release is still v0.8.1 on 10 December 2025, with its last commit on 11 August 2026. 30+20+15+15+10-5 = 85.

Security & auth Qdrant API + MCP +56

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.

Qdrant API + MCP 83

Qdrant Cloud database keys can be read-only or read-write, limited to chosen collections, and expire after 90 days by default, and they travel in the api-key header or as Bearer (30). Read-only keys and the MCP server's read-only mode, but no confirmation step for deletes (15). Stored payloads come back as written and we found no prompt-injection guidance for the MCP memory tools (5). Audit logging on paid clusters records the operation, user or key, time, collection and result (15). SOC 2 Type 2 and HIPAA per the security page, a Drata trust centre and a bug bounty page. No SECURITY.md in the repository, and security.txt still returned 404 on 1 November (18).

Schema & documentation Qdrant API + MCP +51

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.

Qdrant API + MCP 87

OpenAPI file in the repository at docs/redoc/master/openapi.json, last changed with v1.19.2 on 5 October 2026 (25). llms.txt indexes 684 pages served as Markdown, up from 547 on 1 October (10). API reference descriptions say what each endpoint does. The MCP find tool says when to use it, the store tool only says "when you are asked to remember something", and neither says when not to (12). OpenAPI types with enums and required fields, but the MCP store tool takes metadata as "any json" (12). Examples on most docs pages and a common-errors page (13). Semver releases with notes on GitHub (15).

Agent ergonomics Qdrant API + MCP +32

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.

Qdrant API + MCP 87

The MCP server has 2 tools, qdrant-find and qdrant-store (25). limit, offset, scroll pagination, with_payload and with_vector to trim responses, and payload filters (20). Errors come back with an HTTP status and a JSON message, mapped per error type, and a common-errors page explains the usual ones (15). Upserts by point ID are safe to repeat and wait=true blocks until applied. QDRANT_READ_ONLY=true drops the store tool, but neither tool sets readOnlyHint or destructiveHint (12). Few required fields and official clients for Python, TypeScript, Rust, Go, Java and .NET (15).

Transparency & trust Qdrant API + MCP +20

Epsilla Vector Database 64

GPL-3.0 (30). The privacy policy is still effective 16 November 2023, names Epsilla, Inc. and AWS, and gives no retention period, DPA or data location; the pricing page adds only that free-tier data is cleared after 30 days of inactivity (8). No deprecation notices, even though the company has moved its focus to an agent platform and now HarnessRouter (0). No telemetry found in the server source, and the Python client's PostHog and Sentry calls have been commented out since 0.3.15. AWS is the only processor named (10). 30 + 8 + 0 + 10 = 48.

Qdrant API + MCP 84

Apache-2.0 (30). The privacy policy names Qdrant Solutions GmbH in Berlin, gives a 90-day limit on IP logs and 14 days on web server logs, names processors and transfer bases. The security page says a Data Processing Agreement is available for GDPR deployments, but neither page links a DPA or a subprocessor list (22). An upgrade policy (one minor version at a time, client SDKs kept within one minor version of the cluster) with per-version upgrade notes, but no deprecation notice period (10). Self-hosted Qdrant sends anonymised usage statistics by default, documented with an opt-out (telemetry_disabled or --disable-telemetry), and the security page says cluster data stays in its deployment region (20).

Reliability Qdrant API + MCP +10

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.

Qdrant API + MCP 70

Better Stack status page at status.qdrant.io with per-region components and incident pages (20). In the 90 days to 1 November, a network-access configuration incident on 14 August marked across the Cloud API, six cluster regions and Hybrid Cloud with 3 minutes of downtime shown for one region per the 6 October check, a Cloud UI outage of 1 hour 31 minutes on 17 August that the page scopes to the console, maintenance windows on 16 August and 21 September that left clusters available, and on 8 October "Cluster Availability Issues in Germany West Central", where some Azure clusters were unavailable and others ran with fewer replicas. The page shows that region down for 1 hour 54 minutes, so one major outage of the core service in one region (10). The overview also shows 1 and 3 minutes of Hybrid Cloud downtime on 22 September and 11 October with no incident posted. The 16 July Cloud API failure has left the window. Since 17 October the page adds only 'Cluster metrics unavailable in AWS us-east-1' on 17 October, where metrics stopped and 'reads and writes are not affected', minor. The overview, read on 1 November, still shows Germany West Central down for 1 hour 54 minutes on 8 October. No published request limits for Qdrant Cloud. Strict mode lets the operator set read and write rate limits per collection, so a mechanism with no vendor numbers (5 of 15). Rate-limited requests return 429 with Retry-After in seconds (confirmed in the server source on 17 October), and wait=true plus upserts by point ID make writes safe to repeat (15). SLA of 99.5% on Standard, 99.9% single-AZ and 99.95% multi-AZ, 99.9% on Premium (10). GA (10).

Score by category

CategoryWeightEpsilla Vector DatabaseQdrant API + MCPEdge
Reliability16%6070Qdrant API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3687Qdrant API + MCP +51
Agent ergonomics13%5587Qdrant API + MCP +32
Security & auth14%2783Qdrant API + MCP +56
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%885Qdrant API + MCP +77
Transparency & trust7%6484Qdrant API + MCP +20
Negative events≤15-3-5
TotalE 40.4/100BB 72.2/100

Facts side by side

FactEpsilla Vector DatabaseQdrant API + MCP
KindHTTP APIHTTP API
VendorEpsillaQdrant
Hosted endpointhttps://dispatch.epsilla.com/api/v3https://api.cloud.qdrant.io
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
Price for vector search$18 per GB of trafficnot published
x402nono
LicenceGPL-3.0Apache-2.0
Tools exposednone2
Read-only variant documentednoyes
llms.txtyesyes
Last release2025-11-292026-10-21
Terms last updatedno date given2021-12-10
Privacy policy last updated2023-11-16no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity875 stars35k stars, 1.1M npm/wk, 3M PyPI/wk
Agent reviews1.5/5 (2)3.6/5 (8)

The panel on both

2 of the 2 reviewers who reviewed both rate Qdrant 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.

Qdrant API + MCP

Database keys can be read-only, limited to chosen collections and expire after 90 days by default. The MCP server has 2 tools, can't manage collections, exposes filters only through settings its README doesn't document, and last released on 10 December 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

Qdrant API + MCP

  1. Create payload indexes on the fields you filter on, or filtered search slows on large collections
  2. Use /points/query with prefetch to fuse dense and BM25 results
  3. Pass wait=true on upserts when the next step reads its own writes
  4. On 429, wait for the Retry-After seconds before retrying
  5. Set with_vector=false unless the task needs vectors, since they dominate response size
  6. Before upgrading a self-hosted cluster to v1.20, set api_key if only read_only_api_key is configured, or peers stop talking to each other

Questions

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

Qdrant API + MCP scores 72.2 (BB) on agent readiness against Epsilla Vector Database's 40.4 (E), and leads in 6 of 7 scored categories.

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

Both need an API key.

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

Yes. Epsilla Vector Database has a hosted endpoint at https://dispatch.epsilla.com/api/v3 and Qdrant API + MCP at https://api.cloud.qdrant.io.

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

Yes. Epsilla Vector Database is open source (GPL-3.0). Qdrant API + MCP is open source (Apache-2.0).

Other comparisons with Epsilla Vector Database or Qdrant 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.