Periscope Mcp vs Feedthrough

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
P
Periscope Mcp
segentic-lab
📂 Browser Automation
Feedthrough
feedthrough
📂 Browser Automation
SummaryWebsite & 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.In-browser debug bridge that injects into your running web app, so an agent can read the DOM, console logs and network requests, and click/fill/inspect the page. Runs inside the page (not an external CDP driver), so it works in any browser and inside Cypress/Playwright runs.
Quality signal23/100 (Emerging)24/100 (Emerging)
Install pathnpx · lownpx · high
Engagement 0 0 0 0 0 0 4
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView Periscope McpView Feedthrough
More alternatives to Periscope McpMore alternatives to FeedthroughBrowser Automation categoryCanonical compare URL

Other servers like Periscope Mcp