What is the key difference between PageLens AI and Shield?

PageLens AI belongs to the Security category with cloud HTTP/SSE execution, while Shield belongs to the Security category with local stdio execution.

How do I install PageLens AI or Shield in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are PageLens AI and Shield free or paid?

PageLens AI operates under a Free / Open Source model (OAuth 2.0). Shield operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

PageLens AI lists 4 tools with 3 views and 1 GitHub stars. Shield lists 6 tools with 4 views and 11 GitHub stars.

Can I use both PageLens AI and Shield together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

PageLens AI vs Shield

In-depth architectural comparison of the PageLens AI and Shield MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

PageLens AI

Security · Remote HTTP/SSE

Quality: 49/100 (Fair) | Auth: OAuth 2.0

Shield

Security · Local stdio

Quality: 63/100 (Good) | Auth: No auth required

Verdict Summary: Choose PageLens AI if you need specialized Security tools running via a hosted cloud SSE transport. Choose Shield if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose PageLens AI when:

You need dedicated capabilities in the Security domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
Primary tools included: whoami, list_domains, list_scans.

Explore PageLens AI Details

Choose Shield when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Pre-execution MCP call guardrails, TOFU tool-catalog pinning, Tool description and result scanning.

Explore Shield Details

Feature & Specification Comparison

Specification	PageLens AI Security	Shield AperionAI Security
Summary	AI website audit: security, SEO, performance, UX and accessibility checks with actionable fixes.	Local guardrail proxy for AI coding agents. Wraps any MCP server (stdio or Streamable HTTP) and blocks destructive tool calls — DROP TABLE, rm -rf, force-push — before they execute. MCP supply-chain protection: TOFU tool-catalog pinning against rug pulls, plus tool-description and tool-result scanning for tool poisoning and prompt injection. 51 starter rules, approval gates, audit logging. Single binary, Apache-2.0.
Category & Scope

Tools & Capabilities Breakdown

PageLens AI Tools (4)

whoami

Confirm which PageLens account this MCP session is operating on, plus granted OAuth scopes.

list_domains

List the domains you've verified ownership of, along with badge tier and the scan currently anchored to the public badge.

list_scans

List 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 with…

get_scan

Read 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, jour…

Shield Tools (6)

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

PageLens AI Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "pagelens-ai": {
      "url": "https://www.pagelensai.com/api/mcp"
    }
  }
}

Shield Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "aperionai-shield": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-postgres"
      ]
    }
  }
}

Frequently Asked Questions

PageLens AI is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Shield belongs to Security using local stdio subprocess. Select PageLens AI when you need capabilities focused on security and Shield when you require tools for security.

More alternatives to PageLens AI More alternatives to Shield Security category hub Canonical compare URL