whoamiLABSCO SUMMARY
The launch report, sitting next to the code that has to change.
The value is not another audit — it is that the audit lands in the editor where the fix happens, so the agent reads what failed and why it matters before it starts patching.
What it is
A remote MCP server over PageLens AI, an independent launch reviewer for AI-built sites covering UX, SEO, performance, accessibility, security, conversion and QA journey audits. It authorises over OAuth and needs no local install.
What you get
- The domains on your account, listed
- The scans run against a domain, listed
- Scan results read from inside the editor: the owner verdict, the findings and the evidence behind them
- Findings carried across as agent-ready fix context
- Owner decisions recorded against findings
- A remote endpoint — nothing to install and no API key to manage
Requirements
A PageLens AI account. On first connect your client opens a browser to authorise over OAuth — there is no key to paste anywhere.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Picking up a report your agent should act on
List the domains on the account, then the scans behind the one you are working on.
02
Comparing this scan against the last one
Read the scan history for a domain and see what the previous run said before you judge this one.
03
Working out which failures actually block a launch
Read the owner verdict and the ranked findings behind it, rather than an undifferentiated checklist.
04
Handing a fix straight to a coding agent
The finding arrives with its fix context attached, so the agent patches from the evidence instead of a summary you retyped.
9 tools
Listed in project docs. Your client may show a different list.
list_domainslist_scansget_scanlist_findingsget_quick_winsreport_finding_feedbackacknowledge_finding_decisionclear_finding_decisionBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://www.pagelensai.com/api/mcpMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"pagelens": {
"url": "https://www.pagelensai.com/api/mcp"
}
}
}Codex
CODEX · TOML
[mcp_servers.pagelens]
url = "https://www.pagelensai.com/api/mcp"Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"pagelensai-mcp-server": {
"url": "https://www.pagelensai.com/api/mcp"
}
}
}
