Skip to main content

MegaLens

ai.megalens/mcpVersion 1.0.0

Code review by AI models from different companies, usually two. Shows where they agree and disagree.

Status

Sign-in required187 msReachable. It asks for authorization, so we did not look inside.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 13:31 UTC
Latency
187 ms
Remotes responding
1 of 1
Sign-in
OAuth sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://megalens.ai/api/mcpSign-in required187 ms
OAuth sign-in

Claude Code

This server asks for sign-in. Your client opens the sign-in when it connects.

claude mcp add --transport http megalens https://megalens.ai/api/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'

Replace <YOUR_TOKEN> before running.

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: megalens
Remote MCP server URL: https://megalens.ai/api/mcp
This server expects the header Authorization.

Cursor

{
  "mcpServers": {
    "megalens": {
      "url": "https://megalens.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Replace <YOUR_TOKEN> before running.

VS Code

code --add-mcp '{"name":"megalens","type":"http","url":"https://megalens.ai/api/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'

Replace <YOUR_TOKEN> before running.

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

Tools are visible after sign-in; we do not look inside protected servers.

Details

Registry status
Active
Published
Sep 22, 2026
Updated
Sep 22, 2026
Categories (suggested)
Developer toolsAI modelsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing