Head to head · Vector search · October 2026 research run

Chroma API + MCP vs Upstash Vector API + MCP

Upstash Vector API + MCP scores 66.5 (B) on agent readiness against Chroma API + MCP's 50.1 (D), and leads in 6 of 7 scored categories. Chroma API + MCP leads on schema & documentation. Both do vector search.

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

Which one, for what

Chroma API + MCP D

Best for Agent memory and small to mid-sized corpora where an in-process store or a serverless bill by the GiB suits.

Ahead on

  • Schema & documentation, 66 against 49

Also in its favour

  • Runs on your own machine
  • Open source

Watch for

Six advisories against chromadb, two Critical and four High, have no patched release as of 5 November 2026

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
  • Agent ergonomics, 80 against 73
  • Security & auth, 65 against 42
  • Payments & pricing, 60 against 45
  • Maintenance & community, 56 against 35

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Chroma API + MCP loses 7 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.

Security & auth Upstash Vector API + MCP +23

Chroma API + MCP 42

Chroma Cloud keys go in x-chroma-token and are tied to a tenant and database per the 30 September check, with no other scopes found. A local or self-hosted server runs with no auth unless configured (20). No read-only key, and the MCP server has no read-only mode, though a key limited to one database narrows the reach (5). Stored documents come back as written, including pages pulled in by Sync from the web, and we found no prompt-injection guidance (5). No audit log found (0). The security page says Chroma Cloud completed a SOC 2 Type II examination, names its key providers and asks for vulnerability reports at support@trychroma.com, with no acknowledgement time. No security.txt or bug bounty found, the MCP repository's SECURITY.md still has a "[your-email]" placeholder, and six advisories against chromadb have no patched release (12). 20 + 5 + 5 + 0 + 12 = 42.

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.

Maintenance & community Upstash Vector API + MCP +21

Chroma API + MCP 35

Newest release is the JavaScript client 3.5.0 on 30 June 2026, per the 1 October check, 128 days before this one. The server and Python package last tagged 1.5.9 on 4 May 2026 (10). Nothing tagged or dated in the 90 days from 7 August. A commit on 13 October set the version to 1.6.0 ("Bug fix release"), but no 1.6.0 tag exists and PyPI couldn't be read, so it isn't counted (0). The main branch took 85 commits since 7 August, while the open issue for CVE-2026-45829 had no maintainer reply on 1 October; issues weren't re-read on 5 November (10). Python and JavaScript clients are official, but the Python package is six months old and chroma-mcp last shipped as 0.2.6 on 14 August 2025, pinned to chromadb 1.0.16, and isn't in the official MCP registry (10). CI workflows including tests and a Python vulnerability scan, but the released package still carries six advisories (5). 10 + 0 + 10 + 10 + 5 = 35.

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 Chroma API + MCP +17

Chroma API + MCP 66

Each Chroma API reference page's Markdown version shows an OpenAPI 3.1.0 fragment for its operation, drawn from https://api.trychroma.com/openapi.json, which no docs page links as a download. Per-page fragments take 20, as on lucid (20). llms.txt indexes 179 pages on 5 November, each served as Markdown (10). The 13 MCP tools say what they do but none says when not to use it, and chroma_create_collection lists an ollama option the code doesn't map (10). Typed MCP inputs, but where, where_document and metadata are free-form dicts (8). Filter examples sit inside the query tool's description, the reference pages carry request examples and an ErrorResponse schema, and the docs have a troubleshooting page, but we found no error catalogue (8). /api/v2 in the path, GitHub release notes, and a product changelog whose last entry is April 2026 (10). 20 + 10 + 10 + 8 + 8 + 10 = 66.

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.

Reliability Upstash Vector API + MCP +15

Chroma API + MCP 60

Instatus page at status.trychroma.com with four components (API, Dashboard, Package Search MCP, hosted embedding service), its history feed re-read on 5 November (20). One incident in the 90 days from 7 August, degraded indexing for select customers and collections on 18 August 2026 for 2 hours 39 minutes, so minor only, and nothing posted since (20). Chroma Cloud quotas are published with numbers, but as concurrency and size caps (10 concurrent reads and 10 writes per collection, 300 records a write, 300 results a query), not as requests a second (10 of 15). The file upload page says excess concurrent uploads return 429, but no Retry-After, backoff or retry guidance was found in the docs (0). Enterprise lists "SLAs" with no figure, and nothing for Team (0). Chroma Cloud isn't marked beta or preview (10). 20 + 20 + 10 + 0 + 0 + 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

