# Mindola Lens MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.mindola%2Flens
Registry id: `mcp-registry/ai.mindola/lens`
Status: live (checked 2026-10-27T06:21:05.486Z)

## Verdict

Mindola Lens MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 1189 ms median handshake and 1 outage in 90 days. Its agent-readiness grade is A (93/100) across 3 tools, costing an agent about 1,057 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 1189 ms | 13% of MCP servers |
| p95 handshake latency | 3851 ms | — |
| Checks in 30 days | 4,998 | — |
| Outages, 90 days | 1 | — |
| Median recovery | 29 min | — |
| Agent-readiness score | 93/100 (A) | 75% of MCP servers |
| Tools | 3 | — |
| Tool-list size for an agent | ~1,057 tokens | 72% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "mindola-lens-mcp-server": {
      "type": "http",
      "url": "https://app.mindola.ai/mcp/lens"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http mindola-lens-mcp-server https://app.mindola.ai/mcp/lens
```

## Tools (3)

- `add_lens_knowledge`: Add text notes or URLs to a Mindola lens created in this conversation (before it is claimed). Content runs through the standard ingest pipeline so the lens can 
- `create_digital_twin_lens`: Create a shareable Mindola lens (AI clone) from a profile the user has approved in this conversation. Call this only after summarizing the proposed lens for the
- `get_lens_status`: Check a Mindola lens: its share URL, whether it has been claimed, and how much of its knowledge has finished ingesting (ready / pending / failed).

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.