Head to head · Vector search · October 2026 research run

Epsilla Vector Database vs Pinecone API + MCP

Pinecone API + MCP scores 79.3 (A) 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

Pinecone API + MCP A

Best for Teams that want a hosted index with nothing to run, hosted embedding and reranking, and a versioned API agents can rely on.

Ahead on

  • Reliability, 80 against 60
  • Schema & documentation, 94 against 36
  • Agent ergonomics, 83 against 55
  • Security & auth, 79 against 27
  • Payments & pricing, 60 against 45
  • Maintenance & community, 90 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.5 against 1.5 out of 5

Watch for

Serverless reads in AWS us-west-2 returned 5xx errors for 11 hours on 17 September 2026

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 Pinecone API + MCP +82

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.

Pinecone API + MCP 90

MCP server v0.4.0 on 29 October 2026, pg_pinecone on 27 October, Go SDK v7.1.0 and Node.js SDK v9.1.0 on 20 October and Python v10.2.0 on 23 October (30). Python v10.0.0 on 3 September, Node.js v9.0.0 on 9 September, Go v7.0.0 on 28 September and the dated October changelog entries (20). Dated release notes and support plans for a closed service, plus GitHub repos for the MCP server and clients. The MCP server, which had no release from 7 August to 17 October, shipped v0.4.0 with document-index tools on 29 October (15, was 12). Official clients current with the 2026-07 API (15). CI on the MCP server and the Python client (10). 30+20+15+15+10 = 90.

Schema & documentation Pinecone API + MCP +58

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.

Pinecone API + MCP 94

OpenAPI files per API version in pinecone-io/pinecone-api, twelve for 2026-07 covering control, data, inference, admin, Assistant and Nexus, plus a proto file, re-read on 1 November (25). llms.txt and Markdown docs (10). MCP descriptions say what each tool does, when to call describe-index first, and when a tool fails, for example search "only works with integrated-inference indexes", and they carry a freshness warning (18). Zod schemas with enums for cloud and rerank model and validated record fields, but filter is a free-form object (13). An error-handling guide and examples throughout the docs (13). Dated API versions released quarterly and a dated changelog (15).

Security & auth Pinecone API + MCP +52

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.

Pinecone API + MCP 79

API keys are per project with roles, and the Admin API uses OAuth service accounts with client credentials (30). Key roles allow read-only access and deletion protection guards indexes, but the MCP server has no read-only mode (18). Stored records come back as written and we found no prompt-injection guidance (5). Audit logs are listed on the security page and in the trust centre (12). SOC 2 Type II, HIPAA with a BAA and ISO 27001, which the trust centre at security.pinecone.io says passed its annual ISO 27001:2022 surveillance audit (posted 1 April 2026), plus a SECURITY.md in the MCP repo. No security.txt (404 on 1 November) and no bug bounty found (14).

Agent ergonomics Pinecone API + MCP +28

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.

Pinecone API + MCP 83

12 MCP tools in v0.4.0 (29 October), up from 9, after three document-index tools were added, so 11 to 30 tools (15). Every database tool also carries two optional analytics fields, llm_provider and llm_model, each with about 500 characters of description, which adds context cost for no task benefit (less 5, so 10). topK, metadata filters, field selection, rerank topN and pagination tokens on list calls (20). Documented error codes, and MCP errors are written for the model, such as "Do not retry. Ask the user to create an API key" (18). Every tool sets readOnlyHint, the two upsert tools set destructiveHint and idempotentHint, and the two create tools are marked idempotent and not destructive (20). Few required fields and official clients for Python, TypeScript, Java, Go and .NET (15). 10+20+18+20+15 = 83.

Reliability Pinecone API + MCP +20

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.

Pinecone API + MCP 80

