Is Manticore Search agent-ready?

Manticore Search scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is schema observability; its weakest is webhooks and events.

Does Manticore Search publish an OpenAPI spec?

Yes. Manticore Search publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.

What is Manticore Search's Headless Index score?

Manticore Search scores 66/100 on the Headless Index thesis-fit rubric and sits in Band B in the Search & Vector DBs category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Search & Vector DBs

Manticore Search

Headless Index

66/100

JAIRF

Spec invalid

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Manticore Search earns Band B in the Search & Vector DBs category of The Headless Index, with a thesis-fit score of 66/100. Its strongest dimension is schema observability (18/20); its weakest scored dimension is webhooks and events (6/20). Manticore Search publishes a machine-readable OpenAPI specification, which is what lets an agent discover and operate it without human glue code.

Editorial verdict

Manticore Search is solidly built for programmatic consumption. The Headless Index thesis-fit score of 66/100 lands it in the upper-middle of the index, and JAIRF returned malformed_spec for this vendor because the published OpenAPI did not parse cleanly under the open-source scorer. In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Manticore Search lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Manticore treats HTTP JSON as a first-class interface alongside SQL over the MySQL wire protocol (9306 for SQL, 9308 for HTTP JSON). An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Nothing here requires a browser. Configuration is a text file (manticore.conf), tables are created with CREATE TABLE, cluster replication is set up through SQL statements, and the official Docker images cover deployment. Manticore Cloud adds a console for provisioning and billing that has no matching API. There is no Terraform provider and no dedicated CLI beyond the mysql client.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: A server exists in the vendor org (github.com/manticoresoftware/mcp-manticore) and that counts for something, but it is four stars with no commit since April 2026 and no registry entry. Compared with the care visible in the client generation pipeline, the agent story looks unowned. Agents connecting to Manticore today are better served pointing a generic SQL tool at port 9306.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Manticore has no outbound event mechanism. The OpenAPI document defines eleven operations and not one of them registers a callback; there is no signing scheme, no retry policy and no event type list. Galera-based replication propagates writes between nodes, which is state synchronisation rather than notification. An agent that needs to know when indexing settles polls SHOW STATUS (or SHOW META following a query). Net assessment: Manticore Search can be operated by agents for the majority of practical workflows. The closest thing to a gap is webhooks and events^[3], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent16/20

scored

Manticore treats HTTP JSON as a first-class interface alongside SQL over the MySQL wire protocol (9306 for SQL, 9308 for HTTP JSON). The generated client family is unusually complete for a project this size: manticoresearch-php, -python, -go, -java, -net, -typescript and -rust, all regenerated together on 5 August 2026. That discipline matters more than star counts.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+OpenAPI specPublished, 11 operations
·GraphQL endpointDiscovered at https://manticoresearch.com/graphql, introspection disabled or scoped
·SDKs maintained1 (go); top by stars: manticoresoftware/go-sdk (58 stars)

cite (1)

github.sdks@2026-08-19

Headless operation16/20

scored

Nothing here requires a browser. Configuration is a text file (manticore.conf), tables are created with CREATE TABLE, cluster replication is set up through SQL statements, and the official Docker images cover deployment. Manticore Cloud adds a console for provisioning and billing that has no matching API. There is no Terraform provider and no dedicated CLI beyond the mysql client.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
·API operations exposed11 operations in OpenAPI spec
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-08-19

MCP & agent posture10/20

scored

A server exists in the vendor org (github.com/manticoresoftware/mcp-manticore) and that counts for something, but it is four stars with no commit since April 2026 and no registry entry. Compared with the care visible in the client generation pipeline, the agent story looks unowned. Agents connecting to Manticore today are better served pointing a generic SQL tool at port 9306.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/manticoresoftware/mcp-manticore (4 stars, last commit 139 days ago)
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability18/20

scored

The strongest showing in this batch. A complete OpenAPI 3.1 document is fetchable without auth (raw.githubusercontent.com/manticoresoftware/openapi/master/manticore.yml), covering /search, /bulk, /insert, /replace, /update, /delete, /sql and /autocomplete with named component schemas. An agent can generate a client cold from that file, which is exactly what the seven official SDKs do. SHOW TABLES and DESC add runtime introspection.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
+OpenAPIPublished at https://raw.githubusercontent.com/manticoresoftware/openapi/master/manticore.yml (OpenAPI 3.1.0, 11 operations)
·GraphQL introspectionGraphQL endpoint at https://manticoresearch.com/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events6/20

scored

Manticore has no outbound event mechanism. The OpenAPI document defines eleven operations and not one of them registers a callback; there is no signing scheme, no retry policy and no event type list. Galera-based replication propagates writes between nodes, which is state synchronisation rather than notification. An agent that needs to know when indexing settles polls SHOW STATUS (or SHOW META following a query).

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

ai_review_browser.pages_fetched@2026-08-19

JAIRF · 6 dimensions

JAIRF · Spec invalid

An OpenAPI specification was discovered but failed validation. The Jentic engine could not produce a JAIRF score.

cli-jentic exited 1 with no output: Error parsing spec: while scanning for the next token found character '\t' that cannot start any token in "<unicode string>", line 51, column 76: ... used for composite aggregation.

Band rationale:B band: JAIRF=N/A HeadlessIndex=66

04 / Embed

Show Manticore Search's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Calibration

How THI compares to external scorers

Source	Score	Measures	Last checked
Fern Agent Score	not found	Documentation completeness and SDK shape (~22 checks)	—
CLIRank Agent Friendliness	not found	CLI readiness, docs quality, and overall agent affordances	—
Cloudflare Is It Agent Ready?	blocked	Cloudflare's manual agent-readiness heuristic per vendor URL	—
Jentic Scorecard	—	JAIRF-based scorecard requiring a public OpenAPI specification	—

THI 66 vs external median 0

No external scores available to calibrate against.

Peers in Search & Vector DBs

Apache SolrB

Headless Index 66/100

QdrantB

Headless Index 66/100

MeilisearchB

Headless Index 66/100

See full Search & Vector DBs ranking →

FAQ

Manticore Search and agent readiness

Is Manticore Search agent-ready?: Manticore Search scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is schema observability; its weakest is webhooks and events.
Does Manticore Search publish an OpenAPI spec?: Yes. Manticore Search publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.
What is Manticore Search's Headless Index score?: Manticore Search scores 66/100 on the Headless Index thesis-fit rubric and sits in Band B in the Search & Vector DBs category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.