api.searchcode.com
https://api.searchcode.com/v1/mcp
active Production-safe Score 94/100 http no auth
At a glance
| Endpoint | https://api.searchcode.com/v1/mcp |
|---|---|
| Source | https://raw.githubusercontent.com/bd-dxg/my-pi/main/mcp.json |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-08-24 17:36:18 |
| Last checked | 2026-11-17 21:40:52 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 362 / 578 ms |
| Last successful check | 2026-11-17 21:40:52 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
code_analyze— Instant repo overview — languages, complexity, file count, tech stack, code quality findings, and secret scanning. Use as your first call tocode_search— Fast code search across any public git repo. Returns file paths, line numbers, and code snippets with context. Supports regex, boolean quericode_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: Wcode_file_tree— List files and directories in any public git repo. Supports fuzzy file search (query parameter), language/path filtering, and depth control.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 relatcode_get_findings— Get detailed code quality findings from a remote public git repository. Returns rule IDs, line numbers, severity, category, descriptions, ancode_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.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:40:52 | ✓ | ✓ | 433 ms | 91 | active |
| 2026-11-17 21:25:38 | ✓ | ✓ | 226 ms | 94 | active |
| 2026-11-17 21:10:30 | ✓ | ✓ | 250 ms | 94 | active |
| 2026-11-17 20:55:28 | ✓ | ✓ | 294 ms | 94 | active |
| 2026-11-17 20:40:24 | ✓ | ✓ | 233 ms | 94 | active |
| 2026-11-17 20:25:22 | ✓ | ✓ | 252 ms | 94 | active |
| 2026-11-17 20:10:08 | ✓ | ✓ | 448 ms | 91 | active |
| 2026-11-17 19:54:23 | ✓ | ✓ | 383 ms | 91 | active |
| 2026-11-17 19:39:18 | ✓ | ✓ | 385 ms | 91 | active |
| 2026-11-17 19:23:57 | ✓ | ✓ | 235 ms | 94 | active |
| 2026-11-17 19:08:48 | ✓ | ✓ | 259 ms | 94 | active |
| 2026-11-17 18:53:32 | ✓ | ✓ | 340 ms | 91 | active |
| 2026-11-17 18:38:31 | ✓ | ✓ | 388 ms | 91 | active |
| 2026-11-17 18:23:27 | ✓ | ✓ | 228 ms | 94 | active |
| 2026-11-17 18:08:08 | ✓ | ✓ | 426 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.searchcode.com/v1/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-searchcode-com-v1-mcp # JSON