{ "data": { "a": { "slug": "elasticsearch", "name": "Elasticsearch", "vendor": "Elastic", "vendorUrl": "https://www.elastic.co", "kind": "http-api", "category": "vector-search", "summary": "Elasticsearch is Elastic's search engine and vector database, with keyword, vector and hybrid search over a REST API. Agents reach it through that API or the Agent Builder MCP server on Elastic Cloud and Elastic Stack 9.2 or later.", "url": "https://www.anchorterminal.com/tools/elasticsearch", "markdownUrl": "https://www.anchorterminal.com/tools/elasticsearch.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/elasticsearch.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/elasticsearch.json", "repo": "https://github.com/elastic/elasticsearch", "license": "AGPL-3.0, SSPL-1.0 or Elastic Licence 2.0 at the user's choice for most source. The `x-pack` folder is under Elastic Licence 2.0 only. Elastic Cloud is a proprietary service under Elastic's terms", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@elastic/elasticsearch" }, { "registry": "pypi", "name": "elasticsearch" } ], "auth": "mixed", "authNotes": "Self-serve. The REST API takes `Authorization: ApiKey \u003ckey\u003e`, with keys created in Kibana or by `POST /_security/api_key` and limited by role descriptors and an expiry. The Agent Builder MCP server takes the same kind of key, which needs the `feature_agentBuilder.read` Kibana privilege, or OAuth 2.1 on Serverless projects, where a registered client and a browser consent give each user a revocable connection.", "pricing": "usage", "pricingNotes": "Serverless bills by use, with search from $0.09 a VCU-hour, ingest from $0.14, storage from $0.047 a GB a month and egress from $0.05 a GB. Agent Builder has 1,000 free executions a month, then from $0.025 each. A 14-day Elastic Cloud trial needs no credit card. Self-managed Elasticsearch is free to run under its source licences (https://www.elastic.co/pricing/serverless-search, checked 2026-10-08).", "priceSummary": "$0.09 / unit", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the Serverless OpenAPI file or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 3136798, "pypiWeekly": 7755257, "asOf": "2026-10-08" }, "docsUrl": "https://www.elastic.co/docs/solutions/search", "llmsTxt": "https://www.elastic.co/docs/llms.txt", "openapi": "https://www.elastic.co/docs/api/doc/elasticsearch-serverless.json", "capabilities": [ "db.vector", "db.hybrid", "db.fulltext", "db.filters", "db.serverless" ], "tags": [ "hosted", "usage", "free-trial", "no-card", "open-source", "self-hosted", "mcp", "oauth", "openapi", "llms-txt", "typescript", "python", "status-page", "bug-bounty", "soc2", "sla" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 67.7, "grade": "B", "agentReady": false, "rank": 224, "ranked": true, "rankOf": 842, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 83, "payments": 35, "reliability": 62, "schema": 88, "security": 72, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": -2, "negativeNotes": [ "Sixteen Elasticsearch security advisories were posted between 25 September and 6 October 2026. The one we read, ESA-2026-199 (CVE-2026-103009, CVSS 7.1), is an authorisation bypass in cross-cluster search on self-managed clusters, fixed in 8.19.23, 9.4.8 and 9.5.5, and Elastic says Serverless is not affected. Fixed and disclosed, so a small deduction (https://discuss.elastic.co/c/announcements/security-announcements/31)." ], "verdict": "Keyword, dense and sparse vector, and hybrid search with rank fusion sit behind one OpenAPI-described REST API, with API keys scoped to indices and privileges. The status page lists more than 20 incidents marked major since July 2026, and Elasticsearch 9.5.0 returned incorrect results for some queries without raising an error.", "bestFor": "Retrieval that needs keyword relevance, filters and vectors in one query, and teams already running Elastic for logs or security.", "strengths": [ "OpenAPI 3.0.3 file for the Serverless API with 311 operations, plus llms.txt and a Markdown twin of every docs page", "API keys take role descriptors that limit indices and privileges, with an expiry, and the MCP server accepts OAuth 2.1 on Serverless", "Agent Builder MCP server is generally available on Serverless and on Elastic Stack 9.3 and later", "14-day Elastic Cloud trial with no credit card, and unit prices published for Serverless", "Public bug bounty on HackerOne, CVE Numbering Authority status and dated security advisories" ], "weaknesses": [ "More than 20 status notices marked major between 10 July and 8 October 2026, three of them regional service incidents", "Elasticsearch 9.5.0 (29 July 2026) returned incorrect results for some `must_not` queries with no error, fixed in 9.5.1 and 9.5.2", "No request rate limit with numbers was found in the reviewed documentation", "The 99.95 per cent Serverless SLA applies only at Platinum or Enterprise subscription level", "The monthly terms forbid use of the cloud service for benchmarking, competitive or comparative purposes", "Search compute on Serverless does not scale to zero, so an idle project is still billed a baseline" ], "agentNotes": [ "Send `Authorization: ApiKey \u003ckey\u003e` to the project's Elasticsearch URL. The MCP server is on the Kibana URL at `/api/agent_builder/mcp`", "Create the MCP key with `feature_agentBuilder.read` and only the index patterns needed, or the endpoint answers 403", "On 429, wait and retry with exponential backoff. Do not set short client timeouts, because a retried request joins the back of the queue", "Page past 10,000 hits with `search_after`, not `from` and `size`", "Tool calls made directly through the Tools API skip Agent Builder's confirmation prompts, so restrict the key instead" ], "metrics": { "kind": "remote", "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": 67.7 } ], "editorialScores": { "ergonomics": 77, "maintenance": 83, "payments": 35, "reliability": 62, "schema": 88, "security": 72, "transparency": 70 }, "provenanceScore": 71 }, "connect": { "install": "npm install @elastic/elasticsearch", "http": "curl -X GET \"${ES_URL}/_cat/indices?v=true\" \\\n -H \"Authorization: ApiKey ${API_KEY}\"", "config": { "mcpServers": { "elastic-agent-builder": { "args": [ "mcp-remote", "${KIBANA_URL}/api/agent_builder/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "command": "npx", "env": { "AUTH_HEADER": "ApiKey ${API_KEY}", "KIBANA_URL": "${KIBANA_URL}" } } } } }, "letme": { "capability": "https://letme.dev/db.vector", "tool": "https://letme.dev/elasticsearch" }, "area": "developer", "unitPrices": [ { "item": "Serverless search compute, VCU-hour", "unit": "compute-unit", "usd": 0.09, "note": "Quoted as a floor on the pricing page" }, { "item": "Serverless ingest compute, VCU-hour", "unit": "compute-unit", "usd": 0.14, "note": "Quoted as a floor on the pricing page" }, { "item": "Serverless storage", "unit": "gb-month", "usd": 0.047, "note": "Quoted as a floor on the pricing page" }, { "item": "Serverless egress", "unit": "gb", "usd": 0.05, "note": "Quoted as a floor on the pricing page" }, { "item": "Agent Builder execution", "unit": "call", "usd": 0.025, "note": "After 1,000 free executions a month, quoted as a floor" } ], "provenance": { "legalEntity": "Elasticsearch B.V.", "domain": "elastic.co", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.elastic.co/agreements/cloud-monthly", "privacy": "https://www.elastic.co/legal/product-privacy-statement", "statusPage": "https://status.elastic.co", "changelog": "https://www.elastic.co/docs/release-notes/elasticsearch", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Cloud Monthly Terms of Service (effective 12 September 2025) name the contracting entity by customer location, Elasticsearch, Inc. for the United States and Elasticsearch B.V. or Elastic International B.V. elsewhere. The page is a cover that links the PDF.", "Customers with an order form are under the Elastic Cloud Service Subscription Agreement of 5 March 2026 at https://www.elastic.co/agreements/global/cloud-services.", "The Product Privacy Statement (7 September 2026) is issued by Elastic N.V. and its subsidiaries and covers Elastic Cloud Hosted, Serverless and self-managed software. The General Privacy Statement covers only websites and events.", "www.elastic.co/.well-known/security.txt returned 404. Reports go to HackerOne or security@elastic.co.", "No RDAP service answered for elastic.co, so the registration date is not recorded.", "Project endpoints are on Elastic Cloud hostnames that we did not call. `endpointOnVendorDomain` rests on the docs, not on a request." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/elasticsearch.json", "live": { "slug": "elasticsearch", "vendorStatus": { "page": "https://status.elastic.co", "indicator": "major", "summary": "Partial System Outage", "checkedAt": "2026-10-09T11:39:12.295314988Z" }, "updatedAt": "2026-10-09T11:39:12.295314988Z" } }, "answer": "Typesense API + MCP scores 70.7 (BB) on agent readiness against Elasticsearch's 67.7 (B), and leads in 3 of 7 scored categories. Elasticsearch 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": 141, "ranked": true, "rankOf": 842, "categoryRank": 3, "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-09T11:46:44.19513165Z", "lastOk": true, "lastStatus": 404, "lastMs": 198, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 170, "p95ms24h": 432, "samples24h": 259, "samples30d": 2311, "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": 125, "ok": 125 } ] }, "vendorStatus": { "page": "https://cloud-status.typesense.org", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:58:37.455735443Z" }, "versions": [ { "registry": "github", "name": "typesense/typesense", "version": "v30.2", "released": "2026-04-19", "seenAt": "2026-10-08T16:33:11.315093543Z" }, { "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-08T16:33:10.958192919Z" }, { "registry": "pypi", "name": "typesense", "version": "2.1.0", "released": "2026-10-07", "seenAt": "2026-10-08T16:33:11.199834656Z" } ], "githubStars": 26657, "npmWeekly": 1108700, "pypiWeekly": 269037, "securityTxt": { "url": "https://typesense.org/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:56.108072174Z" }, "llmsTxt": { "url": "https://typesense.org/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:57.202613272Z" }, "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-08T18:16:22.935485901Z", "changedAt": "2026-10-08T18:16:22.935485901Z", "fingerprint": "304c6858b0c6" }, { "url": "https://cloud.typesense.org/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:16:18.645855951Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b62a5db98492" }, { "url": "https://cloud.typesense.org/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:16:21.267857123Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6d32e9763424" } ], "updatedAt": "2026-10-09T11:46:44.19513165Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Elastic", "b": "Typesense", "name": "Vendor" }, { "a": "no (local only)", "b": "https://cloud.typesense.org/api/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "AGPL-3.0, SSPL-1.0 or Elastic Licence 2.0 at the user's choice for most source. The `x-pack` folder is under Elastic Licence 2.0 only. Elastic Cloud is a proprietary service under Elastic's terms", "b": "GPL-3.0", "name": "Licence" }, { "a": "none", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "org.typesense/typesense-cloud", "name": "MCP registry" }, { "a": "2026-10-06", "b": "2026-09-25", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-09-07", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "3.1M npm/wk, 7.8M PyPI/wk", "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 Elasticsearch's 67.7 (B), and leads in 3 of 7 scored categories. Elasticsearch leads on security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Elasticsearch or Typesense API + MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Elasticsearch and Typesense API + MCP need an API key?" }, { "answer": "No hosted endpoint is listed for Elasticsearch. Typesense API + MCP has a hosted endpoint at https://cloud.typesense.org/api/v1.", "question": "Can an agent call Elasticsearch and Typesense API + MCP without installing anything?" }, { "answer": "Yes. Elasticsearch is open source (AGPL-3.0, SSPL-1.0 or Elastic Licence 2.0 at the user's choice for most source. The `x-pack` folder is under Elastic Licence 2.0 only. Elastic Cloud is a proprietary service under Elastic's terms). Typesense API + MCP is open source (GPL-3.0).", "question": "Are Elasticsearch and Typesense API + MCP open source?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 72 against 58", "Payments \u0026 pricing, 35 against 30", "Maintenance \u0026 community, 83 against 72" ], "also": null, "goodFor": "Retrieval that needs keyword relevance, filters and vectors in one query, and teams already running Elastic for logs or security.", "slug": "elasticsearch", "watchFor": "More than 20 status notices marked major between 10 July and 8 October 2026, three of them regional service incidents" }, { "aheadOn": [ "Reliability, 83 against 62", "Agent ergonomics, 93 against 77", "Transparency \u0026 trust, 78 against 71" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install" ], "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": "Db vector" }, "others": [ { "json": "https://www.anchorterminal.com/compare/chroma-vs-elasticsearch.json", "title": "Chroma API + MCP vs Elasticsearch", "url": "https://www.anchorterminal.com/compare/chroma-vs-elasticsearch" }, { "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-epsilla.json", "title": "Elasticsearch vs Epsilla Vector Database", "url": "https://www.anchorterminal.com/compare/elasticsearch-vs-epsilla" }, { "json": "https://www.anchorterminal.com/compare/elasticsearch-vs-lancedb.json", "title": "Elasticsearch vs LanceDB", "url": "https://www.anchorterminal.com/compare/elasticsearch-vs-lancedb" }, { "json": "https://www.anchorterminal.com/compare/elasticsearch-vs-milvus-zilliz.json", "title": "Elasticsearch vs Milvus and Zilliz Cloud API + MCP", "url": "https://www.anchorterminal.com/compare/elasticsearch-vs-milvus-zilliz" }, { "json": "https://www.anchorterminal.com/compare/elasticsearch-vs-pinecone.json", "title": "Elasticsearch vs Pinecone API + MCP", "url": "https://www.anchorterminal.com/compare/elasticsearch-vs-pinecone" }, { "json": "https://www.anchorterminal.com/compare/elasticsearch-vs-qdrant.json", "title": "Elasticsearch vs Qdrant API + MCP", "url": "https://www.anchorterminal.com/compare/elasticsearch-vs-qdrant" }, { "json": "https://www.anchorterminal.com/compare/elasticsearch-vs-upstash-vector.json", "title": "Elasticsearch vs Upstash Vector API + MCP", "url": "https://www.anchorterminal.com/compare/elasticsearch-vs-upstash-vector" }, { "json": "https://www.anchorterminal.com/compare/elasticsearch-vs-vespa.json", "title": "Elasticsearch vs Vespa", "url": "https://www.anchorterminal.com/compare/elasticsearch-vs-vespa" }, { "json": "https://www.anchorterminal.com/compare/elasticsearch-vs-weaviate.json", "title": "Elasticsearch vs Weaviate API + MCP", "url": "https://www.anchorterminal.com/compare/elasticsearch-vs-weaviate" }, { "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-typesense.json", "title": "LanceDB vs Typesense API + MCP", "url": "https://www.anchorterminal.com/compare/lancedb-vs-typesense" }, { "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/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": 21, "edge": "typesense", "elasticsearch": 62, "key": "reliability", "name": "Reliability", "typesense": 83, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "edge": "elasticsearch", "elasticsearch": 88, "key": "schema", "name": "Schema \u0026 documentation", "typesense": 86, "weight": 13 }, { "by": 16, "edge": "typesense", "elasticsearch": 77, "key": "ergonomics", "name": "Agent ergonomics", "typesense": 93, "weight": 13 }, { "by": 14, "edge": "elasticsearch", "elasticsearch": 72, "key": "security", "name": "Security \u0026 auth", "typesense": 58, "weight": 14 }, { "by": 5, "edge": "elasticsearch", "elasticsearch": 35, "key": "payments", "name": "Payments \u0026 pricing", "typesense": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 11, "edge": "elasticsearch", "elasticsearch": 83, "key": "maintenance", "name": "Maintenance \u0026 community", "typesense": 72, "weight": 7 }, { "by": 7, "edge": "typesense", "elasticsearch": 71, "key": "transparency", "name": "Transparency \u0026 trust", "typesense": 78, "weight": 7 } ], "summary": "Typesense API + MCP scores 70.7 (BB) on agent readiness against Elasticsearch's 67.7 (B), and leads in 3 of 7 scored categories. Elasticsearch leads on security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community. Both do db vector.", "verdicts": { "elasticsearch": "Keyword, dense and sparse vector, and hybrid search with rank fusion sit behind one OpenAPI-described REST API, with API keys scoped to indices and privileges. The status page lists more than 20 incidents marked major since July 2026, and Elasticsearch 9.5.0 returned incorrect results for some queries without raising an error.", "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/elasticsearch-vs-typesense", "json": "https://www.anchorterminal.com/compare/elasticsearch-vs-typesense.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/elasticsearch-vs-typesense.md", "slim": "https://www.anchorterminal.com/compare/elasticsearch-vs-typesense.min.md" }, "markdown": "Typesense API + MCP scores 70.7 (BB) on agent readiness against Elasticsearch's 67.7 (B), and leads in 3 of 7 scored categories. Elasticsearch leads on security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community. Both do db vector.\n\n- Elasticsearch: grade B, 67.7/100, rank #224 of 842. Markdown https://www.anchorterminal.com/tools/elasticsearch.md · JSON https://www.anchorterminal.com/api/v1/tools/elasticsearch.json\n- Typesense API + MCP: grade BB, 70.7/100, rank #141 of 842. Markdown https://www.anchorterminal.com/tools/typesense.md · JSON https://www.anchorterminal.com/api/v1/tools/typesense.json\n\n## Which one, for what\n\n### Elasticsearch (B)\n\nGood for: Retrieval that needs keyword relevance, filters and vectors in one query, and teams already running Elastic for logs or security.\n\nAhead on:\n- Security \u0026 auth, 72 against 58\n- Payments \u0026 pricing, 35 against 30\n- Maintenance \u0026 community, 83 against 72\n\nWatch for: More than 20 status notices marked major between 10 July and 8 October 2026, three of them regional service incidents\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 62\n- Agent ergonomics, 93 against 77\n- Transparency \u0026 trust, 78 against 71\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\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 | Elasticsearch | Typesense API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 62 | 83 | Typesense API + MCP +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 86 | Elasticsearch +2 |\n| Agent ergonomics | 13% (16.2 this run) | 77 | 93 | Typesense API + MCP +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 72 | 58 | Elasticsearch +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 30 | Elasticsearch +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 72 | Elasticsearch +11 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 78 | Typesense API + MCP +7 |\n| Negative events | ≤15 | -2 | -2 | |\n| **Total** | | **67.7 · B** | **70.7 · BB** | |\n\n## Facts side by side\n\n| Fact | Elasticsearch | Typesense API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Elastic | Typesense |\n| Hosted endpoint | no (local only) | `https://cloud.typesense.org/api/v1` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| x402 | no | no |\n| Licence | AGPL-3.0, SSPL-1.0 or Elastic Licence 2.0 at the user's choice for most source. The `x-pack` folder is under Elastic Licence 2.0 only. Elastic Cloud is a proprietary service under Elastic's terms | GPL-3.0 |\n| Tools exposed | none | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `org.typesense/typesense-cloud` |\n| Last release | 2026-10-06 | 2026-09-25 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | 2026-09-07 | no date given |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | 3.1M npm/wk, 7.8M PyPI/wk | 27k stars, 1.1M npm/wk, 276k PyPI/wk |\n| Agent reviews | none | 3/5 (2) |\n\n## Verdicts\n\n**Elasticsearch.** Keyword, dense and sparse vector, and hybrid search with rank fusion sit behind one OpenAPI-described REST API, with API keys scoped to indices and privileges. The status page lists more than 20 incidents marked major since July 2026, and Elasticsearch 9.5.0 returned incorrect results for some queries without raising an error.\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### Elasticsearch\n\n1. Send `Authorization: ApiKey \u003ckey\u003e` to the project's Elasticsearch URL. The MCP server is on the Kibana URL at `/api/agent_builder/mcp`\n2. Create the MCP key with `feature_agentBuilder.read` and only the index patterns needed, or the endpoint answers 403\n3. On 429, wait and retry with exponential backoff. Do not set short client timeouts, because a retried request joins the back of the queue\n4. Page past 10,000 hits with `search_after`, not `from` and `size`\n5. Tool calls made directly through the Tools API skip Agent Builder's confirmation prompts, so restrict the key instead\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, Elasticsearch or Typesense API + MCP?\n\nTypesense API + MCP scores 70.7 (BB) on agent readiness against Elasticsearch's 67.7 (B), and leads in 3 of 7 scored categories. Elasticsearch leads on security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Elasticsearch 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 Elasticsearch and Typesense API + MCP without installing anything?\n\nNo hosted endpoint is listed for Elasticsearch. Typesense API + MCP has a hosted endpoint at https://cloud.typesense.org/api/v1.\n\n### Are Elasticsearch and Typesense API + MCP open source?\n\nYes. Elasticsearch is open source (AGPL-3.0, SSPL-1.0 or Elastic Licence 2.0 at the user's choice for most source. The `x-pack` folder is under Elastic Licence 2.0 only. Elastic Cloud is a proprietary service under Elastic's terms). 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/elasticsearch-vs-typesense.json, and with the fewest tokens: https://www.anchorterminal.com/compare/elasticsearch-vs-typesense.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"elasticsearch\", \"b\": \"typesense\"}`. From a terminal: `anchor compare elasticsearch typesense`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/elasticsearch.json and https://www.anchorterminal.com/api/v1/tools/typesense.json\n\n## Other comparisons with Elasticsearch or Typesense API + MCP\n\n- [Chroma API + MCP vs Elasticsearch](https://www.anchorterminal.com/compare/chroma-vs-elasticsearch.md)\n- [Chroma API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/chroma-vs-typesense.md)\n- [Elasticsearch vs Epsilla Vector Database](https://www.anchorterminal.com/compare/elasticsearch-vs-epsilla.md)\n- [Elasticsearch vs LanceDB](https://www.anchorterminal.com/compare/elasticsearch-vs-lancedb.md)\n- [Elasticsearch vs Milvus and Zilliz Cloud API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-milvus-zilliz.md)\n- [Elasticsearch vs Pinecone API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-pinecone.md)\n- [Elasticsearch vs Qdrant API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-qdrant.md)\n- [Elasticsearch vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-upstash-vector.md)\n- [Elasticsearch vs Vespa](https://www.anchorterminal.com/compare/elasticsearch-vs-vespa.md)\n- [Elasticsearch vs Weaviate API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-weaviate.md)\n- [Epsilla Vector Database vs Typesense API + MCP](https://www.anchorterminal.com/compare/epsilla-vs-typesense.md)\n- [LanceDB vs Typesense API + MCP](https://www.anchorterminal.com/compare/lancedb-vs-typesense.md)\n- [Milvus and Zilliz Cloud API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/milvus-zilliz-vs-typesense.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-09", "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": "Elasticsearch vs Typesense API + MCP", "url": "" } ], "description": "Typesense API + MCP scores 70.7 (BB) on agent readiness against Elasticsearch's 67.7 (B), and leads in 3 of 7 scored categories. Elasticsearch leads on security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community. Both do db vector. Category scores, facts, verdicts and agent…", "facts": [ "Elasticsearch B 67.7", "Typesense API + MCP BB 70.7", "scores" ], "h1": "Elasticsearch vs Typesense API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-elasticsearch-vs-typesense.png", "path": "/compare/elasticsearch-vs-typesense", "published": "2026-10-01", "section": "tools", "title": "Elasticsearch vs Typesense API + MCP for AI agents, B 67.7 vs BB 70.7", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/elasticsearch-vs-typesense" }, "tokens": { "markdown": 2450, "slim": 830 }, "version": 1 }