mantis-mcp

MCPcommunity
v1.1.0io.github.kahlilashantiMITUpdated 1mo agonpmGitHub

Build proven high converting product showrooms and websites from your existing ecommerce catalog

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Reads these credentials
  • MANTIS_AUTH_TOKENAPI keyoptional

    Bearer token for authenticated Mantis API requests

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.kahlilashanti
LicenseMIT
Version1.1.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies60 resolved · 1 with advisories
Tool surface14 tools · none privileged
Security scan⚠ Warnings (1)v1.1.0 · 3d agoHow well does this scan work?
EvalsNone
IndexedSep 1, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

14 tools · none privileged
Statically extracted from the published packagev1.1.0 · 3d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

installMantisSDKInstall and configure Mantis SDK with proper .npmrc setup

Install and configure Mantis SDK with proper .npmrc setup

No input schema was published for this tool.

validateSetupValidate Mantis SDK installation and configuration

Validate Mantis SDK installation and configuration

No input schema was published for this tool.

createMantisIntegrationGenerate Mantis integration code for your framework

Generate Mantis integration code for your framework

No input schema was published for this tool.

generateEventHandlerGenerate event handler code for Mantis SDK events

Generate event handler code for Mantis SDK events

No input schema was published for this tool.

debugPostMessageDebug postMessage communication issues

Debug postMessage communication issues

No input schema was published for this tool.

analyzeConsoleErrorsAnalyze console errors and suggest fixes

Analyze console errors and suggest fixes

No input schema was published for this tool.

checkBrowserCompatibilityCheck browser compatibility issues

Check browser compatibility issues

No input schema was published for this tool.

testMantisEventTest Mantis SDK events and responses

Test Mantis SDK events and responses

No input schema was published for this tool.

simulateUserFlowSimulate user interactions with Mantis experience

Simulate user interactions with Mantis experience

No input schema was published for this tool.

getPerformanceMetricsGet performance metrics for 3D experience

Get performance metrics for 3D experience

No input schema was published for this tool.

analyzeEventFlowAnalyze event flow and user behavior

Analyze event flow and user behavior

No input schema was published for this tool.

importCatalogImport 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.

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.

No input schema was published for this tool.

createStoreCreate 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 connec…

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 connec…

No input schema was published for this tool.

publishStorePublish the 3D showroom live so customers can start shopping and converting. Final step to launch a high-converting store.

Publish the 3D showroom live so customers can start shopping and converting. Final step to launch a high-converting store.

No input schema was published for this tool.

14 of 14 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Build proven high converting product showrooms and websites from your existing ecommerce catalog

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-01 — observed resolution, not a publisher declaration.

60 packages resolved · 8 direct · 1 carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

82 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+70 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.