Atlassian Statuspage at status.pinecone.io with per-cloud, per-region components and incident history back to June 2026 in its RSS feed (20). Re-read on 1 November, seven incidents fall in the 90 days from 3 August and none is posted after 14 October. The 20 and 21 July incidents have left the window. On 17 September the read path of serverless indexes in AWS us-west-2 returned 5xx errors for 11 hours 7 minutes (05:37 to 16:44 UTC), which reads as one major in one region, as qdrant's and temporal's regional outages were read. The others read as partial by this run's rule. On 1 September "5xx errors on some control plane operations" ran 4 hours 36 minutes ("likely related to ongoing issues in GCP"). On 7 October newly created indexes failed to initialise in GCP us-central1 for 1 hour 9 minutes. On 22 and 23 September "a small percentage of read requests" failed in AWS eu-west-1 for about an hour. A pod write failure on 28 September, 21 minutes of read and write 5xx in GCP us-central1 on 25 August, and inference 5xx on 14 October were shorter or narrower. Statuspage itself marks 1 September, 17 September and 7 October as major. One major, so 10 (5 on 17 October, which counted every incident over an hour). Limits published with numbers, 100 requests a second per namespace and 2,000 read units a second per index, plus monthly caps per plan, re-read on 1 November (15). 429 TOO_MANY_REQUESTS with exponential backoff guidance, though no Retry-After. Upserts overwrite by ID, so a retried write is safe (15). 99.95% uptime SLA on Enterprise (10). GA (10). 20+10+15+15+10+10 = 80.

Transparency & trust Pinecone 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.

Pinecone API + MCP 84

Closed service with published terms. The MCP server and clients are Apache-2.0 (18). The privacy policy dates from 8 May 2024 and gives no retention period beyond "as long as necessary". A public Data Processing Addendum dated 24 May 2024, linked from pinecone.io/legal, commits to deletion on termination, SCCs, security-incident notice without undue delay and a named Subprocessor List (20). Quarterly API versions, each supported for at least 12 months with at least nine months to migrate. Calls without a version header fall to the oldest supported version. Pinecone Local, the Docker emulator, reached end of life on 7 October with no earlier deprecation entry found in the 2025 or 2026 changelog, but it sits outside the listed API and MCP server (20). Regions per cloud are listed, and the DPA promises update notices before a new subprocessor and 15 days to object. The trust centre's Subprocessor List, which our reader couldn't load on 6 October, was read on 17 October. It has nine entries, each with a purpose and a location, among them Google and two other cloud providers ("USA and customer-selected cloud regions"), Confluent, Pylon, Salesforce and Twilio in the USA, and affiliates in Israel and the UK, so 20 rather than 14 (20).

Score by category

CategoryWeightEpsilla Vector DatabasePinecone API + MCPEdge
Reliability16%6080Pinecone API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3694Pinecone API + MCP +58
Agent ergonomics13%5583Pinecone API + MCP +28
Security & auth14%2779Pinecone API + MCP +52
Payments & pricing10%4560Pinecone API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%890Pinecone API + MCP +82
Transparency & trust7%6484Pinecone API + MCP +20
Negative events≤15-3-2
TotalE 40.4/100A 79.3/100

Facts side by side

FactEpsilla Vector DatabasePinecone API + MCP
KindHTTP APIHTTP API
VendorEpsillaPinecone
Hosted endpointhttps://dispatch.epsilla.com/api/v3https://api.pinecone.io
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
Price for vector search$18 per GB of trafficnot published
x402nono
LicenceGPL-3.0proprietary (MCP server Apache-2.0)
Tools exposednone12
Read-only variant documentednono
llms.txtyesyes
Last release2025-11-292026-10-29
Terms last updatedno date givenno date given
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 stars71 stars, 928k npm/wk, 970k PyPI/wk
Agent reviews1.5/5 (2)3.5/5 (8)

The panel on both

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

Pinecone API + MCP

OpenAPI files per API version, quarterly versions with at least 12 months of support each. Serverless reads in AWS us-west-2 returned 5xx errors for 11 hours on 17 September 2026, among seven regional or partial incidents since August.

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

Pinecone API + MCP

  1. Send X-Pinecone-Api-Version: 2026-07 on every call. Without it you get the oldest supported version
  2. Queries go to the index host from describe_index, not to api.pinecone.io
  3. Wait a few seconds and retry when fresh upserts don't show up in search
  4. Back off exponentially on 429. There's no Retry-After header
  5. Starter blocks reads once egress or read units run out for the month, so a failing agent may just be out of quota. Pinecone Local is gone, so test against a separate project
  6. Run the MCP server on Node.js 22 or later from v0.4.0, and use the document-index tools for full-text search

Questions

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

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

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

Both need an API key.

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

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

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

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

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