PageLens AI vs Mcpskills Server — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
PageLens AI vs Mcpskills Server
In-depth architectural comparison of the PageLens AI and Mcpskills Server 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
Mcpskills Server
Security · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Verdict Summary: Choose PageLens AI if you need specialized Security tools running via a hosted cloud SSE transport. Choose Mcpskills Server 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).
AI website audit: security, SEO, performance, UX and accessibility checks with actionable fixes.
Pre-install trust layer for MCP servers, AI skills, and npm packages. Scores any repo or package across 15 signals (incl. OSV/KEV/EPSS vulnerability intelligence) with safety scanning for prompt injection, credential theft, and supply-chain risk; the autogate tool returns a go/no-go install decision. Listed in the official MCP Registry as io.mcpskills/server. npm: @mcpskillsio/server. https://mcpskills.io
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…
Mcpskills Server Tools (9)
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 is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Mcpskills Server belongs to Security using local stdio subprocess. Select PageLens AI when you need capabilities focused on security and Mcpskills Server when you require tools for security.
Score any AI skill, MCP server, or GitHub repo for trustworthiness. Returns a trust score (0-10) across 4 dimensions: Alive, Legit, Solid, Usable. Accepts: owner/repo, GitHub URL, npm package (npm:@scope/name or @scope/name), Smithery URL, or OpenClaw URL. AI skills get enhanced safety scanning. Set MCPSKILLS_API_KEY for full reports.
scan_safety
Run a focused safety scan on an AI skill or MCP server. Checks for prompt injection, shell execution, network exfiltration, credential theft, obfuscated payloads, public network binding (0.0.0.0), and risky npm lifecycle scripts (preinstall/install/postinstall). Accepts any input format (owner/repo, npm package, Smithery URL, etc.).
list_packages
Browse curated, pre-scored AI skill packages organized by use case. Each package contains vetted skills with trust scores. Available packages: Claude Power User, Full-Stack Vibe Coder, Data & Research, DevOps & Infrastructure, Content & Marketing.
get_badge
Get a trust badge URL for any repo or package. Returns a shields.io-style SVG badge showing the trust score and tier. Embed in READMEs. Badge auto-updates hourly.
watch_repo
Start monitoring a repo or package for trust score changes. Alerts when score changes significantly (±0.3 points or tier change). Requires a paid API key.
check_watched
Re-scan all watched repos and check for score changes. Returns any repos whose trust score changed significantly since last check.
batch_check
Check up to 5 repos or packages in one call. Returns a trust assessment for each. Requires a Developer Pro or Team API key. Accepts any mix of formats (owner/repo, npm packages, registry URLs).
auto_gate
Should I install this? Returns a simple go/no-go decision with reasoning. Accepts any format: owner/repo, npm package, Smithery URL, etc. Returns { proceed: true/false, reason: "..." }.
build_stack
Recommend a vetted stack of trusted tools for a described task. Describe what you're building (e.g., "Next.js app with auth, payments, and AI chat") and get back a curated list of the highest-scoring repos in each relevant category, pre-scored and ready to install. Returns tool names, trust scores, tiers, and install hints. Use this instead of guessing which tools to recommend — every suggestion is backed by live trust data.