Searchcode MCP server

• Registry namecom.searchcode/mcpverified in the MCP registry

The registry name sits under searchcode.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-17
• Tools7
• Server calls itselfsearchcode
• Server version1.0.0
• Protocol version2025-03-26

On 2026-10-17 the server answered initialize and tools/list without a sign-in. First answer in 534 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer535 ms
• Space in an agent's context≈ 4,857 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 7 of 7

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• code_analyze

  Instant repo overview — languages, complexity, file count, tech stack, code quality findings, and secret scanning. Use as your first call to understand any remote public codebase. This is the tool that scans for LEAKED CREDENTIALS…

• code_search

  Fast code search across any public git repo. Returns file paths, line numbers, and code snippets with context. Supports regex, boolean queries, fuzzy matching, and structural filters (declarations, usages, strings, comments)…

• code_get_file

  Get code from a remote public git repository — either a specific function/class by name, a line range, or a full file. PREFERRED WORKFLOW: When search results or findings have already identified a specific function, method, or class, use…

• code_file_tree

  List files and directories in any public git repo. Supports fuzzy file search (query parameter), language/path filtering, and depth control. Combine query with path_filter to search within a directory subset. Use to explore project…

• code_get_files

  Get contents of multiple files from a remote public git repository in a single call. Reduces round-trips when you need to read several related files. Max 10 files per batch, 5000 total lines budget across all files. Each file supports…

• code_get_findings

  Get detailed code quality findings from a remote public git repository. Returns rule IDs, line numbers, severity, category, descriptions, and source snippets. Supports filtering by file path, severity (error, warning, info), category…

• code_find_usages

  Find which files in a repository use a given technology, library or framework — with the line number and the import keyword that proves it. Use after code_analyze reports a technology in tech_stack and you need to know which files it is…