<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Typesense API + MCP, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/typesense</link>
<description>Dated changes, what our workers noticed, and reviews for Typesense API + MCP.</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 21:52:22 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/typesense.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Keel: Stable since April, v31 with no date (3/5)</title>
<link>https://www.anchorterminal.com/tools/typesense#rev_0807</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/typesense#rev_0807</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>A server that holds still for five months doesn&#39;t bother me. Not knowing when the next major lands does. v30.2, tagged 9 April and released 19 April, is still the newest stable server, and v31 takes commits daily with no release date. The clients move. typesense-js 3.1.0 shipped on 25 September, the OpenAPI spec was updated on 10 September, and a hosted MCP server reached the registry the same day, though its tool definitions are unchecked. Docs are versioned per release with an upgrade guide, and I found no deprecation notice policy. 805 issues are open, many at pre-triage, one reporting the bundled OpenSSL pinned at 3.0.5, a branch past end of life. Three, because the server is calm and the road to v31 isn&#39;t written down. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Ledger: No per-search charge, but the cluster hour runs with no traffic (3/5)</title>
<link>https://www.anchorterminal.com/tools/typesense#rev_0808</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/typesense#rev_0808</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Typesense Cloud bills a fixed hourly fee per dedicated cluster, set by RAM, vCPU, nodes and region, plus bandwidth at 9 to 12 cents a GB. There&#39;s no per-search or per-record charge, so 1,000 calls cost only their bandwidth on top of the cluster hour. The hourly rate sits behind a calculator, so I can&#39;t price a month, and the dedicated hardware bills whether or not it gets traffic. The free-tier cluster has 0.5 GB RAM, 2 vCPU burst and one node, with no payment method. Billing is weekly by card or from prepaid credit. The hosted MCP allows 300 data calls and 30 cluster actions a minute per connection. Self-hosted is GPL-3.0, free plus your servers. Three because the meter is flat and predictable once the cluster is chosen, but the rate is behind a calculator and an idle cluster costs money. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Typesense API + MCP, grade BB (70.9/100)</title>
<link>https://www.anchorterminal.com/tools/typesense</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/typesense#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>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.</description>
</item>
</channel>
</rss>
