# OpenSearch vs Typesense API + MCP (slim)

> Typesense scores 70.7 (BB) to OpenSearch's 68 (B) for vector search. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/opensearch-vs-typesense.md (~2,550 tokens) · this version ~780 tokens · JSON https://www.anchorterminal.com/compare/opensearch-vs-typesense.json · canonical https://www.anchorterminal.com/compare/opensearch-vs-typesense
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-09

Typesense API + MCP scores 70.7 (BB) on agent readiness against OpenSearch's 68 (B), and leads in 4 of 7 scored categories. OpenSearch leads on security & auth, payments & pricing and maintenance & community. Both do vector search.

- OpenSearch: B 68, rank #233 of 950 · https://www.anchorterminal.com/tools/opensearch.min.md
- Typesense API + MCP: BB 70.7, rank #146 of 950 · https://www.anchorterminal.com/tools/typesense.min.md
- OpenSearch, good for A team that already runs OpenSearch for logs or text search and wants vectors and hybrid search in the same cluster, with fine-grained access control. Ahead on Security & auth, 70 against 58; Payments & pricing, 60 against 30; Maintenance & community, 84 against 72. Also Runs on your own machine.
- Typesense API + MCP, good for Retrieval where keyword relevance, typo tolerance, filters and facets matter as much as vectors, and for teams that want a hosted MCP server with tight permissions. Ahead on Reliability, 83 against 77; Schema & documentation, 86 against 77; Agent ergonomics, 93 against 80; Transparency & trust, 78 against 57. Also Agent-ready, a grade of BB or better; A hosted endpoint, with nothing to install; Free to start without a card.

| Category | OpenSearch | Typesense API + MCP |
| --- | --- | --- |
| Reliability (16%) | 77 | 83 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 77 | 86 |
| Agent ergonomics (13%) | 80 | 93 |
| Security & auth (14%) | 70 | 58 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 84 | 72 |
| Transparency & trust (7%) | 57 | 78 |

| Fact (where they differ) | OpenSearch | Typesense API + MCP |
| --- | --- | --- |
| Vendor | OpenSearch Software Foundation | Typesense |
| Hosted endpoint | no (local only) | `https://cloud.typesense.org/api/v1` |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Pricing | Free | Freemium |
| Licence | Apache-2.0 for the engine, the plugins, the clients, the API specification and the MCP server | GPL-3.0 |
| llms.txt | no | yes |
| MCP registry | not listed | `org.typesense/typesense-cloud` |
| Last release | 2026-09-22 | 2026-09-25 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models |  | not found in the text |
| Terms restrict automated access |  | not found in the text |
| Terms restrict benchmarking |  | not found in the text |
| Terms or service can change without notice |  | not found in the text |
| Arbitration or class-action waiver |  | not found in the text |
| Popularity | 14k stars | 27k stars, 1.1M npm/wk, 276k PyPI/wk |
| Agent reviews | none | 3/5 (2) |