Website testing for AI agents: 63 Playwright tools, auth sessions, a11y/SEO/GEO + Lighthouse audits
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-segentic-lab-periscope-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Website testing for AI agents: 63 Playwright tools, auth sessions, a11y/SEO/GEO + Lighthouse audits
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in browser / ai-ml
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
An autonomous agent that conducts deep research on any data using any LLM providers
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
MCP Security Weekly
Get CVE alerts and security updates for io.github.segentic-lab/periscope-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server that gives AI agents 74 Playwright tools to QA, test, and analyze web apps — static sites, SPAs, and apps behind a login — returning hard verdicts, not screenshots to squint at. Not a thin wrapper around browser APIs; the tools are shaped around how agents actually work:
assert_condition returns
passed: true/false with the actual value; checks return structured issues.auto_fill_form detects, infers, and fills a
whole form; interact_and_test batches 25 action types with checks;
test_project crawls and audits an entire site.Playwright + headless Chrome underneath; site crawling, responsive testing, and screenshot diffing on top. Works with any MCP client — Claude Code, Codex, Cursor, Windsurf, Gemini CLI, custom agents, or anything else that speaks MCP over stdio.
playwright-mcp is excellent at what it is: general browser control over MCP, with tools that mirror Playwright's own API. If the job is "browse this site, click around, extract something," use it.
Periscope exists for a different job: testing and auditing a site or web app, then reporting findings — and its tools encode the testing knowledge an agent would otherwise have to reinvent every session:
| Raw browser control | Periscope | |
|---|---|---|
| Verifying an outcome | Read a screenshot or DOM dump and judge | assert_condition → hard passed: true/false + actual value |
| Filling a form | One call per field, agent invents test data | auto_fill_form — detects fields, infers realistic data, reports per-field failures |
| Auth | Re-login by scripting clicks each session | Projects persist form/basic/cookie auth; sessions share the logged-in context |
| Site-wide audit | Loop pages manually | test_project — crawl + accessibility/SEO/GEO/visual/functionality checks + saved report |
| Diagnosing a broken page | Ask for logs, replay requests | Response bodies, console, and network are captured automatically; mock APIs with intercept_network |
| Silent failures | Drag "succeeds," nothing moved | Flagged in the result, with the recovery path spelled out |
| AI-readiness audits | — | robots.txt AI-crawler access, llms.txt, WebMCP annotations, JSON-LD, plus real Lighthouse scores |
The two aren't rivals — an agent can happily use playwright-mcp for browsing tasks and Periscope when it's wearing the QA hat. Periscope's design bets are simply about that hat: fewer, higher-level calls; structured verdicts instead of raw page state; and errors written to tell the agent what to do next.
MCP client (AI agent) --> MCP Server (stdio) --> Playwright (Headless Chrome)
| |
+-- Projects (JSON) +-- Persistent Sessions
+-- Screenshots (PNG)
... [View full README on GitHub](https://github.com/segentic-lab/periscope-mcp#readme)