Chroma API + MCP 45

No x402, MPP or L402 (0). Per-unit prices published without login, $2.50 per GiB written, $0.33 per GiB a month stored, $0.0075 per TiB scanned and $0.09 per GiB returned (20). $5 of credit for new users, but neither the pricing page nor the pricing docs say whether a card is needed (10 of 20). A person signs up in the browser to get a key. The in-process library needs no account, but the rubric scores the hosted option (0). Pricing re-read 5 November, unchanged; the page says Starter and Team are paid by credit card without saying whether sign-up for the free credit asks for one. 0 + 20 + 10 + 0 = 30. 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.

Agent ergonomics Upstash Vector API + MCP +7

Chroma API + MCP 73

13 MCP tools, in the 11 to 30 band (15). The API and the query tool take include to drop embeddings or documents from the response (3 back). limit and offset on list and get, n_results, metadata and document filters, and pagination and field selection in the Search API (20). MCP errors come back as "Failed to ... " plus the raw exception text, and we found no documented error codes (10). upsert makes writes safe to repeat, but the MCP tools carry no readOnlyHint or destructiveHint, including chroma_delete_collection (10). Only the collection name and query text are required. Official Python and JavaScript clients (15). 15 + 3 + 20 + 10 + 10 + 15 = 73.

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

CategoryWeightChroma API + MCPUpstash Vector API + MCPEdge
Reliability16%6075Upstash Vector API + MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6649Chroma API + MCP +17
Agent ergonomics13%7380Upstash Vector API + MCP +7
Security & auth14%4265Upstash Vector API + MCP +23
Payments & pricing10%4560Upstash Vector API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3556Upstash Vector API + MCP +21
Transparency & trust7%7477Upstash Vector API + MCP +3
Negative events≤15-70
TotalD 50.1/100B 66.5/100

Facts side by side

FactChroma API + MCPUpstash Vector API + MCP
KindHTTP APIHTTP API
VendorChromaUpstash
Hosted endpointhttps://api.trychroma.com/api/v2https://api.upstash.com/v2
TransportsHTTP, stdioHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicenceApache-2.0MIT
Tools exposed1374
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedio.github.upstash/mcp-server
Last release2026-06-302026-10-23
Terms last updated2024-10-02not read yet
Privacy policy last updated2024-10-02not 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 noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Popularitynone70 stars, 187k npm/wk, 34k PyPI/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

Chroma API + MCP

Runs in-process, as a local server or serverless on Chroma Cloud with the same v2 API, with per-unit cloud prices published. Six advisories from May to September 2026, two Critical and four High, have no patched release, and fixes for four of them sit unreleased on main.

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

Chroma API + MCP

  1. Don't expose a self-hosted chromadb 1.5.9 server. It has no auth by default and four unpatched advisories, two of them code execution
  2. Don't rely on SimpleRBACAuthorizationProvider to keep tenants apart on a self-hosted server
  3. Batch writes in groups of 300 or fewer on Chroma Cloud
  4. Pass include without embeddings, since returned GiB are billed
  5. Don't pass ollama to chroma_create_collection. The description lists it but the server can't map it

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, Chroma API + MCP or Upstash Vector API + MCP?

Upstash Vector API + MCP scores 66.5 (B) on agent readiness against Chroma API + MCP's 50.1 (D), and leads in 6 of 7 scored categories. Chroma API + MCP leads on schema & documentation.

Do Chroma API + MCP and Upstash Vector API + MCP need an API key?

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

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

Yes. Chroma API + MCP has a hosted endpoint at https://api.trychroma.com/api/v2 and Upstash Vector API + MCP at https://api.upstash.com/v2.

Are Chroma API + MCP and Upstash Vector API + MCP open source?

Chroma API + MCP is open source (Apache-2.0). No open-source release is listed for Upstash Vector API + MCP.

Other comparisons with Chroma API + MCP 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.