# io.github.meemoprasad/meeba-brain (remote · meeba-context-mcp-469248886325.us-central1.run.app)

Ground-truth code graph for your codebase: exact callers, callees, symbols & dependencies.

- Trust score: 69/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-17

## Components

- remote · `meeba-context-mcp-469248886325.us-central1.run.app`: 69/100 (this document), [markdown](https://verifymcp.io/servers/meemoprasad-meeba-brain/meeba-context-mcp-469248886325.md), [page](https://verifymcp.io/servers/meemoprasad-meeba-brain/meeba-context-mcp-469248886325)

## Channel facts

- Endpoint: `https://meeba-context-mcp-469248886325.us-central1.run.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-17.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 587 tokens (~117/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http meemoprasad-meeba-brain https://meeba-context-mcp-469248886325.us-central1.run.app/mcp
```

### Codex

```toml
[mcp_servers.meemoprasad-meeba-brain]
url = "https://meeba-context-mcp-469248886325.us-central1.run.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "meemoprasad-meeba-brain": {
      "type": "remote",
      "url": "https://meeba-context-mcp-469248886325.us-central1.run.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add meemoprasad-meeba-brain --url https://meeba-context-mcp-469248886325.us-central1.run.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  meemoprasad-meeba-brain:
    url: "https://meeba-context-mcp-469248886325.us-central1.run.app/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-17 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-15 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-13 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-11 (score 66, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-09 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-08 (score 62)

First indexed and scored.

## MCP tools (5)

### `search_code` (~113 tokens)

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.

Input parameters:

- `query` (string, required): Natural-language or keyword description of what you're looking for.
- `top_k` (integer): Max number of results to return (default 8, max 20).

Output parameters:

- `result` (string)

### `get_symbol_definition` (~118 tokens)

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.

Input parameters:

- `name` (string, required): The bare symbol name (e.g. "get_upstream_impact"), or "ClassName.method_name" for a specific method when the bare name is ambiguous across multiple classes.

Output parameters:

- `result` (string)

### `get_callers` (~106 tokens)

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.

Input parameters:

- `function_name` (string, required): The bare function/method name (e.g. "save_user"). If multiple unrelated symbols share this name, results are grouped by which definition they call.

Output parameters:

- `result` (string)

### `get_callees` (~76 tokens)

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.

Input parameters:

- `function_name` (string, required): The bare function/method name (e.g. "sync_repository").

Output parameters:

- `result` (string)

### `get_dependencies` (~98 tokens)

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.

Input parameters:

- `file_path` (string, required): Repo-relative path (e.g. "utils/knowledge_graph/graph_builder.py"). Matches by exact path first, then by suffix if no exact match (so "graph_builder.py" alone will still resolve if unambiguous).

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/meemoprasad-meeba-brain/meeba-context-mcp-469248886325#diagnostics

## Score history

- 2026-08-17: 69
- 2026-08-16: 68
- 2026-08-15: 68
- 2026-08-14: 67
- 2026-08-13: 67
- 2026-08-12: 66
- 2026-08-11: 66
- 2026-08-10: 63
- 2026-08-09: 62
- 2026-08-08: 62

## Links

- Remote endpoint: https://meeba-context-mcp-469248886325.us-central1.run.app/mcp
- Repository: https://github.com/meemoprasad/meeba-brain-marketplace
- Changelog RSS feed: https://verifymcp.io/servers/meemoprasad-meeba-brain/meeba-context-mcp-469248886325.xml
- Changelog JSON feed: https://verifymcp.io/servers/meemoprasad-meeba-brain/meeba-context-mcp-469248886325.json
- HTML version of this page: https://verifymcp.io/servers/meemoprasad-meeba-brain/meeba-context-mcp-469248886325