# Typesense API + MCP vs Upstash Vector API + MCP

> Typesense API + MCP has a score of 70.9 (BB) against Upstash Vector API + MCP's 62.4 (B). Both do db vector. The largest gap is schema & documentation, 37 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/typesense-vs-upstash-vector
- Markdown: https://www.anchorterminal.com/compare/typesense-vs-upstash-vector.md (~1,650 tokens)
- Slim: https://www.anchorterminal.com/compare/typesense-vs-upstash-vector.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/typesense-vs-upstash-vector.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

Typesense API + MCP has a score of 70.9 (BB) against Upstash Vector API + MCP's 62.4 (B). Both do db vector. The largest gap is schema & documentation, 37 points.

- Typesense API + MCP: grade BB, 70.9/100, rank #93 of 452. Markdown https://www.anchorterminal.com/tools/typesense.md · JSON https://www.anchorterminal.com/api/v1/tools/typesense.json
- Upstash Vector API + MCP: grade B, 62.4/100, rank #218 of 452. Markdown https://www.anchorterminal.com/tools/upstash-vector.md · JSON https://www.anchorterminal.com/api/v1/tools/upstash-vector.json

## Which one, for what

Pick Typesense API + MCP for reliability (+8), schema & documentation (+37), agent ergonomics (+18), maintenance & community (+26).

Pick Upstash Vector API + MCP for security & auth (+5), payments & pricing (+10).

## Score by category

| Category | Weight | Typesense API + MCP | Upstash Vector API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 83 | 75 | Typesense API + MCP +8 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 49 | Typesense API + MCP +37 |
| Agent ergonomics | 13% (16.2 this run) | 93 | 75 | Typesense API + MCP +18 |
| Security & auth | 14% (17.5 this run) | 58 | 63 | Upstash Vector API + MCP +5 |
| Payments & pricing | 10% (12.5 this run) | 30 | 40 | Upstash Vector API + MCP +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 72 | 46 | Typesense API + MCP +26 |
| Transparency & trust | 7% (8.8 this run) | 80 | 82 | Upstash Vector API + MCP +2 |
| Negative events | ≤15 | -2 | 0 | |
| **Total** | | **70.9 · BB** | **62.4 · B** | |

## Facts side by side

| Fact | Typesense API + MCP | Upstash Vector API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Typesense | Upstash |
| Hosted endpoint | `https://cloud.typesense.org/api/v1` | `https://api.upstash.com/v2` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | GPL-3.0 | MIT |
| Tools exposed | 9 | 55 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | `org.typesense/typesense-cloud` | `io.github.upstash/mcp-server` |
| Last release | 2026-09-25 | 2026-08-24 |
| Popularity | 27k stars, 1.1M npm/wk, 276k PyPI/wk | 70 stars, 187k npm/wk, 34k PyPI/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |

## Verdicts

**Typesense API + MCP.** Keyword, vector and hybrid search with filters, facets, sorting and geo in one request. Server v30.2 from April 2026 is still the newest stable release.

**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

### Typesense API + MCP

1. Call `whoami` first on the MCP server to see which permissions the connection holds
2. Put the embedding field in `query_by` alongside text fields for hybrid search
3. Send the key in `X-TYPESENSE-API-KEY`, not in the URL, so it stays out of logs
4. Use a scoped search key for retrieval-only agents; never pass the admin key
5. Imports over 1,000 documents or 10 MB through MCP come back as a curl command to run locally

### 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

## Other comparisons with Typesense API + MCP or Upstash Vector API + MCP

- [Chroma API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/chroma-vs-typesense.md)
- [Chroma API + MCP vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/chroma-vs-upstash-vector.md)
- [Epsilla Vector Database vs Typesense API + MCP](https://www.anchorterminal.com/compare/epsilla-vs-typesense.md)
- [Epsilla Vector Database vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/epsilla-vs-upstash-vector.md)
- [LanceDB vs Typesense API + MCP](https://www.anchorterminal.com/compare/lancedb-vs-typesense.md)
- [LanceDB vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/lancedb-vs-upstash-vector.md)
- [Milvus and Zilliz Cloud API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/milvus-zilliz-vs-typesense.md)
- [Milvus and Zilliz Cloud API + MCP vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/milvus-zilliz-vs-upstash-vector.md)
- [Pinecone API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/pinecone-vs-typesense.md)
- [Pinecone API + MCP vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/pinecone-vs-upstash-vector.md)
- [Qdrant API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/qdrant-vs-typesense.md)
- [Qdrant API + MCP vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/qdrant-vs-upstash-vector.md)
- [Typesense API + MCP vs Weaviate API + MCP](https://www.anchorterminal.com/compare/typesense-vs-weaviate.md)
- [Upstash Vector API + MCP vs Weaviate API + MCP](https://www.anchorterminal.com/compare/upstash-vector-vs-weaviate.md)