Head to head · Vector search · October 2026 research run

Upstash Vector API + MCP vs Weaviate API + MCP

Upstash Vector API + MCP scores 66.5 (B) on agent readiness against Weaviate API + MCP's 59.9 (C), and leads in 2 of 7 scored categories. Weaviate API + MCP leads on schema & documentation, agent ergonomics, security & auth and maintenance & community. Both do vector search.

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

Which one, for what

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 35

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Weaviate API + MCP loses 12 points for them

Watch for

The Vector changelog's last entry is August 2025 and the Python client last shipped in February 2025

Weaviate API + MCP C

Best for Hybrid keyword and vector retrieval with filters and multi-tenancy, self-hosted or managed, and for agents that work over MCP.

Ahead on

  • Schema & documentation, 84 against 49
  • Agent ergonomics, 95 against 80
  • Security & auth, 80 against 65
  • Maintenance & community, 90 against 56

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

No public status page or incident history

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.

Reliability Upstash Vector API + MCP +40

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.

Weaviate API + MCP 35

No public status page. status.weaviate.io still doesn't resolve, and status.weaviate.cloud (incident.io, titled "Weaviate Enterprise Status") shows a page-not-found body and an empty feed.atom on 1 November (0). No readable history (5). No request limits published for the database. The only numbers are on the AI services (Embeddings 2,000 requests a day and Query Agent 1,000 a month on Free) and a 60-second request timeout on Weaviate Cloud, now stated on the MCP page too (5 of 15). No 429 or backoff guidance found, but the import docs tell you to use deterministic UUIDs so a retried write can't duplicate objects, per the 1 October check (5 of 15). SLA of 99.5% on Flex and up to 99.95% on Premium (10). The database API is GA. The MCP docs page carries "Added in v1.38" with no preview label, though llms.txt still calls the MCP server a preview (10). 0+5+5+5+10+10 = 35.

Schema & documentation Weaviate API + MCP +35

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.

Weaviate API + MCP 84

Swagger 2.0 file at docs.weaviate.io/openapi.json covers REST only, and search and bulk import run over gRPC. All 4 MCP tools have typed JSON Schema inputs (22). llms.txt (10). MCP descriptions are one line each, such as "Performs hybrid search combining vector similarity and keyword matching (BM25).", with nothing on when to use or avoid a tool. Operators can override them in a config file (10). Typed inputs with required fields, an operator enum in the filter schema, alpha bounded 0 to 1 with a 0.75 default and limit defaulting to 100 (13). Code examples on most docs pages, and the MCP page now has an "Errors and limits" section giving the 401, 400, 503 and isError answers with their text. REST error responses are still documented unevenly (14). Semver releases and dated release notes (15). 22+10+10+13+14+15 = 84.

Maintenance & community Weaviate API + MCP +34

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.

Weaviate API + MCP 90

v1.40.3 tagged on 28 October 2026, with v1.39.14 and v1.38.23 on 27 October (30). Dozens of patch releases across three supported minors since 3 August, with v1.40.0 on 6 October after three release candidates from 15 September (20). Issue replies per the 1 October check, not re-read on 1 November because GitHub's pages refuse us: 456 open issues, the newest bug reports answered within weeks (15). Official clients in five languages, Python 4.24.1 on 26 October and TypeScript 3.15.2 on 27 October (15). CI on pull requests with a linter and a security lint workflow, per the 1 October check (10). 30+20+15+15+10 = 90.

Agent ergonomics Weaviate API + MCP +15

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.

Weaviate API + MCP 95

4 MCP tools (25). limit, return_properties, return_metadata, target_properties, filters and tenants on hybrid search, plus a cursor API for paging through a collection (20). The MCP page now documents each error an agent meets, with its code and text (401 with a JSON body for a bad key, 400 listing supported protocol versions, 503 when the server is off, isError results for permission failures, invalid arguments and disabled writes, and the 60-second cut-off). No catalogue for the REST API (15). Every tool sets readOnlyHint, destructiveHint and idempotentHint, and the write tool is hidden from tools/list until write access is enabled (20). Only query and collection_name are required. Official clients for Python, TypeScript, Go, Java and C# (15). 25+20+15+20+15 = 95.

