Developer · Local MCP server
sqry - Semantic Code Search
AST-based semantic code search: 39 tools over 37 languages. Call tracing and impact analysis.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.verivus-oss/sqry- Version
- 32.0.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- Cargo (crates.io), OCI image (Docker)
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- verivus-oss (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/verivus-oss) · how
- Website
- github.com/verivus-oss/sqry
- Repository
- github.com/verivus-oss/sqry (folder sqry-mcp)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| Cargo (crates.io) | sqry-mcp | 32.0.1 | stdio |
| OCI image (Docker) | ghcr.io/verivus-oss/sqry-mcp:v32.0.1 | - | stdio |
How to connect sqry - Semantic Code Search
sqry - Semantic Code Search runs locally from a Rust crate published to crates.io: sqry-mcp version 32.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs the Rust toolchain; cargo install builds the program. It reads the environment variable SQRY_MCP_WORKSPACE_ROOT; set it in the client's configuration for this server.
sqry - Semantic Code Search runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/verivus-oss/sqry-mcp:v32.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm ghcr.io/verivus-oss/sqry-mcp:v32.0.1. Required arguments: --mount.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"sqry": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/verivus-oss/sqry-mcp:v32.0.1"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from verivus-oss (GitHub)
| Server | Runs |
|---|---|
| LLM CLI GatewayOne MCP endpoint for Claude Code, Codex, Gemini, Grok and Mistral CLIs, with durable async jobs. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| SqliteSQLite MCP - query databases, inspect schemas, explain queries, export data. | Local · stdio |
| SqlServer.RulesAnalyze T-SQL scripts for design, naming, and performance issues and prevent bad practices. | Local · stdio |
| SqlServerMcpMCP server for SQL Server: schema inspection, safe read-only queries, query plan analysis. | Local · stdio |
| SqlsureSemantic SQL inspector: catches double-counting, wrong joins, PII exposure before execution. | Local · stdio |
| sqry - Semantic Code SearchAST-based semantic code search: 33 tools, 35 languages, call tracing, impact analysis. | Local · stdio |
| SquigglesLet your coding agent see the squiggles - LSP diagnostics, navigation, refactoring, and extras. | Local · stdio |
| squirrelscanWebsite QA for your coding agent: audit SEO, performance, security, accessibility over MCP. | Remote · HTTPLive check: ✓ handshake |
| sqzPre-injection context compression for coding agents. Zero LLM calls, zero telemetry, offline-safe. | Local · stdio |