Meeba Brain
by meeba-context-mcp-469248886325.us-central1.run.app in Developer tools
Repository knowledge graph MCP server for codebase understanding and debugging.
https://meeba-context-mcp-469248886325.us-central1.run.app/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 242 ms typical, 367 ms slowest 5%
- Last check
- 3 h ago
- Next check
- in 3 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"meeba-brain": {
"type": "http",
"url": "https://meeba-context-mcp-469248886325.us-central1.run.app/mcp"
}
}
}5 tools
- search_code
Hybrid semantic + keyword search over the connected repository's actual indexed content. Use this for open-ended questions ("where is rate limiting implemented?", "how are uploads validated?") where you don't already know an exact symbol or file name -- for those, use get_symbol_
- get_symbol_definition
Finds where a function, class, or method is actually defined in this repo -- exact file, line range, and signature-relevant metadata (async, decorators, docstring if present). Use this before assuming a symbol's location/signature from memory or from a similarly-named symbol in a
- get_callers
Every place in this repo that calls the given function or method -- a COMPLETE list from the parsed call graph, not a best-effort guess. Use this before renaming/changing a function's signature, or when you need to understand a function's blast radius before modifying it.
- get_callees
Every function/method the given function calls -- what it depends on to do its job. Use this to understand a function's behavior by seeing what it delegates to, before assuming what it does from its name alone.
- get_dependencies
What a specific file imports/depends on. Use this to understand a file's place in the codebase before assuming what's available to it, or before moving/refactoring it.
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 3 h ago | Passed | 200 | 213 ms |
| 12 h ago | Passed | 200 | 367 ms |
| 22 h ago | Passed | 200 | 242 ms |
| 31 h ago | Passed | 200 | 377 ms |