Security & auth Weaviate API + MCP +15

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.

Weaviate API + MCP 80

Weaviate Cloud keys are created per cluster with an RBAC role (admin, viewer or custom), and can be rotated and deleted. Self-hosted instances add OIDC (30). Viewer roles, write tools off by default on self-hosted MCP and a read-only switch on Weaviate Cloud, though that switch is off by default (18). Search returns stored objects as written and the MCP docs give no prompt-injection guidance (5). With RBAC on, authorisation decisions and role changes are written to an audit log, with source IP, and the MCP server exports six Prometheus metrics. Not a full per-call log (10). SOC 2 Type II and HIPAA on the pricing page, a trust portal at trust.weaviate.io, a Vulnerability Disclosure Program report form, and advisories published on the Weaviate blog with severity, affected versions and fixes (7 November 2025, 1 and 15 October 2026). No bug bounty found, no SECURITY.md and no security.txt. novu takes 17 for the same record with ISO 27001 added, so 17 here at most (17). 30+18+5+10+17 = 80.

Score by category

CategoryWeightUpstash Vector API + MCPWeaviate API + MCPEdge
Reliability16%7535Upstash Vector API + MCP +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4984Weaviate API + MCP +35
Agent ergonomics13%8095Weaviate API + MCP +15
Security & auth14%6580Weaviate API + MCP +15
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5690Weaviate API + MCP +34
Transparency & trust7%7773Upstash Vector API + MCP +4
Negative events≤150-12
TotalB 66.5/100C 59.9/100

Facts side by side

FactUpstash Vector API + MCPWeaviate API + MCP
KindHTTP APIHTTP API
VendorUpstashWeaviate
Hosted endpointhttps://api.upstash.com/v2no (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
LicenceMITBSD-3-Clause (some parts under the Weaviate License)
Tools exposed744
Read-only variant documentedyesyes
llms.txtyesyes
MCP registryio.github.upstash/mcp-servernot listed
Last release2026-10-232026-10-28
Terms last updatednot read yet2026-05-01
Privacy policy last updatednot read yet2024-02-01
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetnot found in the text
Popularity70 stars, 187k npm/wk, 34k PyPI/wk17k stars, 406k npm/wk, 2.3M PyPI/wk
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Weaviate API + MCP higher, the other way from the total score.

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

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.

Weaviate API + MCP

Built-in MCP server with 4 typed tools, full annotations and documented error answers, and write tools hidden until enabled on self-hosted instances. Weaviate posts security advisories on its blog, three in the last year, but one released authentication fix in October carried none. No public status page or incident history.

Before you call either

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

Weaviate API + MCP

  1. Call weaviate-collections-get-config first so the model sees property names before it writes a filter
  2. Set return_properties on weaviate-query-hybrid, since every property comes back in full otherwise and limit defaults to 100
  3. Turn on Enable MCP Read-Only in Weaviate Cloud, or use a viewer key, before giving an agent the MCP endpoint
  4. Check collection names before an upsert, because auto-schema creates a new collection from a typo
  5. Move GraphQL queries to the clients or the REST Search API before 1 December 2026 on Weaviate Cloud

Questions

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

Upstash Vector API + MCP scores 66.5 (B) on agent readiness against Weaviate API + MCP's 59.9 (C), and leads in 2 of 7 scored categories. Weaviate API + MCP leads on schema & documentation, agent ergonomics, security & auth and maintenance & community.

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

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

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

Upstash Vector API + MCP has a hosted endpoint at https://api.upstash.com/v2. No hosted endpoint is listed for Weaviate API + MCP.

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

No open-source release is listed for Upstash Vector API + MCP. Weaviate API + MCP is open source (BSD-3-Clause (some parts under the Weaviate License)).

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