Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ai.mindola/lens

REMOTE · APP.MINDOLA.AI

Create your digital twin: a public page that answers from your own material, with citations.

Available components

0 this week 25 Trust /100

Last scanned (6 hours ago)

Scores higher than 10% of remote servers

Reachable. Last reached 5 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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.

  • 28 Oct 26 −61
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 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
  • 25 Sept 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
  • 30 Aug 26 0
    • Stability: 0.97 → pass security
  • 26 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
  • 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.

Diagnostics

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 5 Nov 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 1814, 3799 8, 8 Verified
mindola.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 402
Header Value
strict-transport-security max-age=63072000

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 HTTP error 402
http (plaintext) http://app.mindola.ai/mcp/lens HTTPS enforced 308 https://app.mindola.ai/mcp/lens
MCP tools · 3 exposed · ~527 tokens

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 →

Tool Tokens
add_lens_knowledge ~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.

NameTypeReqDescription
itemsarrayyes–
lens_tokenstringyesThe token from the lens's share URL (the part after /me/).

No output schema declared.

No examples provided.

create_digital_twin_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.

NameTypeReqDescription
accentColorstring–Optional hex color, for example #4f46e5.
audiencestring–Who this lens is intended to help or answer questions for.
biostring–A concise first-person or third-person biography assembled from user-confirmed information.
boundariesarray–Things the lens should not claim, discuss, or answer beyond. Ask the user to confirm these before calling.
contextstring–Extra grounding context for how the lens should answer. Use only information the user confirmed.
displayNamestring–The user's preferred public name for the lens, after they confirm it.
expertisearray–Specific domains, skills, or interests the user confirmed.
factsarray–Concrete user-approved facts to seed the lens memory. Each item should stand alone.
localestring–Optional BCP-47 locale for user-facing lens copy.
sourceSummarystring–Short note describing what ChatGPT used to assemble the profile, without exposing hidden chain-of-thought or unapproved private data.
suggestedPromptsarray–Starter questions visitors can ask the lens.
taglinestring–A short one-line summary of what this lens represents.
tonestring–The visitor-facing tone of the lens.
topicNamestring–The Mindola space name that will hold the seeded facts.
vibeWordsarray–Up to four short adjectives for the lens profile.
NameTypeReqDescription
claimRequiredbooleanyes–
claimUrlstring|nullyes–
displayNamestringyes–
expiresAtstring|nullyes–
factCountnumberyes–
manageUrlstring|nullyes–
shareUrlstringyes–
suggestedPromptsarrayyes–
topicNamestringyes–

No examples provided.

get_lens_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).

NameTypeReqDescription
lens_tokenstringyesThe token from the lens's share URL (the part after /me/).

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http ai-mindola-lens 'https://app.mindola.ai/mcp/lens'
Common questions

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 25 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?

Its publisher declares no required credentials for ai.mindola/lens. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.