{ "data": { "a": { "slug": "opensearch", "name": "OpenSearch", "vendor": "OpenSearch Software Foundation", "vendorUrl": "https://opensearch.org", "kind": "http-api", "category": "vector-search", "summary": "OpenSearch is an open-source search and analytics engine with vector, text and hybrid search, run by its owner. Agents reach it through a REST API, official clients, an OpenSearch MCP Server and an MCP endpoint inside the cluster.", "url": "https://www.anchorterminal.com/tools/opensearch", "markdownUrl": "https://www.anchorterminal.com/tools/opensearch.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/opensearch.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/opensearch.json", "repo": "https://github.com/opensearch-project/OpenSearch", "license": "Apache-2.0 for the engine, the plugins, the clients, the API specification and the MCP server", "transports": [ "http", "stdio" ], "packages": [ { "registry": "oci", "name": "opensearchproject/opensearch" }, { "registry": "pypi", "name": "opensearch-mcp-server-py" }, { "registry": "pypi", "name": "opensearch-py" } ], "auth": "mixed", "authNotes": "The owner sets access up on their own cluster. The Security plugin accepts basic auth, client certificates, JWT, OpenID Connect and SAML, and since 3.7 API keys sent as `Authorization: ApiKey \u003ctoken\u003e`. Only a security administrator can create, list or revoke a key. Each key names cluster permissions and index patterns with allowed actions, lasts 90 days at most, and cannot reach system indexes or the Security API. API keys are off until enabled in `config.yml`. The MCP server takes basic auth, AWS IAM, request headers or mTLS, or no authentication.", "pricing": "free", "pricingNotes": "Free software under Apache-2.0 with nothing to buy from the foundation, so an agent can start on a local Docker container with no account or contract. The owner pays for the machines. Three certified vendors sell long-term support, and opensearch.org lists no price for it (checked 2026-10-09).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the documentation source, the API specification or the MCP server source (checked 2026-10-09).", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": 13800, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.opensearch.org/latest/vector-search/", "openapi": "https://api-spec.opensearch.org/opensearch-openapi.yaml", "capabilities": [ "db.vector", "db.hybrid", "db.fulltext", "db.filters" ], "tags": [ "open-source", "self-hosted", "http-api", "mcp", "docker", "openapi", "api-key", "python", "javascript", "java", "go", "free" ], "lastRelease": "2026-09-22", "graded": true, "anchor": { "graded": true, "score": 68, "grade": "B", "agentReady": false, "rank": 233, "ranked": true, "rankOf": 950, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 84, "payments": 60, "reliability": 77, "schema": 77, "security": 70, "transparency": 57 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -5, "negativeNotes": [ "Until 0.12.0 (fix merged 3 August 2026, released 17 September 2026) the OpenSearch MCP Server attached its own configured credentials to any cluster URL a caller named in dynamic connection mode, which had shipped in 0.10.0 on 2 June 2026. The fix is described in the changelog and commit, and the repository lists no published advisory. Three points (https://github.com/opensearch-project/opensearch-mcp-server-py/blob/main/CHANGELOG.md).", "The Security plugin published four advisories on 30 April 2026, one moderate (GHSA-x83w-23jp-g6pw, document-level security not applied to documents linked by `has_child` or `has_parent`) and three low. Fixed and disclosed, so two points (https://github.com/opensearch-project/security/security/advisories)." ], "verdict": "OpenSearch 3.9.0 runs vector, text and hybrid search under Apache-2.0, with an OpenAPI 3.1 description of its REST API and API keys limited by permission and index pattern. The owner runs the cluster, no status page or SLA comes with the software, and no tool in the MCP server sets a read-only or destructive annotation.", "bestFor": "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.", "strengths": [ "Apache-2.0 for the engine, the plugins, the clients and the MCP server, under a foundation hosted by The Linux Foundation", "An OpenAPI 3.1 description of the REST API is published as one file, with about 717 operations in 36 namespace files in the source repository", "API keys since 3.7 carry cluster and index permissions, expire within 90 days at most, and are revoked on every node at once", "Approximate k-NN with filters applied during the search on the Lucene and Faiss engines, plus hybrid and neural sparse search", "Releases follow a published schedule about every eight weeks. 3.8.0 was tagged on 31 July and 3.9.0 on 22 September 2026" ], "weaknesses": [ "No hosted service from the foundation. The owner installs, secures and runs the cluster, and no status page or SLA exists for the software", "No `llms.txt` on docs.opensearch.org (HTTP 404), and doc pages carry about 160 KB of navigation text each", "The MCP server allows writes by default (`OPENSEARCH_SETTINGS_ALLOW_WRITE` is `true`) and no tool sets `readOnlyHint` or `destructiveHint`", "Before version 0.12.0 the MCP server sent its own configured credentials to any cluster URL a caller named. No advisory was published", "The core repository shows about 2,500 open issues, and 21 of the 25 newest carried the `untriaged` label on 9 October 2026" ], "agentNotes": [ "Create the index with `index.knn` set to true and a `knn_vector` field of the right dimension before indexing vectors", "Put the `filter` clause inside the `knn` query for filtering during the search. A filter outside it runs afterwards and can return fewer than `k` hits", "Ask a security administrator for an API key and send it as `Authorization: ApiKey \u003ctoken\u003e`. The token is shown once and lasts 90 days at most", "Use `size`, `_source` and `filter_path` to keep responses small, and `search_after` with a point in time for deep paging", "Set `OPENSEARCH_SETTINGS_ALLOW_WRITE=false` on the MCP server unless writes are needed. `GenericOpenSearchApiTool` can call any endpoint" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68 } ], "editorialScores": { "ergonomics": 80, "maintenance": 84, "payments": 60, "reliability": 77, "schema": 77, "security": 70, "transparency": 69 }, "provenanceScore": 45 }, "connect": { "install": "docker run -d -p 9200:9200 -p 9600:9600 -e \"discovery.type=single-node\" -e \"OPENSEARCH_INITIAL_ADMIN_PASSWORD=\u003ccustom-admin-password\u003e\" opensearchproject/opensearch:latest", "http": "curl https://localhost:9200 -ku admin:\"\u003ccustom-admin-password\u003e\"", "config": { "mcpServers": { "opensearch": { "args": [ "opensearch-mcp-server-py" ], "command": "uvx" } } } }, "letme": { "capability": "https://letme.dev/db.vector", "tool": "https://letme.dev/opensearch" }, "area": "developer", "provenance": { "legalEntity": "OpenSearch Software Foundation, a project of The Linux Foundation", "domain": "opensearch.org", "domainRegistered": "2003-05-15", "endpointOnVendorDomain": false, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://docs.opensearch.org/latest/version-history/", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The foundation page says the OpenSearch Software Foundation is a project of The Linux Foundation and is not involved in technical oversight of the open source project.", "No terms or privacy document is set. The site footer links The Linux Foundation's general terms and privacy policy, which are a parent body's website notices. The Apache-2.0 licence stands in for the software.", "The software runs on the owner's machines, so no endpoint is on the vendor's domain and there is no status page.", "https://opensearch.org/.well-known/security.txt answered 404 on 9 October 2026. `SECURITY.md` in the core repository asks for reports by email to security@opensearch.org.", "RDAP for opensearch.org gives a registration date of 2003-05-15 and a transfer on 13 November 2024.", "The first release date is the 1.0 general availability date in the maintenance table on the releases page." ], "score": 45 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/opensearch.json", "live": { "slug": "opensearch", "versions": [ { "registry": "github", "name": "opensearch-project/OpenSearch", "version": "3.9.0", "released": "2026-09-29", "seenAt": "2026-10-09T17:11:12.76716689Z" }, { "registry": "pypi", "name": "opensearch-mcp-server-py", "version": "0.12.0", "released": "2026-09-17", "seenAt": "2026-10-09T17:11:10.759906653Z" }, { "registry": "pypi", "name": "opensearch-py", "version": "3.2.0", "released": "2026-04-27", "seenAt": "2026-10-09T17:11:10.949518654Z" } ], "githubStars": 13832, "pypiWeekly": 75145, "pages": [ { "url": "https://docs.opensearch.org/latest/version-history/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:37:58.648544982Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9aa4527e824d" } ], "updatedAt": "2026-10-09T18:37:58.648544982Z" } }, "answer": "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 \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "typesense", "name": "Typesense API + MCP", "vendor": "Typesense", "vendorUrl": "https://typesense.org", "kind": "http-api", "category": "vector-search", "summary": "Open-source (GPL-3.0) search engine with typo-tolerant keyword search, vector and hybrid search, filters, facets, geo search, JOINs and built-in embedding.", "url": "https://www.anchorterminal.com/tools/typesense", "markdownUrl": "https://www.anchorterminal.com/tools/typesense.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/typesense.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/typesense.json", "repo": "https://github.com/typesense/typesense", "license": "GPL-3.0", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://cloud.typesense.org/api/v1", "packages": [ { "registry": "npm", "name": "typesense" }, { "registry": "pypi", "name": "typesense" } ], "auth": "mixed", "authNotes": "Cluster API uses the X-TYPESENSE-API-KEY header, with admin keys, keys scoped to collections and actions, and signed scoped search keys for per-user filters. Typesense Cloud Management API uses a capability-limited key. The hosted MCP server uses OAuth with a consent screen (Search only, Search and curate, Manage clusters, Build, Everything presets) or a Cluster Management API key as Bearer for cluster tools only.", "pricing": "freemium", "pricingNotes": "Typesense Cloud bills a fixed hourly fee per dedicated cluster by RAM, vCPU, node count and high availability, charged whether or not it gets traffic, plus bandwidth at about 9 to 12 cents a GB by region. No per-record or per-search charges. A free-tier cluster (0.5 GB RAM, 2 vCPU burst, one node) needs no payment method. Billed weekly by card, or prepaid credits. Self-hosted Typesense is free software plus your own infrastructure (https://cloud.typesense.org/pricing).", "priceSummary": "$0.09 / GB", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 support in docs, pricing or MCP docs (checked 2026-09-30).", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": 26615, "npmWeekly": 1096989, "pypiWeekly": 276494, "asOf": "2026-09-30" }, "docsUrl": "https://typesense.org/docs/", "llmsTxt": "https://typesense.org/docs/llms.txt", "openapi": "https://raw.githubusercontent.com/typesense/typesense-api-spec/master/openapi.yml", "registryName": "org.typesense/typesense-cloud", "capabilities": [ "db.vector", "db.hybrid", "db.fulltext", "db.filters" ], "tags": [ "hosted", "freemium", "no-card", "free-tier", "open-source", "self-hosted", "local", "mcp", "llms-txt", "typescript", "python" ], "lastRelease": "2026-09-25", "graded": true, "anchor": { "graded": true, "score": 70.7, "grade": "BB", "agentReady": true, "rank": 146, "ranked": true, "rankOf": 950, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 93, "maintenance": 72, "payments": 30, "reliability": 83, "schema": 86, "security": 58, "transparency": 78 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": -2, "negativeNotes": [ "GHSA-97x4-gm45-jpcw (moderate, search cache not isolated between scoped search keys) and GHSA-fpx5-8c99-247j (high, unauthenticated denial of service on /multi_search), both published 18 May 2026. The cache-keying fix landed on 20 March 2026 before v30.2. Fixed and disclosed, so a small deduction (https://github.com/typesense/typesense/security)." ], "verdict": "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.", "bestFor": "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.", "strengths": [ "Keyword, vector and hybrid search with filters, facets, sorting and geo in one request", "Hosted MCP server with OAuth consent presets, server-held data keys and destructive-tool annotations", "No status notices from July to October 2026 across 21 regions", "OpenAPI 3.0.3 spec with 79 operations, updated September 2026", "Free-tier cloud cluster without a payment method, and no per-request charges" ], "weaknesses": [ "Server v30.2 from April 2026 is still the newest stable release", "The authentication docs show the API key as a URL query parameter", "No SLA found, and SOC 2 reports need a paid support plan", "The MCP data tools need a browser sign-in, so a headless agent gets cluster tools only", "Cloud billing is per cluster-hour on dedicated hardware, so an idle cluster still costs money" ], "agentNotes": [ "Call `whoami` first on the MCP server to see which permissions the connection holds", "Put the embedding field in `query_by` alongside text fields for hybrid search", "Send the key in `X-TYPESENSE-API-KEY`, not in the URL, so it stays out of logs", "Use a scoped search key for retrieval-only agents; never pass the admin key", "Imports over 1,000 documents or 10 MB through MCP come back as a curl command to run locally" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 70.7 } ], "editorialScores": { "ergonomics": 93, "maintenance": 72, "payments": 30, "reliability": 83, "schema": 86, "security": 58, "transparency": 74 }, "provenanceScore": 82 }, "connect": { "http": "curl -G \"https://$TYPESENSE_HOST/collections/books/documents/search\" \\\n -H \"X-TYPESENSE-API-KEY: $TYPESENSE_API_KEY\" \\\n --data-urlencode \"q=harry potter\" --data-urlencode \"query_by=title\"", "claudeCode": "claude mcp add --transport http typesense-cloud https://cloud.typesense.org/mcp/v1", "config": { "mcpServers": { "typesense-cloud": { "url": "https://cloud.typesense.org/mcp/v1" } } } }, "letme": { "capability": "https://letme.dev/db.vector", "tool": "https://letme.dev/typesense" }, "area": "developer", "unitPrices": [ { "item": "Cloud bandwidth out", "unit": "gb", "usd": 0.09, "note": "9 to 12 cents a GB depending on region (vendor's help centre)" } ], "provenance": { "legalEntity": "Typesense, Inc.", "domain": "typesense.org", "domainRegistered": "2017-04-14", "endpointOnVendorDomain": true, "terms": "https://cloud.typesense.org/legal/terms", "privacy": "https://cloud.typesense.org/legal/privacy", "statusPage": "https://cloud-status.typesense.org", "changelog": "https://github.com/typesense/typesense/releases", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Cloud cluster hosts are on typesense.net, a separate domain from typesense.org." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/typesense.json", "live": { "slug": "typesense", "probe": { "target": "https://cloud.typesense.org/api/v1", "method": "get", "lastAt": "2026-10-10T01:38:11.635747502Z", "lastOk": true, "lastStatus": 404, "lastMs": 181, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 172, "p95ms24h": 436, "samples24h": 250, "samples30d": 2453, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://cloud-status.typesense.org", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:51:21.670597091Z" }, "versions": [ { "registry": "github", "name": "typesense/typesense", "version": "v30.2", "released": "2026-04-19", "seenAt": "2026-10-09T17:25:51.744599262Z" }, { "registry": "mcp-registry", "name": "org.typesense/typesense-cloud", "version": "1.0.1", "seenAt": "2026-10-09T02:57:46.004536428Z" }, { "registry": "npm", "name": "typesense", "version": "3.1.1", "seenAt": "2026-10-09T17:25:50.743850996Z" }, { "registry": "pypi", "name": "typesense", "version": "2.1.0", "released": "2026-10-07", "seenAt": "2026-10-09T17:25:51.562841612Z" } ], "githubStars": 26824, "npmWeekly": 956387, "pypiWeekly": 270796, "securityTxt": { "url": "https://typesense.org/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:39:30.33104674Z" }, "llmsTxt": { "url": "https://typesense.org/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:55.921593627Z" }, "domain": { "domain": "typesense.org", "registered": "2017-04-14", "source": "https://rdap.publicinterestregistry.org/rdap/domain/typesense.org", "checkedAt": "2026-10-04T13:03:37.438842208Z" }, "pages": [ { "url": "https://cloud.typesense.org/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:33:57.924643813Z", "changedAt": "2026-10-08T18:16:22.935485901Z", "fingerprint": "304c6858b0c6" }, { "url": "https://cloud.typesense.org/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:33:53.631738885Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b62a5db98492" }, { "url": "https://cloud.typesense.org/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:33:56.420397703Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6d32e9763424" } ], "updatedAt": "2026-10-10T01:38:11.635747502Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "OpenSearch Software Foundation", "b": "Typesense", "name": "Vendor" }, { "a": "no (local only)", "b": "https://cloud.typesense.org/api/v1", "name": "Hosted endpoint" }, { "a": "HTTP, stdio", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0 for the engine, the plugins, the clients, the API specification and the MCP server", "b": "GPL-3.0", "name": "Licence" }, { "a": "9", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "org.typesense/typesense-cloud", "name": "MCP registry" }, { "a": "2026-09-22", "b": "2026-09-25", "name": "Last release" }, { "a": "no document linked", "b": "no date given", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "14k stars", "b": "27k stars, 1.1M npm/wk, 276k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, OpenSearch or Typesense API + MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do OpenSearch and Typesense API + MCP need an API key?" }, { "answer": "OpenSearch runs on your own machine, with no hosted endpoint listed. Typesense API + MCP has a hosted endpoint at https://cloud.typesense.org/api/v1.", "question": "Can an agent call OpenSearch and Typesense API + MCP without installing anything?" }, { "answer": "Yes. OpenSearch is open source (Apache-2.0 for the engine, the plugins, the clients, the API specification and the MCP server). Typesense API + MCP is open source (GPL-3.0).", "question": "Are OpenSearch and Typesense API + MCP open source?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 70 against 58", "Payments \u0026 pricing, 60 against 30", "Maintenance \u0026 community, 84 against 72" ], "also": [ "Runs on your own machine" ], "goodFor": "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.", "slug": "opensearch", "watchFor": "No hosted service from the foundation. The owner installs, secures and runs the cluster, and no status page or SLA exists for the software" }, { "aheadOn": [ "Reliability, 83 against 77", "Schema \u0026 documentation, 86 against 77", "Agent ergonomics, 93 against 80", "Transparency \u0026 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" ], "goodFor": "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.", "slug": "typesense", "watchFor": "Server v30.2 from April 2026 is still the newest stable release" } ], "job": { "capability": "db.vector", "name": "Vector search" }, "others": [ { "json": "https://www.anchorterminal.com/compare/chroma-vs-opensearch.json", "title": "Chroma API + MCP vs OpenSearch", "url": "https://www.anchorterminal.com/compare/chroma-vs-opensearch" }, { "json": "https://www.anchorterminal.com/compare/chroma-vs-typesense.json", "title": "Chroma API + MCP vs Typesense API + MCP", "url": "https://www.anchorterminal.com/compare/chroma-vs-typesense" }, { "json": "https://www.anchorterminal.com/compare/elasticsearch-vs-opensearch.json", "title": "Elasticsearch vs OpenSearch", "url": "https://www.anchorterminal.com/compare/elasticsearch-vs-opensearch" }, { "json": "https://www.anchorterminal.com/compare/elasticsearch-vs-typesense.json", "title": "Elasticsearch vs Typesense API + MCP", "url": "https://www.anchorterminal.com/compare/elasticsearch-vs-typesense" }, { "json": "https://www.anchorterminal.com/compare/epsilla-vs-opensearch.json", "title": "Epsilla Vector Database vs OpenSearch", "url": "https://www.anchorterminal.com/compare/epsilla-vs-opensearch" }, { "json": "https://www.anchorterminal.com/compare/epsilla-vs-typesense.json", "title": "Epsilla Vector Database vs Typesense API + MCP", "url": "https://www.anchorterminal.com/compare/epsilla-vs-typesense" }, { "json": "https://www.anchorterminal.com/compare/lancedb-vs-opensearch.json", "title": "LanceDB vs OpenSearch", "url": "https://www.anchorterminal.com/compare/lancedb-vs-opensearch" }, { "json": "https://www.anchorterminal.com/compare/lancedb-vs-typesense.json", "title": "LanceDB vs Typesense API + MCP", "url": "https://www.anchorterminal.com/compare/lancedb-vs-typesense" }, { "json": "https://www.anchorterminal.com/compare/meilisearch-vs-opensearch.json", "title": "Meilisearch vs OpenSearch", "url": "https://www.anchorterminal.com/compare/meilisearch-vs-opensearch" }, { "json": "https://www.anchorterminal.com/compare/meilisearch-vs-typesense.json", "title": "Meilisearch vs Typesense API + MCP", "url": "https://www.anchorterminal.com/compare/meilisearch-vs-typesense" }, { "json": "https://www.anchorterminal.com/compare/milvus-zilliz-vs-opensearch.json", "title": "Milvus and Zilliz Cloud API + MCP vs OpenSearch", "url": "https://www.anchorterminal.com/compare/milvus-zilliz-vs-opensearch" }, { "json": "https://www.anchorterminal.com/compare/milvus-zilliz-vs-typesense.json", "title": "Milvus and Zilliz Cloud API + MCP vs Typesense API + MCP", "url": "https://www.anchorterminal.com/compare/milvus-zilliz-vs-typesense" }, { "json": "https://www.anchorterminal.com/compare/opensearch-vs-pinecone.json", "title": "OpenSearch vs Pinecone API + MCP", "url": "https://www.anchorterminal.com/compare/opensearch-vs-pinecone" }, { "json": "https://www.anchorterminal.com/compare/opensearch-vs-qdrant.json", "title": "OpenSearch vs Qdrant API + MCP", "url": "https://www.anchorterminal.com/compare/opensearch-vs-qdrant" }, { "json": "https://www.anchorterminal.com/compare/opensearch-vs-upstash-vector.json", "title": "OpenSearch vs Upstash Vector API + MCP", "url": "https://www.anchorterminal.com/compare/opensearch-vs-upstash-vector" }, { "json": "https://www.anchorterminal.com/compare/opensearch-vs-vespa.json", "title": "OpenSearch vs Vespa", "url": "https://www.anchorterminal.com/compare/opensearch-vs-vespa" }, { "json": "https://www.anchorterminal.com/compare/opensearch-vs-weaviate.json", "title": "OpenSearch vs Weaviate API + MCP", "url": "https://www.anchorterminal.com/compare/opensearch-vs-weaviate" }, { "json": "https://www.anchorterminal.com/compare/pinecone-vs-typesense.json", "title": "Pinecone API + MCP vs Typesense API + MCP", "url": "https://www.anchorterminal.com/compare/pinecone-vs-typesense" }, { "json": "https://www.anchorterminal.com/compare/qdrant-vs-typesense.json", "title": "Qdrant API + MCP vs Typesense API + MCP", "url": "https://www.anchorterminal.com/compare/qdrant-vs-typesense" }, { "json": "https://www.anchorterminal.com/compare/typesense-vs-upstash-vector.json", "title": "Typesense API + MCP vs Upstash Vector API + MCP", "url": "https://www.anchorterminal.com/compare/typesense-vs-upstash-vector" }, { "json": "https://www.anchorterminal.com/compare/typesense-vs-vespa.json", "title": "Typesense API + MCP vs Vespa", "url": "https://www.anchorterminal.com/compare/typesense-vs-vespa" }, { "json": "https://www.anchorterminal.com/compare/typesense-vs-weaviate.json", "title": "Typesense API + MCP vs Weaviate API + MCP", "url": "https://www.anchorterminal.com/compare/typesense-vs-weaviate" } ], "scores": [ { "by": 6, "edge": "typesense", "key": "reliability", "name": "Reliability", "opensearch": 77, "typesense": 83, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 9, "edge": "typesense", "key": "schema", "name": "Schema \u0026 documentation", "opensearch": 77, "typesense": 86, "weight": 13 }, { "by": 13, "edge": "typesense", "key": "ergonomics", "name": "Agent ergonomics", "opensearch": 80, "typesense": 93, "weight": 13 }, { "by": 12, "edge": "opensearch", "key": "security", "name": "Security \u0026 auth", "opensearch": 70, "typesense": 58, "weight": 14 }, { "by": 30, "edge": "opensearch", "key": "payments", "name": "Payments \u0026 pricing", "opensearch": 60, "typesense": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "opensearch", "key": "maintenance", "name": "Maintenance \u0026 community", "opensearch": 84, "typesense": 72, "weight": 7 }, { "by": 21, "edge": "typesense", "key": "transparency", "name": "Transparency \u0026 trust", "opensearch": 57, "typesense": 78, "weight": 7 } ], "summary": "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 \u0026 auth, payments \u0026 pricing and maintenance \u0026 community. Both do vector search.", "verdicts": { "opensearch": "OpenSearch 3.9.0 runs vector, text and hybrid search under Apache-2.0, with an OpenAPI 3.1 description of its REST API and API keys limited by permission and index pattern. The owner runs the cluster, no status page or SLA comes with the software, and no tool in the MCP server sets a read-only or destructive annotation.", "typesense": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/opensearch-vs-typesense", "json": "https://www.anchorterminal.com/compare/opensearch-vs-typesense.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/opensearch-vs-typesense.md", "slim": "https://www.anchorterminal.com/compare/opensearch-vs-typesense.min.md" }, "markdown": "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 \u0026 auth, payments \u0026 pricing and maintenance \u0026 community. Both do vector search.\n\n- OpenSearch: grade B, 68/100, rank #233 of 950. Markdown https://www.anchorterminal.com/tools/opensearch.md · JSON https://www.anchorterminal.com/api/v1/tools/opensearch.json\n- Typesense API + MCP: grade BB, 70.7/100, rank #146 of 950. Markdown https://www.anchorterminal.com/tools/typesense.md · JSON https://www.anchorterminal.com/api/v1/tools/typesense.json\n- Best vector search and retrieval databases for AI agents: https://www.anchorterminal.com/best/vector-search/index.md\n- All 85 retrieval comparisons: https://www.anchorterminal.com/compare/vector-search/index.md\n\n## Which one, for what\n\n### OpenSearch (B)\n\nGood 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.\n\nAhead on:\n- Security \u0026 auth, 70 against 58\n- Payments \u0026 pricing, 60 against 30\n- Maintenance \u0026 community, 84 against 72\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No hosted service from the foundation. The owner installs, secures and runs the cluster, and no status page or SLA exists for the software\n\n### Typesense API + MCP (BB)\n\nGood 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.\n\nAhead on:\n- Reliability, 83 against 77\n- Schema \u0026 documentation, 86 against 77\n- Agent ergonomics, 93 against 80\n- Transparency \u0026 trust, 78 against 57\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: Server v30.2 from April 2026 is still the newest stable release\n\n\n## Score by category\n\n| Category | Weight | OpenSearch | Typesense API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 77 | 83 | Typesense API + MCP +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 77 | 86 | Typesense API + MCP +9 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 93 | Typesense API + MCP +13 |\n| Security \u0026 auth | 14% (17.5 this run) | 70 | 58 | OpenSearch +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 30 | OpenSearch +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 84 | 72 | OpenSearch +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 57 | 78 | Typesense API + MCP +21 |\n| Negative events | ≤15 | -5 | -2 | |\n| **Total** | | **68 · B** | **70.7 · BB** | |\n\n## Facts side by side\n\n| Fact | OpenSearch | Typesense API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | OpenSearch Software Foundation | Typesense |\n| Hosted endpoint | no (local only) | `https://cloud.typesense.org/api/v1` |\n| Transports | HTTP, stdio | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | Apache-2.0 for the engine, the plugins, the clients, the API specification and the MCP server | GPL-3.0 |\n| Tools exposed | 9 | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `org.typesense/typesense-cloud` |\n| Last release | 2026-09-22 | 2026-09-25 |\n| Terms last updated | no document linked | no date given |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | not found in the text |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | not found in the text |\n| Popularity | 14k stars | 27k stars, 1.1M npm/wk, 276k PyPI/wk |\n| Agent reviews | none | 3/5 (2) |\n\n## Verdicts\n\n**OpenSearch.** OpenSearch 3.9.0 runs vector, text and hybrid search under Apache-2.0, with an OpenAPI 3.1 description of its REST API and API keys limited by permission and index pattern. The owner runs the cluster, no status page or SLA comes with the software, and no tool in the MCP server sets a read-only or destructive annotation.\n\n**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.\n\n## Before you call either\n\n### OpenSearch\n\n1. Create the index with `index.knn` set to true and a `knn_vector` field of the right dimension before indexing vectors\n2. Put the `filter` clause inside the `knn` query for filtering during the search. A filter outside it runs afterwards and can return fewer than `k` hits\n3. Ask a security administrator for an API key and send it as `Authorization: ApiKey \u003ctoken\u003e`. The token is shown once and lasts 90 days at most\n4. Use `size`, `_source` and `filter_path` to keep responses small, and `search_after` with a point in time for deep paging\n5. Set `OPENSEARCH_SETTINGS_ALLOW_WRITE=false` on the MCP server unless writes are needed. `GenericOpenSearchApiTool` can call any endpoint\n\n### Typesense API + MCP\n\n1. Call `whoami` first on the MCP server to see which permissions the connection holds\n2. Put the embedding field in `query_by` alongside text fields for hybrid search\n3. Send the key in `X-TYPESENSE-API-KEY`, not in the URL, so it stays out of logs\n4. Use a scoped search key for retrieval-only agents; never pass the admin key\n5. Imports over 1,000 documents or 10 MB through MCP come back as a curl command to run locally\n\n## Questions\n\n### Which is better for AI agents, OpenSearch or Typesense API + MCP?\n\nTypesense 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 \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do OpenSearch and Typesense API + MCP need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call OpenSearch and Typesense API + MCP without installing anything?\n\nOpenSearch runs on your own machine, with no hosted endpoint listed. Typesense API + MCP has a hosted endpoint at https://cloud.typesense.org/api/v1.\n\n### Are OpenSearch and Typesense API + MCP open source?\n\nYes. OpenSearch is open source (Apache-2.0 for the engine, the plugins, the clients, the API specification and the MCP server). Typesense API + MCP is open source (GPL-3.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/opensearch-vs-typesense.json, and with the fewest tokens: https://www.anchorterminal.com/compare/opensearch-vs-typesense.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"opensearch\", \"b\": \"typesense\"}`. From a terminal: `anchor compare opensearch typesense`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/opensearch.json and https://www.anchorterminal.com/api/v1/tools/typesense.json\n\n## Other comparisons with OpenSearch or Typesense API + MCP\n\n- [Chroma API + MCP vs OpenSearch](https://www.anchorterminal.com/compare/chroma-vs-opensearch.md)\n- [Chroma API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/chroma-vs-typesense.md)\n- [Elasticsearch vs OpenSearch](https://www.anchorterminal.com/compare/elasticsearch-vs-opensearch.md)\n- [Elasticsearch vs Typesense API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-typesense.md)\n- [Epsilla Vector Database vs OpenSearch](https://www.anchorterminal.com/compare/epsilla-vs-opensearch.md)\n- [Epsilla Vector Database vs Typesense API + MCP](https://www.anchorterminal.com/compare/epsilla-vs-typesense.md)\n- [LanceDB vs OpenSearch](https://www.anchorterminal.com/compare/lancedb-vs-opensearch.md)\n- [LanceDB vs Typesense API + MCP](https://www.anchorterminal.com/compare/lancedb-vs-typesense.md)\n- [Meilisearch vs OpenSearch](https://www.anchorterminal.com/compare/meilisearch-vs-opensearch.md)\n- [Meilisearch vs Typesense API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-typesense.md)\n- [Milvus and Zilliz Cloud API + MCP vs OpenSearch](https://www.anchorterminal.com/compare/milvus-zilliz-vs-opensearch.md)\n- [Milvus and Zilliz Cloud API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/milvus-zilliz-vs-typesense.md)\n- [OpenSearch vs Pinecone API + MCP](https://www.anchorterminal.com/compare/opensearch-vs-pinecone.md)\n- [OpenSearch vs Qdrant API + MCP](https://www.anchorterminal.com/compare/opensearch-vs-qdrant.md)\n- [OpenSearch vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/opensearch-vs-upstash-vector.md)\n- [OpenSearch vs Vespa](https://www.anchorterminal.com/compare/opensearch-vs-vespa.md)\n- [OpenSearch vs Weaviate API + MCP](https://www.anchorterminal.com/compare/opensearch-vs-weaviate.md)\n- [Pinecone API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/pinecone-vs-typesense.md)\n- [Qdrant API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/qdrant-vs-typesense.md)\n- [Typesense API + MCP vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/typesense-vs-upstash-vector.md)\n- [Typesense API + MCP vs Vespa](https://www.anchorterminal.com/compare/typesense-vs-vespa.md)\n- [Typesense API + MCP vs Weaviate API + MCP](https://www.anchorterminal.com/compare/typesense-vs-weaviate.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "OpenSearch vs Typesense API + MCP", "url": "" } ], "description": "Typesense scores 70.7 (BB) to OpenSearch's 68 (B) for vector search. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "OpenSearch B 68", "Typesense API + MCP BB 70.7", "scores" ], "h1": "OpenSearch vs Typesense API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-opensearch-vs-typesense.png", "path": "/compare/opensearch-vs-typesense", "published": "2026-10-01", "section": "tools", "title": "OpenSearch vs Typesense for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/opensearch-vs-typesense" }, "tokens": { "markdown": 2550, "slim": 780 }, "version": 1 }