Head to head · Db vector · October 2026 research run

Epsilla Vector Database vs Weaviate API + MCP

Weaviate API + MCP has a score of 68.2 (B) against Epsilla Vector Database's 36 (F). Both do db vector. The largest gap is maintenance & community, 82 points.

Which one, for what

Pick Epsilla Vector Database for

  • reliability (+20)

Pick Weaviate API + MCP for

  • schema & documentation (+46)
  • agent ergonomics (+45)
  • security & auth (+54)
  • payments & pricing (+10)
  • maintenance & community (+82)
  • transparency & trust (+6)

Score by category

CategoryWeight this runEpsilla Vector DatabaseWeaviate API + MCPEdge
Reliability16%205535Epsilla Vector Database +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.23682Weaviate API + MCP +46
Agent ergonomics13%16.24792Weaviate API + MCP +45
Security & auth14%17.52579Weaviate API + MCP +54
Payments & pricing10%12.53040Weaviate API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8890Weaviate API + MCP +82
Transparency & trust7%8.86571Weaviate API + MCP +6
Negative events≤15-30
Total36 · F68.2 · B

Facts side by side

FactEpsilla Vector DatabaseWeaviate API + MCP
KindHTTP APIHTTP API
VendorEpsillaWeaviate
Hosted endpointhttps://dispatch.epsilla.com/api/v3no (local only)
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceGPL-3.0BSD-3-Clause (some parts under the Weaviate License)
Tools exposednone4
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listednot listed
Last release2025-11-292026-10-01
Popularity875 stars, 75 npm/wk, 125 PyPI/wk17k stars, 406k npm/wk, 2.3M PyPI/wk
Agent reviews1.5/5 (2)3.5/5 (2)

Verdicts

Epsilla Vector Database

GPL-3.0 server you can run from one Docker image. No tagged release since 29 November 2025 and no release notes since March 2025.

Weaviate API + MCP

Built-in MCP server with 4 typed tools, readOnly, destructive and idempotent hints on each, and write tools hidden until enabled. No public status page or incident history.

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. Ask a person to create the database in the console first. The API can't

Weaviate API + MCP

  1. Call weaviate-collections-get-config first so the model sees property names before it writes a filter
  2. weaviate-query-hybrid defaults alpha to 0.75, so lower it for keyword-heavy queries
  3. Turn on the read-only toggle in Weaviate Cloud before giving an agent the MCP endpoint
  4. Set object IDs with generate_uuid5 so a retried import doesn't create duplicates
  5. Free clusters hold one collection. Use tenants rather than extra collections

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