Manticore Search

Created By
manticoresoftware3 months ago
MCP server for Manticore Search — enables AI assistants to query and manage Manticore Search databases directly. Supports full-text search, KNN vector search, fuzzy search, and real-time data access.
Overview

Manticore Search MCP Server

Enable AI assistants to query and manage Manticore Search databases directly through the Model Context Protocol (MCP).

Features

  • SQL Query Execution - Run SELECT, SHOW, DESCRIBE queries
  • Full-Text Search - Leverage Manticore's powerful full-text search capabilities
  • KNN Vector Search - Perform vector similarity searches
  • Fuzzy Search - Handle typos and approximate matches
  • Real-time Data Access - Live database queries from AI assistants
  • Documentation Access - Built-in Manticore documentation fetcher

Installation

# Install with uvx (recommended)
uvx mcp-manticore

# Or with pip
pip install mcp-manticore

Configuration

Add to your MCP client configuration:

{
  "mcpServers": {
    "manticore": {
      "command": "uvx",
      "args": ["mcp-manticore"],
      "env": {
        "MANTICORE_HOST": "localhost",
        "MANTICORE_PORT": "9308"
      }
    }
  }
}

Environment Variables

VariableDefaultDescription
MANTICORE_HOSTlocalhostManticore server host
MANTICORE_PORT9308HTTP API port
MANTICORE_USER-Username (optional)
MANTICORE_PASSWORD-Password (optional)
MANTICORE_ALLOW_WRITE_ACCESSfalseEnable write operations
MANTICORE_ALLOW_DROPfalseEnable destructive operations
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
manticoresoftware
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago