← Registry

Analytics

xanlens.com

Runs a geographical visibility audit for a brand across AI search engines.

1 endpoint1 known toolsFirst detected May 15, 2026Last detected September 25, 2026

ENDPOINT 1

https://xanlens.com/api/mcp

No auth detected

MCP server metadata

Name
xanlens
Version
1.0.0
Capabilities
tools

Known tools 1

xanlens_audit

Run a GEO visibility audit for a brand across AI search engines

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.xanlens]
url = "https://xanlens.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "xanlens": {
      "type": "http",
      "url": "https://xanlens.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: xanlens
Remote MCP URL: https://xanlens.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "xanlens": {
      "url": "https://xanlens.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "xanlens": {
      "type": "http",
      "url": "https://xanlens.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "xanlens",
  "transport": "streamable-http",
  "url": "https://xanlens.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for xanlens.com was fetched 2026-08-04T03:02:31.597Z and is being refreshed.

Trust status Neutral

xanlens.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.