io.github.meemoprasad/meeba-brain
REMOTE · MEEBA-CONTEXT-MCP-469248886325.US-CENTRAL1.RUN.APP · SCANNED AUG 17
Ground-truth code graph for your codebase: exact callers, callees, symbols & dependencies.
Available components
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. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 587 tokens (~117/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · meeba-context-mcp-469248886325.us-central1.run.app
claude mcp add --transport http meemoprasad-meeba-brain https://meeba-context-mcp-469248886325.us-central1.run.app/mcp
[mcp_servers.meemoprasad-meeba-brain] url = "https://meeba-context-mcp-469248886325.us-central1.run.app/mcp"
{
"$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 mcp add meemoprasad-meeba-brain --url https://meeba-context-mcp-469248886325.us-central1.run.app/mcp --transport streamable-http
mcp_servers:
meemoprasad-meeba-brain:
url: "https://meeba-context-mcp-469248886325.us-central1.run.app/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Aug 26 +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.
- 15 Aug 26 +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.
- 13 Aug 26 +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.
- 11 Aug 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 +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.
- 9 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Aug 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Aug 2026 · Probed https://meeba-context-mcp-469248886325.us-central1.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WR2,O=Google Trust Services,C=US | 20 Jul 2026 | 12 Oct 2026 | ECDSA 256 | SHA256-RSA | 38debd2c8e3a8edd0a7d8f666faac3dd |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WR2,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a07c4cded100ad9d66a5107b98 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of meeba-context-mcp-469248886325.us-central1.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://meeba-context-mcp-469248886325.us-central1.run.app/mcp | Verified | 200 | |
| http (plaintext) | http://meeba-context-mcp-469248886325.us-central1.run.app/mcp | HTTPS enforced | 302 | https://meeba-context-mcp-469248886325.us-central1.run.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_callees ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| function_name | string | yes | The bare function/method name (e.g. "sync_repository"). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_callers ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| function_name | string | yes | The bare function/method name (e.g. "save_user"). If multiple unrelated symbols share this name, results are grouped by which definition they call. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_dependencies ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_symbol_definition ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_code ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural-language or keyword description of what you're looking for. |
| top_k | integer | – | Max number of results to return (default 8, max 20). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.