GitHits
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
AI website audit: security, SEO, performance, UX and accessibility checks with actionable fixes.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 3/12 | Full marks for a release or code change within 30 days |
| Still answering | 8/8 | The cloud endpoint answered at the last check |
| Usage score | 15/100 |
Quality: Passed 5/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install PageLens AI. Follow https://mcp.popnx.com/i/pagelens-ai-pagelensai-mcp-server.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (www.pagelensai.com) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
PageLens AIhttps://www.pagelensai.com/api/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsPageLens AI
Use PageLens AI and tell me what you can do for me, then show me one thing✓ If Claude says it is using PageLens AI or shows a PageLens AI tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
PageLens AIhttps://www.pagelensai.com/api/mcpStart a new chat and pick PageLens AI from your plugins before typing
Use PageLens AI and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using PageLens AI or shows a PageLens AI tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user pagelensai https://www.pagelensai.com/api/mcpYou should see PageLens AI listed as connected
Use PageLens AI and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using PageLens AI or shows a PageLens AI tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use PageLens AI and tell me what you can do for me, then show me one thing✓ If Cursor says it is using PageLens AI or shows a PageLens AI tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use PageLens AI and tell me what you can do for me, then show me one thing✓ If VS Code says it is using PageLens AI or shows a PageLens AI tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://www.pagelensai.com/api/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user pagelensai https://www.pagelensai.com/api/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"pagelensai": {
"url": "https://www.pagelensai.com/api/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"pagelensai": {
"type": "http",
"url": "https://www.pagelensai.com/api/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account PageLens-AI, which owns the repo
Code last changed 5 months ago
Uses MIT
Responded in 406 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/pagelens-ai-pagelensai-mcp-server)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 5 months ago, and the latest version (1.0.0) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: GitHits, Dependency Management MCP Server, Snyk MCP, TokenSafe, Draugr
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Sonatype component intelligence: versions, security analysis, and Trust Score recommendations
Easily find and fix security issues in your applications leveraging Snyk platform capabilities.
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
| This one PageLens AI | GitHits | Dependency Management MCP Server | Snyk MCP | TokenSafe | Draugr | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Cloud or install on your computer | Runs in the cloud, nothing to install | Installs on your computer | Cloud or install on your computer | Installs on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 5/5 | 5/5 | 3/4 | 3/3 | 5/5 | 3/3 |
| License | MIT | Apache-2.0 | – | Apache-2.0 | MIT | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Connect PageLens AI reports to Claude Desktop, Cursor, Codex, and other MCP clients so your AI assistant can understand what failed, why it matters, and what to fix next.
An MCP (Model Context Protocol) server that gives AI agents direct access to PageLens AI - the independent launch reviewer for AI-built websites. PageLens AI turns launch risk across UX, SEO, Performance, Accessibility, Security, Conversion, and QA journey audits into plain-English priorities and agent-ready fix context.
Plug it into Cursor, Claude Desktop, Codex, or any MCP-compatible client and your agent can read scan results, drill into findings, surface quick wins, record owner decisions, and help close the fix loop without leaving the IDE.
https://www.pagelensai.com/api/mcp
This is a remote MCP server — no local install required.
If you do not want to read technical detail, start in the PageLens web report and copy the fix prompt into Lovable, Bolt, Replit, Cursor, Codex, Claude Code, Copilot, or Windsurf. If you do want your coding agent to work directly with the report data, connect this MCP server.
Add to your ~/.cursor/mcp.json (or workspace .cursor/mcp.json):
{
"mcpServers": { "pagelens": { "url": "https://www.pagelensai.com/api/mcp" } } }
Add to claude_desktop_config.json:
{
"mcpServers": { "pagelens": { "type": "http", "url": "https://www.pagelensai.com/api/mcp" } } }
Add to ~/.codex/config.toml:
[mcp_servers.pagelens]
url = "https://www.pagelensai.com/api/mcp"
Use the streamable HTTP endpoint:
https://www.pagelensai.com/api/mcp
This server uses OAuth 2.0. Your MCP client will open a browser window to authorize with your PageLens account on first connect. No API keys to manage.
Scopes granted on authorization:
| Scope | What it unlocks |
|---|---|
read:scans | List and read your scan results |
read:findings | Read findings and quick wins |
write:feedback | Submit finding feedback and owner decisions |
whoamiConfirm which PageLens account this MCP session is operating on, plus granted OAuth scopes.
{}
list_domainsList the domains you've verified ownership of, along with badge tier and the scan currently anchored to the public badge.
{
"include_unverified": false }
list_scansList your most recent PageLens scans. Filter by status, domain, or date. Returns a slim summary per scan (id, URL, score, grade, severity counts, and launchVerdict). Scans may include launchContext with builderPlatform and launchMoment so agents can frame fixes for the owner's workflow without changing evidence or severity. QA Audit scans include a compact qaAudit summary with confidence, journey-step count, pages reviewed versus page budget, blocked/needs-review step counts, auth-profile status, and the reason fewer than the page budget were captured when the safe same-origin link graph is exhausted.
{
"limit": 20, "status": "COMPLETE", "domain": "example.com", "since": "2026-01-01T00:00:00Z" }
Status values: PENDING · RUNNING · COMPLETE · FAILED · CANCELLED
get_scanRead the full summary for a single scan: score, grade, owner-first launchVerdict, severity counts, launch context, executive summary, top-5 highest-priority findings, and per-persona reviews. For QA Audit scans, get_scan also returns a qaAudit block containing the product-flow synthesis, journey replay, safe blocked actions, confidence, authenticated-route context, and page-budget coverage.
{
"scan_id": "clxxxxxxxxxxxxxxx" }
pagelensai://scan/{id}/markdownFetch the same agent-flavoured Markdown report available from the PageLens UI. Standard reports include launch-context and verdict front matter such as ai_builder, launch_moment, launch_verdict_status, and launch_verdict when captured, followed by an Owner launch verdict section and an AI-builder priority prompt pack your agent can act on before it reaches the detailed evidence. For QA Audit scans, this includes front matter such as qa_journey_event_count, qa_confidence, and qa_needs_review_step_count, followed by the application interpretation, journey replay, blocked/risky paths, safe actions, and next QA tests.
Use this when an agent needs rich context to reason about a QA Audit:
pagelensai://scan/clxxxxxxxxxxxxxxx/markdown
pagelensai://scan/{id}/summary.jsonFetch compact JSON for a scan. Standard scans include the same launchVerdict object returned by list_scans and get_scan: status, label, headline, summary, and next step. For QA Audit scans, the qaAudit object includes journey metadata, synthesis, page-budget coverage, and any queue_exhausted reason explaining why fewer than the purchased page count were discoverable.
pagelensai://scan/clxxxxxxxxxxxxxxx/summary.json
list_findingsPage through all findings for a scan. Filter by severity, category, persona, page URL, or rule ID. Use format: "full" to include descriptions, suggestions, and evidence.
{
"scan_id": "clxxxxxxxxxxxxxxx", "severity": "HIGH", "category": "SECURITY", "format": "full", "limit": 50 }
Severity levels: CRITICAL · HIGH · MEDIUM · LOW · INFO
Categories: UX · SEO · PERFORMANCE · ACCESSIBILITY · SECURITY · CONTENT · HEADERS · DESIGN · ERROR
Personas: MARKETER · CRO · UX · ACCESSIBILITY · BRAND · EXECUTIVE · PERFORMANCE · SEO
get_quick_winsReturn the top N quick-win findings — high impact, low-to-moderate effort — ranked by the same Impact × Effort scorer used in the PageLens dashboard. Optionally override the scan's preset to re-rank under a different lens.
{
"scan_id": "clxxxxxxxxxxxxxxx", "limit": 5, "preset_override": "CONVERSION" }
Presets: PRE_SALES · PRE_LAUNCH · CONVERSION · INVESTOR · BRAND_POLISH
report_finding_feedbackFlag a finding as a false positive, wrong severity, wrong category, or not actionable. Requires a paragraph of reasoning and a concrete evidence snippet.
{
"finding_id": "clxxxxxxxxxxxxxxx", "kind": "FALSE_POSITIVE", "reason": "The selector .pointer-events-auto matches 100+ utility classes, not a single offending element.", "evidence": " — Tailwind utility, not an event-handler.", "proposed_severity": "LOW" }
Feedback kinds: FALSE_POSITIVE · INCORRECT_SEVERITY · INCORRECT_CATEGORY · NOT_ACTIONABLE · OTHER
acknowledge_finding_decisionAttach owner-controlled context to a finding when the issue is real, but reflects an intentional architecture, security, or product tradeoff.
This does not hide the finding, edit the report, or change the PageLens score. It records the rationale so the report can show that the owner has acknowledged the tradeoff, and future scans can recognise the same finding as previously acknowledged.
{
"finding_id": "clxxxxxxxxxxxxxxx", "decision": "INTENTIONAL_TRADEOFF", "reason": "Next.js Cache Components and PPR currently prevent us from using per-request CSP nonces safely.", "evidence": "proxy.ts documents the CSP tradeoff: script-src uses 'unsafe-inline' because cached HTML shells cannot vary nonces per request.", "expires_at": "2026-10-01T00:00:00Z" }
Decision kinds: ACKNOWLEDGED · ACCEPTED_RISK · INTENTIONAL_TRADEOFF · WONT_FIX_NOW
clear_finding_decisionClear a previously acknowledged decision so it stops appearing on current and future reports. The audit history is preserved.
{
"decision_id": "clxxxxxxxxxxxxxxx", "reason": "We have migrated to a nonce-compatible rendering path." }
You can also clear by finding_id when you do not have the decision_id.
Each scan runs a deterministic rule engine + AI reviewer pipeline across every page:
| Area | Examples |
|---|---|
| SEO | Title/meta length, canonical URL, Open Graph, heading hierarchy |
| Performance | Core Web Vitals (LCP, CLS, INP), page weight, render-blocking resources, DOM size, third-party load |
| Security | HTTP→HTTPS redirect, exposed .env/.git files, SSL expiry, XSS surfaces, source maps, exposed secrets in page source |
| Accessibility | Focus-visible CSS, reduced-motion support, ARIA patterns |
| UX | Hero hierarchy, mobile menu patterns, CTA structure |
| Content | Placeholder text, stale copyright year, mixed-content references |
| QA Audit | Journey replay, safe form/input exploration, blocked risky actions, app-flow synthesis, page-budget coverage |
Findings include severity, effort estimate, copy-pasteable evidence, and a one-line fix suggestion.
QA Audit scans are different from standard technical scans: the primary artifact is the agentic journey report. PageLens will attempt to review the purchased page budget (for example, up to 10 pages on QA Audit) and should only return fewer pages when the safe same-origin link graph is exhausted. It can use validated auth profiles for scoped post-login routes, while still avoiding SSO, CAPTCHA, MFA, signup, payment, destructive changes, and other committing actions.
Fix with my AI builder:
"Read the latest PageLens Launch Pack report for example.com, list the top 3 owner-risk fixes, and turn each one into a patch plan I can apply in this repo."
Respect launch context:
"Open the latest PageLens report. If it was built with Codex or Cursor and the launch moment is Product Hunt, prioritise the fixes that make it safe to post publicly, then give me exact patches."
Pre-launch audit in Cursor:
"Use the latest PageLens scan for my staging site, list all CRITICAL and HIGH findings, and create GitHub issues for the top 5."
CRO review:
"Fetch the latest scan for example.com, get the CONVERSION quick wins, and summarise what to fix before the campaign launch."
Security sweep:
"List all SECURITY findings with severity HIGH or above from my last scan and show me the evidence for each."
Accepted architecture decision:
"For the CSP unsafe-inline finding, acknowledge this as an intentional Next.js/PPR tradeoff with the rationale from our security docs. Do not mark it as a false positive."
Post-fix validation:
"I re-ran PageLens from the CLI/API after fixing the findings. Compare the latest scan to the previous one and tell me what improved, regressed, or still needs work."
MCP reads and works with report data through OAuth. To create a new scan from automation, use the PageLens CLI, API, GitHub Action, or deploy hooks with a Pro+ plan; then ask your MCP-connected assistant to inspect the completed report.
QA Audit review:
"Fetch the latest QA Audit for example.com, read the markdown resource, and tell me which user journeys were verified, which actions were blocked safely, and whether PageLens reviewed the full page budget."
PageLens AI suppor