manticore-mcp-server

An MCP (Model Context Protocol) server that exposes Manticore Search capabilities to MCP-compatible clients, including search, document insert/update/delete, table/index inspection, and cluster status/management tools.

Evaluated Apr 04, 2026 (17d ago)

Repo ↗ Search mcp manticore search go database agent-tools integration

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

No auth/scopes are documented for the MCP server; destructive and cluster-management operations are exposed as tools, increasing blast radius if misused. TLS/auth to the Manticore endpoint is not documented (example uses http://localhost). No explicit guidance is provided on logging/secret handling, allowlisting tools, or auditing agent actions.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You run Manticore Search in a controlled environment and want agent tools for search and index management with predictable query/result limits.

Avoid When

You cannot restrict who can operate destructive tools (delete/update) or you lack observability for agent-driven actions.

Use Cases

• AI-assisted full-text search across Manticore indexes
• Index/table schema discovery for building search workflows
• Automating document ingestion and updates via an agent
• Operational visibility for cluster health/status monitoring
• Implementing agent-driven boolean/fuzzy search with highlighting

Not For

• Untrusted or internet-exposed deployments without network/auth controls
• Production cluster management via an LLM/agent without strict safeguards
• Regulated environments requiring strong documented compliance and audit controls

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

OAuth: No Scopes: No

No authentication/authorization mechanism is described for the MCP server; access appears to be gated only by where the server is deployed and the reachability of the underlying Manticore HTTP endpoint.

Pricing

Free tier: No

Requires CC: No

No pricing information provided (open-source MCP server).

Agent Metadata

Pagination

configurable result limits and pagination

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Agent may call destructive tools (delete/update) unless the MCP client or tooling is configured to prevent it.
⚠ Underlying Manticore HTTP endpoint is referenced as reachable at /search; failures/timeouts may need tuning via REQUEST_TIMEOUT.
⚠ Pagination/limits depend on MAX_RESULTS_PER_QUERY and tool parameters; agents may otherwise request many results and incur performance costs.
⚠ Cluster management tools are noted as 'use with caution in production', which is especially relevant for autonomous agents.

Alternatives

Use Manticore Search HTTP API directly with your own client/orchestration Build a custom wrapper service with auth, auditing, and strict allowlists over Manticore endpoints Use existing MCP servers (if available) for search platforms compatible with your stack

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for manticore-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.