searchcode
Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.
| Endpoint | https://api.searchcode.com/v1/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 7 tools · grade D (61) · pin ts_8f4cc562f078f2fbd6065108b65de025 · protocol 2025-03-26 |
| First / last listed | 2026-11-07 02:33 UTC / 2026-11-07 02:33 UTC |
| Grade over time | 2026-11-07: D (61), 7 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: code_analyze code_search code_get_file code_file_tree code_get_files code_get_findings code_find_usages
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: security_summary is a dedicated secret and credential scanner covering API keys, access tokens, private keys and connection strings, each with a file, a line and a conf params: detail_level, include_all_dirs, language, path, repository*, scan_test_files, tests |
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). Dependency/build directories excluded by default. Searching for leaked secrets? Call code_analyze instead and read security_summary — it runs a real secret and credential sca params: case_sensitive, code_filter, context_lines, include_all_dirs, max_matches_per_file, max_results, offset, query*, repository*, snippet_mode |
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 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 understandi params: end_line, include_adjacent_symbols, max_lines, path*, repository*, start_line, symbol_name |
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 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 params: include_all_dirs, include_stats, language, max_depth, max_results, path_filter, query, repository* |
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 optional line ranges. Failed files return per-file errors without blocking other files. params: max_lines, paths*, repository* |
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 (security, deprecated, safety, correctness, maintainability, accessibility, modernization, performance, concurrency), and kind (security, quality) — kind=security is params: category, kind, max_results, offset, path, repository*, scan_test_files, severity, tests |
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 actually in, rather than searching for import statements by hand. Returns file, line, evidence keyword and language. COVERAGE LIMIT: technology detection reads onl params: language, max_results, offset, path_filter, repository*, technology* |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.