mcp server
searchcode
Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.
Description as published by the maintainer. Source
- version 1.0.0
- slowing
- retrieval
slowing — Registry entry last updated 2026-03-05. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
code_analyze(path, language, repository, detail_level, scan_test_files, include_all_dirs)- Instant repo overview — languages, complexity, file count, tech stack, code quality findings, and credential scanning. Use as your first call to understand any remote public codebase. Supports language filtering and path scoping (for large monorepos, analyze a subdirectory instead of the full repo). When analysing multiple repositories, call in parallel rather than sequentially. Dependency/build directories excluded by default. Required: repository.
code_file_tree(query, language, max_depth, repository, max_results, path_filter, include_stats, include_all_dirs)- 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 layout, find files by name, or browse specific directories. Results capped at 1000 files; response includes total_files, files_shown, and truncated fields. Use language or path_filter to narrow large repos. Dependency/build directories excluded by default. Required: repository.
code_get_file(path, end_line, max_lines, repository, start_line, symbol_name, include_adjacent_symbols)- 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 symbol_name to extract just that declaration. This avoids fetching entire files and keeps context focused. Only fetch full files when you need a broad understanding of a file you haven't seen before. For supported languages (Go, Python, TypeScript, JavaScript, Java, C, C++, C#, Kotlin, Swift, Rust) the response includes a symbols list of declarations with line ranges. This is not a first-call tool — use code_analyze or code_search first to identify targets, then extract precisely what you need. Required: repository, path.
code_get_files(paths, max_lines, repository)- 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 optional line ranges. Failed files return per-file errors without blocking other files. Required: repository, paths.
code_get_findings(path, offset, category, severity, repository, max_results, scan_test_files)- 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), and category (security, deprecated, safety, correctness, maintainability, accessibility, modernization, performance, concurrency). Use after code_analyze to drill into specific findings. Shares the same analysis cache — no duplicate work if analyze already ran. Required: repository.
code_search(query, offset, repository, code_filter, max_results, snippet_mode, context_lines, case_sensitive, include_all_dirs, max_matches_per_file)- 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). Dependency/build directories excluded by default. Required: repository, query.
Last successful function declaration observed on . Source: https://api.searchcode.com/v1/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.searchcode.com/v1/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-05 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-03-05 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.searchcode.com | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | api.searchcode.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json