Is the Searchcode MCP server down?

• Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "code_analyze",
  "description": "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 confidence grade. Prefer it over grepping for key prefixes with code_search — a pattern search only find",
  "inputSchema": {
    "type": "object",
    "required": [
      "repository"
    ],
    "properties": {
      "path": {
        "type": "string",
        "description": "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 question is about a specific component. Omit to analyze the entire repository."
      },
      "tests": {
        "enum": [
          "exclude",
          "include",
          "only"
        ],
        "type": "string",
        "default": "exclude",
        "description": "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, leaves them out of code_quality_summary and security_summary and counts them in tests_excluded; \"include\" adds them, each marked test: true; \"only\" returns just them. They are kept, not deleted: a credential committed in a test fixture is still a real credential, and include reaches it."
      },
      "language": {
        "type": "string",
        "description": "Filter results to a specific language (e.g. \"Java\", \"Go\", \"Python\")."
      },
      "repository": {
        "type": "string",
        "description": "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 demand. Wildcards and placeholders (\"*\", \"all\", \"global\", a bare host like \"github.com\") are rejected — if you do not have a specific repository URL, ask for one rather than guessing."
      },
      "detail_level": {
        "enum": [
          "summary",
          "full"
        ],
        "type": "string",
        "description": "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 for deep per-language audits or when you need granular per-file breakdowns within a specific language."
      },
      "scan_test_files": {
        "type": "boolean",
        "default": false,
        "description": "Older spelling of tests=\"include\", honoured when tests is not set. Prefer tests."
      },
      "include_all_dirs": {
        "type": "boolean",
        "default": false,
        "description": "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/vendored code."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

• Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "code_find_usages",
  "description": "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 only the first 150 lines of each file, so a file that imports the technology further down, or uses it w",
  "inputSchema": {
    "type": "object",
    "required": [
      "repository",
      "technology"
    ],
    "properties": {
      "offset": {
        "type": "integer",
        "default": 0,
        "description": "Skip this many files before returning. Use for paging."
      },
      "language": {
        "type": "string",
        "description": "Restrict results to files of this language (e.g. \"Python\", \"Go\")."
      },
      "repository": {
        "type": "string",
        "description": "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 demand. Wildcards and placeholders (\"*\", \"all\", \"global\", a bare host like \"github.com\") are rejected — if you do not have a specific repository URL, ask for one rather than guessing."
      },
      "technology": {
        "type": "string",
        "description": "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 first if you are unsure what is detected."
      },
      "max_results": {
        "type": "integer",
        "default": 50,
        "maximum": 500,
        "description": "Maximum number of files to return (cap: 500)."
      },
      "path_filter": {
        "type": "string",
        "description": "Restrict results to files whose path contains this substring (e.g. \"src/\", \"handlers\")."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

• Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "code_get_file",
  "description": "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, J",
  "inputSchema": {
    "type": "object",
    "required": [
      "repository",
      "path"
    ],
    "properties": {
      "path": {
        "type": "string",
        "description": "File path relative to repository root"
      },
      "end_line": {
        "type": "integer",
        "description": "Last line to return (inclusive). If omitted, returns to end of file. Cannot combine with symbol_name."
      },
      "max_lines": {
        "type": "integer",
        "default": 500,
        "maximum": 2000,
        "description": "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_name instead — it returns only the relevant declaration and avoids pulling unnecessary context."
      },
      "repository": {
        "type": "string",
        "description": "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 demand. Wildcards and placeholders (\"*\", \"all\", \"global\", a bare host like \"github.com\") are rejected — if you do not have a specific repository URL, ask for one rather than guessing."
      },
      "start_line": {
        "type": "integer",
        "default": 1,
        "description": "First line to return (1-based). Cannot combine with symbol_name."
      },
      "symbol_name": {
        "type": "string",
        "description": "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 fetching the entire file. Cannot combine with start_line/end_line. Response includes a symbols list for supported languages."
      },
      "include_adjacent_symbols": {
        "type": "boolean",
        "default": false,
        "description": "When true and symbol_name is set, includes structurally related declarations (nearby siblings) alongside the target symbol."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}