io.github.kahlilashanti/mantis-mcp
NPM · MANTIS-MCP · SCANNED SEP 21
Build proven high converting product showrooms and websites from your existing ecommerce catalog
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 48 of 137 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1006 tokens (~71/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 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
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; "publishStore" implies "publish" 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 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.kahlilashanti/mantis-mcp server?
io.github.kahlilashanti/mantis-mcp runs locally as an npm package, launched with npx -y mantis-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mantis-mcp
claude mcp add kahlilashanti-mantis-mcp -- npx -y mantis-mcp
{
"mcpServers": {
"kahlilashanti-mantis-mcp": {
"command": "npx",
"args": [
"-y",
"mantis-mcp"
]
}
}
} {
"servers": {
"kahlilashanti-mantis-mcp": {
"command": "npx",
"args": [
"-y",
"mantis-mcp"
]
}
}
} codex mcp add kahlilashanti-mantis-mcp -- npx -y mantis-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kahlilashanti-mantis-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"mantis-mcp"
],
"enabled": true
}
}
} openclaw mcp add kahlilashanti-mantis-mcp --command npx --arg -y --arg mantis-mcp
mcp_servers:
kahlilashanti-mantis-mcp:
command: "npx"
args: ["-y", "mantis-mcp"] {
"McpServers": {
"kahlilashanti-mantis-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mantis-mcp"
]
}
}
} assistant mcp add kahlilashanti-mantis-mcp -t stdio -c npx -a -y mantis-mcp
{
"mcpServers": {
"kahlilashanti-mantis-mcp": {
"command": "npx",
"args": [
"-y",
"mantis-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
- CVE-2026-82562 no longer affects this package ▲ security
- CVE-2026-82417 no longer affects this package ▲ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Analysed npm/mantis-mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 137 packages
| Packages resolved | 137 |
|---|---|
| Stale | 48 |
| 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 →
analyzeConsoleErrors ~43
Analyze console errors and suggest fixes
| Name | Type | Req | Description |
|---|---|---|---|
| browserInfo | object | – | Browser information (userAgent, etc.) |
| errors | array | yes | Console error messages to analyze |
No output schema declared.
No examples provided.
analyzeEventFlow ~44
Analyze event flow and user behavior
| Name | Type | Req | Description |
|---|---|---|---|
| sessionData | object | – | Session data to analyze (optional) |
| timeRange | object | – | Time range for analysis (optional) |
No output schema declared.
No examples provided.
checkBrowserCompatibility ~40
Check browser compatibility issues
| Name | Type | Req | Description |
|---|---|---|---|
| features | array | yes | Features to check compatibility for |
| userAgent | string | – | Browser user agent string (optional) |
No output schema declared.
No examples provided.
createMantisIntegration ~90
Generate Mantis integration code for your framework
| Name | Type | Req | Description |
|---|---|---|---|
| features | array | yes | Features to include: cart, camera, variants, analytics |
| framework | string | yes | Target framework (react, vue, next, shopify, etc.) |
| responseMode | string | – | Override response format (execute for IDE, instructions for chat) |
| storeType | string | – | Type of store for optimized experience |
No output schema declared.
No examples provided.
createStore ~165
Create a 3D commerce showroom that converts better than traditional e-commerce. Use this after importing products to build a store that drives sales. Shopify checkout integrates automatically when shopifyStore is provided. For other e-commerce platforms, the agent can help configure checkout connections.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Store configuration (optional) |
| description | string | – | Store description (optional) |
| name | string | yes | Store/showroom name |
| organizationId | string | – | Organization ID (optional) |
| products | array | – | Products to add to store |
| shopifyStore | string | – | Shopify store domain for automatic checkout integration (e.g., "your-store.myshopify.com"). When provided, products in the 3D showroom will link directly to your Shopify store for checkout. |
No output schema declared.
No examples provided.
debugPostMessage ~59
Debug postMessage communication issues
| Name | Type | Req | Description |
|---|---|---|---|
| captureTime | number | – | Seconds to capture messages (default: 10) |
| filterOrigin | string | – | Filter messages from specific origin (optional) |
| url | string | – | URL to debug (optional) |
No output schema declared.
No examples provided.
generateEventHandler ~62
Generate event handler code for Mantis SDK events
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform when event fires |
| event | string | yes | Event type (cart-opened, model-click, etc.) |
| framework | string | yes | Target framework for code generation |
No output schema declared.
No examples provided.
getPerformanceMetrics ~66
Get performance metrics for 3D experience
| Name | Type | Req | Description |
|---|---|---|---|
| duration | number | – | Duration to monitor in seconds (default: 60) |
| metrics | array | yes | Metrics to collect: fps, load-time, memory, gpu |
| url | string | – | URL to analyze (optional) |
No output schema declared.
No examples provided.
importCatalog ~136
Import product catalog from Shopify, CSV, or manual input to build a high-converting 3D commerce store. Use this when a merchant wants to create or improve an e-commerce store.
| Name | Type | Req | Description |
|---|---|---|---|
| csvData | string | – | CSV data with columns: name,description,imageURL,price,sku (for CSV import) |
| products | array | – | Product array (for manual import) |
| shopifyAccessToken | string | – | Shopify API access token (for Shopify import) |
| shopifyStore | string | – | Shopify store domain (for Shopify import) |
| source | string | yes | Import source: shopify, csv, or manual |
No output schema declared.
No examples provided.
installMantisSDK ~62
Install and configure Mantis SDK with proper .npmrc setup
| Name | Type | Req | Description |
|---|---|---|---|
| authToken | string | – | Authentication token for private registry (optional) |
| framework | string | yes | Target framework for integration |
| projectPath | string | – | Project directory path (optional) |
No output schema declared.
No examples provided.
publishStore ~70
Publish the 3D showroom live so customers can start shopping and converting. Final step to launch a high-converting store.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Custom domain (optional) |
| showroomAlias | string | – | Showroom alias to publish |
| showroomId | string | – | Showroom ID to publish |
No output schema declared.
No examples provided.
simulateUserFlow ~53
Simulate user interactions with Mantis experience
| Name | Type | Req | Description |
|---|---|---|---|
| flow | array | yes | Flow steps: load-experience, click-model, open-cart, add-item |
| timing | object | – | Delays between actions (optional) |
No output schema declared.
No examples provided.
testMantisEvent ~55
Test Mantis SDK events and responses
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Event data payload (optional) |
| event | string | yes | Event type to test |
| expectedResponse | object | – | Expected response for validation (optional) |
No output schema declared.
No examples provided.
validateSetup ~61
Validate Mantis SDK installation and configuration
| Name | Type | Req | Description |
|---|---|---|---|
| checkAuth | boolean | – | Check authentication setup (default: true) |
| checkOrigins | boolean | – | Check allowed origins configuration (default: true) |
| projectPath | string | – | Project directory to validate (optional) |
No output schema declared.
No examples provided.
What is the io.github.kahlilashanti/mantis-mcp server?
io.github.kahlilashanti/mantis-mcp is listed in the public MCP registry as io.github.kahlilashanti/mantis-mcp. Build proven high converting product showrooms and websites from your existing ecommerce catalog. This page covers its npm package (mantis-mcp).
Is the io.github.kahlilashanti/mantis-mcp server safe to use?
io.github.kahlilashanti/mantis-mcp scores 68 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.kahlilashanti/mantis-mcp server expose?
io.github.kahlilashanti/mantis-mcp exposes 14 tools: installMantisSDK, validateSetup, createMantisIntegration, generateEventHandler, debugPostMessage, and 9 more. Their descriptions and schemas cost roughly 1,006 tokens of context every time the server is loaded.
Is the io.github.kahlilashanti/mantis-mcp server still maintained?
io.github.kahlilashanti/mantis-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.kahlilashanti/mantis-mcp server under?
io.github.kahlilashanti/mantis-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.