MegaLens MCP server
online · 100% uptimeai.megalens/mcp·v1.0.0Code review by AI models from different companies, usually two. Shows where they agree and disagree.
0 stars
Reviews
Write oneNobody has reviewed MegaLens yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
MegaLens tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 554ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 40 days ago12/15
- Maintainer identityregistry namespace matches repository owner; website matches verified namespace8/10
How MegaLens compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 134 ms
- faster than 76% of 30,031 servers
Install MegaLens in Claude Code, Cursor or VS Code
claude mcp add --transport http mcp https://megalens.ai/api/mcp
What the publisher says
From the MegaLens repository's README, as published. We do not edit it. Read it on GitHub
megalens-mcp
Code review from a panel of AI models, inside the AI tool you already use. MegaLens selects up to four AI models from different companies to review your code, and reports where they agree and where they disagree. On Free, MegaLens selects two reviewing models.
Works with Claude Code, Codex CLI, Cursor, Gemini CLI and Lovable. GitHub Copilot is coming soon.
Your first review is free, with no card.
Quick Start
npx megalens-mcp setupThe setup wizard:
- Asks for your MegaLens token (get one here)
- Detects installed tools automatically
- Writes the correct config for each tool
The wizard does not ask for an OpenRouter key. To use your own key, add one header by hand: see Adding your own OpenRouter key.
Supported Tools
If no tool is detected, the wizard lets you pick one and creates the config file. The wizard can also write configs for Windsurf and Grok Build. Those are not supported or tested.
Lovable needs no config file and no wizard. Paste the server URL and your token into Lovable's MCP connector form. Steps: megalens.ai/integrations/lovable
Manual Setup
The tools use two config languages and three different top-level keys, which is why the wizard exists.
Keep the ?ide= on each URL. It tells MegaLens which tool the review came from. It does not change which models review your code: the panel is the same whichever tool you call it from.
Claude Code
Run this once. The --scope user flag makes MegaLens available in every project:
claude mcp add --transport http --scope user megalens "https://megalens.ai/api/mcp?ide=claude-code" \
--header "Authorization: Bearer ml_tok_your_token_here"Or in .mcp.json (project) / ~/.claude.json (user):
{
"mcpServers": {
"megalens": {
"type": "http",
"url": "https://megalens.ai/api/mcp?ide=claude-code",
"headers": {
"Authorization": "Bearer ml_tok_your_token_here"
}
}
}
}Cursor
~/.cursor/mcp.json or .cursor/mcp.json. No type field. Cursor does not use one:
{
"mcpServers": {
"megalens": {
"url": "https://megalens.ai/api/mcp?ide=cursor",
"headers": {
"Authorization": "Bearer ml_tok_your_token_here"
}
}
}
}Gemini CLI
~/.gemini/settings.json. Gemini CLI uses httpUrl, not url:
{
"mcpServers": {
"megalens": {
"httpUrl": "https://megalens.ai/api/mcp?ide=gemini-cli",
"headers": {
"Authorization": "Bearer ml_tok_your_token_here"
}
}
}
}GitHub Copilot in VS Code (coming soon, not supported yet)
GitHub Copilot is coming soon. If you want to try it early: .vscode/mcp.json. The top-level key is servers, not mcpServers. A config written for Claude Code or Cursor will not be read here:
{
"servers": {
"megalens": {
"type": "http",
"url": "https://megalens.ai/api/mcp?ide=copilot",
"headers": {
"Authorization": "Bearer ml_tok_your_token_here"
}
}
}
}Codex
~/.codex/config.toml or .codex/config.toml. TOML, not JSON:
[mcp_servers.megalens]
url = "https://megalens.ai/api/mcp?ide=codex"
http_headers = { "Authorization" = "Bearer ml_tok_your_token_here" }Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
MegaLens: common questions
- Is MegaLens MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the MegaLens safety report
- How do I install MegaLens?
- It runs remotely at megalens.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does MegaLens need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is MegaLens maintained?
- The last commit was 42 days ago (2026-09-23). The latest release is v1.0.0.
- Is MegaLens up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does MegaLens compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 134 ms (faster than 76% of 30,031 servers). Full comparison.