Periscope MCP (Segentic Lab)

Frameworks & Eval · tested 2026-08-14 · by the Hlido desk, not the vendor

In short: A 74-tool Playwright QA server that returns verdicts rather than screenshots — a sharp idea, reviewed through its parent lab's index page because the project has no public surface of its own.

Quick answer

Periscope MCP (Segentic Lab) scores 61/100 (FADING) on Hlido’s independent, hands-on test (reviewed 2026-08-14). FADING because the checks this category needs — tool inventory, install path, configuration, evidence of the core claim — are all unmet on the public surface; the project has no page of its own and is represented only by Pricing: Open source (free entry point documented).

The idea is good and stated crisply: most browser-QA MCP servers hand an agent screenshots and let it guess, and Periscope instead exposes 74 Playwright tools that return hard verdicts. For an agent consumer that distinction is real — a pass/fail verdict is actionable, an image requires a vision round-trip and a judgement call. The project is Python, AGPL-3.0, and marked live alongside three siblings (lens-mcp, glovebox-mcp, hero-fx) from a Slovenian studio that publishes its build write-ups. The problem is that this is all the public surface says. The reviewed URL resolves to the lab's project index, not to Periscope itself — there is no project page, no tool inventory, no installation instructions, no configuration reference and no example verdict output. Everything specific about the product lives behind a 'read build' link or in the repository. So the differentiating claim, that the verdicts are hard and useful, is exactly the claim with no evidence attached to it. The score reflects a real and well-positioned tool that has not yet been given a surface an evaluator can assess. AGPL-3.0 is also worth flagging early rather than late: it is a deliberate choice with real consequences for anyone embedding this in a commercial product.

Why FADING

FADING because the checks this category needs — tool inventory, install path, configuration, evidence of the core claim — are all unmet on the public surface; the project has no page of its own and is represented only by a two-line card on a lab index. Not lower, because the positioning is specific rather than generic, the licence and language are declared, the project is marked live, and sibling projects suggest an active workshop. Confidence is low: this reviews a listing, not a product surface.

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-671e021c628a008b-lab-segentic-dev). Our own captures — not vendor marketing material.

Periscope MCP (Segentic Lab) — run screenshot 1 (home.png)
home.png
Periscope MCP (Segentic Lab) — run screenshot 2 (page__main.png)
page__main.png
Periscope MCP (Segentic Lab) — run screenshot 3 (page_.png)
page_.png
Periscope MCP (Segentic Lab) — run screenshot 4 (page__projects.png)
page__projects.png

What it does well

What it fails at

Red flags

Best for

  • Teams already comfortable with AGPL-3.0 who want structured QA verdicts instead of screenshot interpretation
  • Python shops preferring a Python-native browser QA server
  • Evaluators willing to go to the repository, since that is where all the substance lives

Not recommended for

  • Commercial products where AGPL-3.0 obligations are a blocker — decide this before investing time
  • Buyers who need to assess capability before installing; there is no public inventory to assess
  • Anyone wanting a supported product rather than a released workshop tool

Pricing & access

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-11.

Compared to

Agent relevance

MCP

Agentic-Commerce Readiness 33/100 · SURFACE-ONLY

Independent readiness for agent delegation & transaction. How it’s scored · check live

An MCP server with a stated 74-tool surface, but no published inventory or configuration, so an agent cannot evaluate or configure it without cloning the repository. The verdict-oriented output design would be strongly agent-friendly if it were documented.

Agent-friendly score: 5/10

Evidence

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-2+editorial-narrative-v2 · Methodology version 2026.08 ·

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Hlido trust score

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/segentic-lab-periscope-mcp.svg)](https://hlido.eu/check/?agent=segentic-lab-periscope-mcp)

HTML

<a href="https://hlido.eu/check/?agent=segentic-lab-periscope-mcp"><img src="https://hlido.eu/badge/segentic-lab-periscope-mcp.svg" alt="Hlido trust score"></a>