# Meeba Brain

> Repository knowledge graph MCP server for codebase understanding and debugging.

- name: io.github.meemoprasad/meeba-brain
- version: 1.0.1
- connection class: R0 (autonomous)
- trust: 91/100
- quality: 85/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.meemoprasad%2Fmeeba-brain
- tools: https://api.protogrid.dev/v1/servers/io.github.meemoprasad%2Fmeeba-brain/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "meeba-brain": {
      "type": "http",
      "url": "https://meeba-context-mcp-469248886325.us-central1.run.app/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 85
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-100% ~updated-41d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_callees (destructiveHint); search_code (destructiveHint); get_symbol_definition (destructiveHint); …
- pass `tools.token_cost`: about 773 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 773 tokens to load them all
- tool set hash: b33fa979d06be7ed602756ed9da5ebdd
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.meemoprasad/meeba-brain.svg)](https://protogrid.dev/servers/io.github.meemoprasad/meeba-brain)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://meeba-context-mcp-469248886325.us-central1.run.app/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (5)

- `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_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_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.
- `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
different file.
- `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_definition or get_dependencies instead, they're more precise.