Manticore Search
PYPI · MCP-MANTICORE · SCANNED SEP 20
MCP server for Manticore Search — lets AI assistants query and manage search databases.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 2 of 27 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 192 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 452 tokens (~90/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_query" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Manticore Search MCP server?
Manticore Search runs locally as a PyPI package, launched with uvx mcp-manticore. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-manticore
claude mcp add manticoresoftware-mcp-manticore -- uvx mcp-manticore
{
"mcpServers": {
"manticoresoftware-mcp-manticore": {
"command": "uvx",
"args": [
"mcp-manticore"
]
}
}
} {
"servers": {
"manticoresoftware-mcp-manticore": {
"command": "uvx",
"args": [
"mcp-manticore"
]
}
}
} codex mcp add manticoresoftware-mcp-manticore -- uvx mcp-manticore
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"manticoresoftware-mcp-manticore": {
"type": "local",
"command": [
"uvx",
"mcp-manticore"
],
"enabled": true
}
}
} openclaw mcp add manticoresoftware-mcp-manticore --command uvx --arg mcp-manticore
mcp_servers:
manticoresoftware-mcp-manticore:
command: "uvx"
args: ["mcp-manticore"] {
"McpServers": {
"manticoresoftware-mcp-manticore": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-manticore"
]
}
}
} assistant mcp add manticoresoftware-mcp-manticore -t stdio -c uvx -a mcp-manticore
{
"mcpServers": {
"manticoresoftware-mcp-manticore": {
"command": "uvx",
"args": [
"mcp-manticore"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/mcp-manticore@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 27 packages
| Packages resolved | 27 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe_table Describe Table ~38
Get the schema of a specific table/index in Manticore Search.
| Name | Type | Req | Description |
|---|---|---|---|
| table_name | string | yes | The name of the table/index to describe |
Structured output declared, but exposes no named fields.
No examples provided.
get_documentation Get Documentation ~104
Fetch documentation from Manticore Search manual. Use list_documentation() first to discover available files.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | Number of lines after match to include (default: 0) |
| before | integer | – | Number of lines before match to include (default: 0) |
| content | – | – | Optional search term to filter content (returns only matching sections) |
| file_path | string | yes | Path to documentation file (e.g., "Searching/KNN.md") |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_documentation List Documentation ~198
List available documentation files from Manticore Search manual. IMPORTANT: Make ONE call with regex OR patterns to find multiple topics at once. DO NOT make multiple calls - use pipe (|) to combine patterns. The file list is cached, so filtering is instant and local.
| Name | Type | Req | Description |
|---|---|---|---|
| search | – | – | Regex pattern to filter files (case-insensitive). Use OR patterns (|) to match multiple topics in ONE call: EFFICIENT (single call): - "knn|vector|embedding" - find all vector-related docs - "search… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_tables List Tables ~33
List available tables/indexes in Manticore Search. Returns: JSON string containing list of table names and their types
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
run_query Run Query ~79
Execute a SQL query against Manticore Search. Queries run in read-only mode by default. Set MANTICORE_ALLOW_WRITE_ACCESS=true to allow DDL and DML statements when your Manticore server permits them.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The SQL query to execute (e.g., "SELECT * FROM my_index LIMIT 10") |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Manticore Search MCP server?
Manticore Search is an MCP server listed in the public MCP registry as io.github.manticoresoftware/mcp-manticore. MCP server for Manticore Search, lets AI assistants query and manage search databases. This page covers its PyPI package (mcp-manticore).
Is the Manticore Search MCP server safe to use?
Manticore Search scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Manticore Search MCP server expose?
Manticore Search exposes 5 tools: run_query, list_tables, describe_table, list_documentation, get_documentation. Their descriptions and schemas cost roughly 452 tokens of context every time the server is loaded.
Is the Manticore Search MCP server still maintained?
Manticore Search is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.