ai.mindola/lens
REMOTE · APP.MINDOLA.AI · SCANNED SEP 21
Create your digital twin: a public page that answers from your own material, with citations.
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 683 tokens (~227/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the ai.mindola/lens MCP server?
ai.mindola/lens is a hosted endpoint at https://app.mindola.ai/mcp/lens, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.mindola.ai
claude mcp add --transport http ai-mindola-lens 'https://app.mindola.ai/mcp/lens'
{
"mcpServers": {
"ai-mindola-lens": {
"url": "https://app.mindola.ai/mcp/lens"
}
}
} {
"servers": {
"ai-mindola-lens": {
"type": "http",
"url": "https://app.mindola.ai/mcp/lens"
}
}
} [mcp_servers.ai-mindola-lens] url = "https://app.mindola.ai/mcp/lens"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-mindola-lens": {
"type": "remote",
"url": "https://app.mindola.ai/mcp/lens",
"enabled": true
}
}
} openclaw mcp add ai-mindola-lens --url 'https://app.mindola.ai/mcp/lens' --transport streamable-http
mcp_servers:
ai-mindola-lens:
url: "https://app.mindola.ai/mcp/lens" {
"McpServers": {
"ai-mindola-lens": {
"Transport": "http",
"Url": "https://app.mindola.ai/mcp/lens"
}
}
} assistant mcp add ai-mindola-lens -t streamable-http -u 'https://app.mindola.ai/mcp/lens'
{
"mcpServers": {
"ai-mindola-lens": {
"type": "http",
"url": "https://app.mindola.ai/mcp/lens"
}
}
} 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.
- 30 Aug 26 +1
- Stability: 0.97 → pass security
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Jul 26 0
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 21 Sept 2026 · Probed https://app.mindola.ai/mcp/lens
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.mindola.ai | CN=YR2,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 5a9b8917ad4a49a54c67c19d6869869f691 |
| SANs: app.mindola.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.mindola.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| mindola.ai. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://telegram.org https://*.i.posthog.com https://us-assets.i.posthog.com https://eu-assets.i.posthog.com https://va.vercel-scripts.com https://*.crisp.chat; worker-src 'self' blob: https://*.crisp.chat; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net https://*.crisp.chat; img-src 'self' blob: data: https:; media-src 'self' blob: data: https:; font-src 'self' https://fonts.gstatic.com https://cdn.jsdelivr.net https://*.crisp.chat; connect-src 'self' https://vercel.com https://eu.i.posthog.com https://us.i.posthog.com https://eu-assets.i.posthog.com https://us-assets.i.posthog.com https://*.blob.vercel-storage.com https://*.public.blob.vercel-storage.com https://*.ingest.sentry.io https://*.ingest.de.sentry.io https://*.ingest.us.sentry.io https://*.ingest.eu.sentry.io https://vitals.vercel-insights.com https://*.crisp.chat wss://*.relay.crisp.chat; manifest-src 'self'; frame-src 'self' https://oa |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.mindola.ai/mcp/lens | Verified | 200 | |
| http (plaintext) | http://app.mindola.ai/mcp/lens | HTTPS enforced | 308 | https://app.mindola.ai/mcp/lens |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_lens_knowledge Add knowledge to a lens ~79
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 answer from it, with citations.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| lens_token | string | yes | The token from the lens's share URL (the part after /me/). |
No output schema declared.
No examples provided.
create_digital_twin_lens Create a Mindola lens ~382
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 user and receiving explicit confirmation. Use only information the user provided or confirmed in the conversation; do not claim access to hidden memory, private chats, or external accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| accentColor | string | – | Optional hex color, for example #4f46e5. |
| audience | string | – | Who this lens is intended to help or answer questions for. |
| bio | string | – | A concise first-person or third-person biography assembled from user-confirmed information. |
| boundaries | array | – | Things the lens should not claim, discuss, or answer beyond. Ask the user to confirm these before calling. |
| context | string | – | Extra grounding context for how the lens should answer. Use only information the user confirmed. |
| displayName | string | – | The user's preferred public name for the lens, after they confirm it. |
| expertise | array | – | Specific domains, skills, or interests the user confirmed. |
| facts | array | – | Concrete user-approved facts to seed the lens memory. Each item should stand alone. |
| locale | string | – | Optional BCP-47 locale for user-facing lens copy. |
| sourceSummary | string | – | Short note describing what ChatGPT used to assemble the profile, without exposing hidden chain-of-thought or unapproved private data. |
| suggestedPrompts | array | – | Starter questions visitors can ask the lens. |
| tagline | string | – | A short one-line summary of what this lens represents. |
| tone | string | – | The visitor-facing tone of the lens. |
| topicName | string | – | The Mindola space name that will hold the seeded facts. |
| vibeWords | array | – | Up to four short adjectives for the lens profile. |
| Name | Type | Req | Description |
|---|---|---|---|
| claimRequired | boolean | yes | – |
| claimUrl | string|null | yes | – |
| displayName | string | yes | – |
| expiresAt | string|null | yes | – |
| factCount | number | yes | – |
| manageUrl | string|null | yes | – |
| shareUrl | string | yes | – |
| suggestedPrompts | array | yes | – |
| topicName | string | yes | – |
No examples provided.
get_lens_status Check a lens's status ~66
Check a Mindola lens: its share URL, whether it has been claimed, and how much of its knowledge has finished ingesting (ready / pending / failed).
| Name | Type | Req | Description |
|---|---|---|---|
| lens_token | string | yes | The token from the lens's share URL (the part after /me/). |
No output schema declared.
No examples provided.
What is the ai.mindola/lens MCP server?
ai.mindola/lens is an MCP server listed in the public MCP registry as ai.mindola/lens. Create your digital twin: a public page that answers from your own material, with citations. This page covers its hosted endpoint (https://app.mindola.ai/mcp/lens).
Is the ai.mindola/lens MCP server safe to use?
ai.mindola/lens scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.mindola/lens MCP server expose?
ai.mindola/lens exposes 3 tools: create_digital_twin_lens, add_lens_knowledge, get_lens_status. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.
Does the ai.mindola/lens MCP server require authentication?
No. We connected to ai.mindola/lens without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.mindola/lens MCP server still maintained?
ai.mindola/lens is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.