Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
searchcode is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http searchcode-mcp https://api.searchcode.com/v1/mcp
# 2 — ask your agent for something these tools do
# code_analyze, code_search, code_get_file and 4 more
searchcode costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SEAll 1 server
searchcode1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http searchcode-mcp https://api.searchcode.com/v1/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail_level | string | no | Controls response verbosity. summary returns top 20 across all languages; full returns top 20 per language. Use summary for portfolio reviews, hiring assessments, and high-level overviews. Use full fo |
| include_all_dirs | boolean | no | Include dependency/build/cache directories that are excluded by default (vendor, node_modules, third_party, target, build, dist, Pods, generated, etc.). Set to true if you need to analyze generated/ve |
| language | string | no | Filter results to a specific language (e.g. "Java", "Go", "Python"). |
| path | string | no | Subdirectory to scope analysis to (e.g. 'src', 'clang/lib'). Only files under this path are walked and analyzed — use this for large monorepos where full analysis is too slow or when the user's questi |
| repository | string | yes | Full git URL of ONE public remote repository, e.g. "https://github.com/redis/redis". Required. There is no cross-repository or global search: this API analyses one repository per call, cloning it on d |
| scan_test_files | boolean | no | Older spelling of tests="include", honoured when tests is not set. Prefer tests. |
| tests | string | no | Findings in TEST files (*_test.go, test/, tests/, spec/, __tests__/, testdata/, *.test.ts, *.spec.js, *Test.java, *Tests.cs, test_*.py, conftest.py, *_spec.rb and the like). "exclude", the default, le |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_sensitive | boolean | no | Whether to match case-sensitively. |
| code_filter | string | no | Structural filter to narrow matches to specific code regions. only-declarations and only-usages use heuristic patterns and support 30+ languages (Go, Python, JS/TS, Rust, Java, C/C++, C#, Ruby, PHP, K |
| context_lines | integer | no | Lines of context before and after each match. |
| include_all_dirs | boolean | no | Include dependency/build/cache directories that are excluded by default (vendor, node_modules, third_party, target, build, dist, Pods, generated, etc.). Set to true if you need to search generated/ven |
| max_matches_per_file | integer | no | Maximum matches to show per file (cap: 50). Keeps responses compact for files with many hits. The response includes matches_in_file (total) so you know if more exist. |
| max_results | integer | no | Maximum number of file results to return. Integer between 1 and 100 — values above 100 are rejected, not clamped. Paginate with offset for more. |
| offset | integer | no | Skip this many results before returning. Use for paging. |
| query | string | yes | Search query. Keywords are ANDed — use OR for exploratory multi-term searches (e.g. auth OR login OR session). Prefer single precise terms over multi-keyword phrases. Supports OR, NOT, "phrases", rege |
| repository | string | yes | Full git URL of ONE public remote repository, e.g. "https://github.com/redis/redis". Required. There is no cross-repository or global search: this API analyses one repository per call, cloning it on d |
| snippet_mode | string | no | auto (ranked relevance), grep (every matching line), or summary (1 best match per file, no context — very compact). Use auto when exploring or discovering where something is used across a codebase (e. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| end_line | integer | no | Last line to return (inclusive). If omitted, returns to end of file. Cannot combine with symbol_name. |
| include_adjacent_symbols | boolean | no | When true and symbol_name is set, includes structurally related declarations (nearby siblings) alongside the target symbol. |
| max_lines | integer | no | Lines to return (max: 2000). When reading an unfamiliar file for orientation, set this to 2000. When you already know which function or class you need (from search or findings results), prefer symbol_ |
| path | string | yes | File path relative to repository root |
| repository | string | yes | Full git URL of ONE public remote repository, e.g. "https://github.com/redis/redis". Required. There is no cross-repository or global search: this API analyses one repository per call, cloning it on d |
| start_line | integer | no | First line to return (1-based). Cannot combine with symbol_name. |
| symbol_name | string | no | PREFERRED for targeted retrieval. Name of a function/method/class to extract — returns only that declaration. Use this when search results or findings have pointed you to a specific symbol, instead of |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_all_dirs | boolean | no | Include dependency/build/cache directories that are excluded by default (vendor, node_modules, third_party, target, build, dist, Pods, generated, etc.). Set to true if you need to see generated/vendor |
| include_stats | boolean | no | If true, include line count and file size for each file. |
| language | string | no | Filter to only show files of this language (e.g. "Go", "Java"). |
| max_depth | integer | no | Maximum directory depth to return. If omitted, returns full tree. |
| max_results | integer | no | Max fuzzy matches to return. Integer between 1 and 100 — values above 100 are rejected, not clamped. Only used with query. |
| path_filter | string | no | Filter to restrict tree to matching paths. Supports both glob patterns (e.g. 'pkg/', 'src//*.go') and token-style filters (e.g. 'pkg/api .go'). Glob patterns are auto-converted to token filters. W |
| query | string | no | Fuzzy search query for finding files by approximate name. Returns ranked matches instead of tree. Examples: 'main.go', 'auth handler'. Can be combined with path_filter to search within a directory sub |
| repository | string | yes | Full git URL of ONE public remote repository, e.g. "https://github.com/redis/redis". Required. There is no cross-repository or global search: this API analyses one repository per call, cloning it on d |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_lines | integer | no | Per-file safety cap on lines returned (cap: 2000). |
| paths | array | yes | List of files to read. Each entry has a path and optional line range. |
| repository | string | yes | Full git URL of ONE public remote repository, e.g. "https://github.com/redis/redis". Required. There is no cross-repository or global search: this API analyses one repository per call, cloning it on d |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Filter findings by category. |
| kind | string | no | Partition the findings: "security" returns the security-category findings, "quality" returns every other category. The two are exhaustive and do not overlap, so kind is the way to ask for everything-b |
| max_results | integer | no | Maximum number of findings to return (cap: 200). |
| offset | integer | no | Skip this many findings before returning. Use for paging. |
| path | string | no | Filter findings to files matching this path prefix (e.g. "pkg/api/" or "src/main.go"). |
| repository | string | yes | Full git URL of ONE public remote repository, e.g. "https://github.com/redis/redis". Required. There is no cross-repository or global search: this API analyses one repository per call, cloning it on d |
| scan_test_files | boolean | no | Older spelling of tests="include", honoured when tests is not set. Prefer tests. |
| severity | string | no | Filter findings by severity level. |
| tests | string | no | Findings in TEST files (*_test.go, test/, tests/, spec/, __tests__/, testdata/, *.test.ts, *.spec.js, *Test.java, *Tests.cs, test_*.py, conftest.py, *_spec.rb and the like). "exclude", the default, le |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Restrict results to files of this language (e.g. "Python", "Go"). |
| max_results | integer | no | Maximum number of files to return (cap: 500). |
| offset | integer | no | Skip this many files before returning. Use for paging. |
| path_filter | string | no | Restrict results to files whose path contains this substring (e.g. "src/", "handlers"). |
| repository | string | yes | Full git URL of ONE public remote repository, e.g. "https://github.com/redis/redis". Required. There is no cross-repository or global search: this API analyses one repository per call, cloning it on d |
| technology | string | yes | Technology, library or framework to find. Matched against the names code_analyze reports in tech_stack, exactly first and then as a substring — so "boto3" finds "AWS SDK (Boto3)". Call code_analyze fi |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install searchcode or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish searchcode can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.