In-depth architectural comparison of the Periscope MCP and MCP Accessibility Scanner 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
Periscope MCP
Browser Automation · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
MCP Accessibility Scanner
Browser Automation · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Periscope MCP if you need specialized Browser Automation tools running via a local process. Choose MCP Accessibility Scanner if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Periscope MCP when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Website & web-app testing built for AI agents rather than raw browser bindings: 66 Playwright tools with hard assertions, auto form-fill, persistent authenticated sessions (incl. interactive login for 2FA/SSO), network mocking, real INP, and accessibility/SEO/GEO (llms.txt, AI-crawler access, WebMCP) + Lighthouse audits.
MCP server for automated web accessibility scanning with Playwright and Axe-core.
Category & Scope
Tools & Capabilities Breakdown
Periscope MCP Tools (74)
create_project
Create a new testing project
list_projects
List all projects
get_project
Get project details
delete_project
Delete project + data
set_form_login
Configure username/password form login
set_basic_auth
Configure HTTP Basic Auth
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).
Periscope MCP is categorized under Browser Automation and uses a local stdio subprocess. In contrast, MCP Accessibility Scanner belongs to Browser Automation using local stdio subprocess. Select Periscope MCP when you need capabilities focused on browser automation and MCP Accessibility Scanner when you require tools for browser automation.
Open a **visible** window to log in by hand (2FA/SSO/CAPTCHA), then `save_login
save_login
Capture the manual-login session; the project then runs authenticated + headless
copy_auth
Copy auth config + session state between projects
test_url
Test a single URL (screenshot + checks)
+62 more tools listed on main page
MCP Accessibility Scanner Tools (42)
scan_page
Performs a comprehensive accessibility scan on the current page using Axe-core.
audit_site
Crawls and scans multiple internal pages, then aggregates violations across the site.
scan_page_matrix
Runs Axe scans on the same page across viewport/media/zoom variants and compares deltas against baseline.
audit_keyboard
Audits real keyboard focus behavior by pressing Tab (and optional Shift+Tab) with practical heuristics.
audit_screen_reader
Audits what a screen reader actually announces, using the browser's own accessibility tree (`page.ariaSnapshot`) plus element geometry. No screen reader is installed or driven; this is a static reading of the exposed tree.
browser_navigate
Navigate to a URL.
browser_navigate_back
Go back to the previous page.
browser_navigation_timeout
Set default navigation timeout for existing tabs.
browser_default_timeout
Set default operation timeout for existing tabs.
browser_snapshot
Capture accessibility snapshot of the current page (better than screenshot for analysis).
browser_find
Search the current page accessibility snapshot without returning the full snapshot.