Mantic.Sh logo

Mantic.Sh

Unclaimed

by marcoaapfortes

A structural code search engine for Al agents.

Install

$npx mantic.sh@latest "your search query"

Set up this server

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions
ai-agentclaudecode-searchcontext-retrievalcursordeveloper-toolsmcpmcp-serverragtypescript

More in Search & Web

Browse the full directory

Unclaimed listing

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

6 of 6 tools

Documented tools (6)

From project documentation. A server handshake does not verify each tool’s description or behavior.

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Mantic.Sh MCP Server

How do I connect Mantic.Sh MCP Server to Claude?
The listing records `npx mantic.sh@latest "your search query"` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Cursor, VS Code as compatible clients.
Is Mantic.Sh MCP Server free?
The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Mantic.Sh MCP Server do?
Mantic.Sh MCP Server documents 6 tools to the agent, including analyze_intent, find_references, get_context. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.