kogiQA MCP Web Browser — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to kogiQA browser automation and exploratory testing: Does selector-free interaction provide reproducible evidence for page changes without borrowing screenshot-only assumptions?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Natural-language browser QA, debugging, exploration and end-to-end test development.

What we know

Selector-free browser automation MCP intended for agents to inspect, navigate and test web applications through natural-language tasks.

Maintenance / activity evidence

kogiqa-mcp 1.3.103 published 2026-09-11T15:40:51.382Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Browser-session authority over supplied URLs and any authenticated target session. Reported action classes: Submit forms or otherwise mutate target apps; Potentially drive development/test actions against local/staging/production URLs. Complete write authority is not verified.
Authentication not yet verified.
Sensitive access: Authenticated browser sessions, Internal web apps, Potential credentials/customer data

Broad browser automation with incomplete disclosed isolation/data-handling boundaries; use isolated test accounts and non-production targets.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does selector-free interaction provide reproducible evidence for page changes without borrowing screenshot-only assumptions?

The bounded review of the publisher's documented kogiQA browser automation and exploratory testing and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Broad browser automation with incomplete disclosed isolation/data-handling boundaries; use isolated test accounts and non-production targets.
Browser-session authority over supplied URLs and any authenticated target session.
Data-handling/telemetry behavior was not fully disclosed in the reviewed official pages.
Reviewed write actions: Submit forms or otherwise mutate target apps; Potentially drive development/test actions against local/staging/production URLs
Sensitive access: Authenticated browser sessions, Internal web apps, Potential credentials/customer data
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
server authentication
browser isolation
telemetry/retention
exact tool inventory
No server authentication or hosted endpoint is documented.
Browser interactions may mutate target applications.
Privacy/retention/telemetry and browser isolation boundaries were not established.
Exact MCP tool schemas are not listed in the reviewed README.

Original activity observations

kogiqa-mcp 1.3.103 published 2026-09-11T15:40:51.382Z

Technical identity

npm/kogiqa-mcp

Exact implementation source: https://www.npmjs.com/package/kogiqa-mcp ↗
Reviewed resource type: MCP Server
Repository identity: atagon-GmbH/kogiqa-mcp
Package identity: npm:kogiqa-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
kogiqa-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
atagon-gmbh/kogiqa-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.
Evidence source ↗
kogiqa.com/
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Claude Code only · Publisher instructions
claude mcp add kogiqa-browser npx kogiqa-mcp@latest
Configure / authenticate
MCP100 setup guide
Use publisher kogiqa-browser Claude Code registration, or VS Code/Cursor direct install; browser permission required.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Previously reviewed configuration / prerequisites: Node.js 20+
Check connection
Suggested check
Confirm browser MCP tools are listed; avoid page modification in verification.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `kogiqa-mcp` in Claude Code, remove its exact client entry with `claude mcp remove kogiqa-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Publisher install example registration name(s): kogiqa-browser. The supplied removal example applies only to an existing Claude Code registration named kogiqa-mcp; it does not remove the differently named install example. Confirm the actual host entry before use.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide · Review before use
```
claude mcp remove kogiqa-mcp
```

Official Documentation & Sources

What it does

Selector-free browser automation MCP intended for agents to inspect, navigate and test web applications through natural-language tasks.

Capability: Browser Automation
Resource type: MCP Server
Best fit: Natural-language browser QA, debugging, exploration and end-to-end test development.

Representative uses

Smoke-test user flows
Investigate CSS/layout issues
Collect browser console errors
Map/document an app
Generate browser tests

Limitations

No server authentication or hosted endpoint is documented.
Browser interactions may mutate target applications.
Privacy/retention/telemetry and browser isolation boundaries were not established.
Exact MCP tool schemas are not listed in the reviewed README.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Browser-session authority over supplied URLs and any authenticated target session.
Data handling: Data-handling/telemetry behavior was not fully disclosed in the reviewed official pages.
Cost: unknown
Risk and cautions: Broad browser automation with incomplete disclosed isolation/data-handling boundaries; use isolated test accounts and non-production targets.

Access scope and cautions

Write actions: Not verified Submit forms or otherwise mutate target apps Potentially drive development/test actions against local/staging/production URLs
Sensitive access: Authenticated browser sessions Internal web apps Potential credentials/customer data
Risk level: high

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Smoke-test user flows; Investigate CSS/layout issues; Collect browser console errors; Map/document an app; Generate browser tests.

What setup information is documented?

Recorded installation/entrypoint step: npx kogiqa-mcp@latest. Recorded transport: stdio. Prerequisites: Node.js 20+; MCP-compatible client. These are the documented setup details, not a claim that installation or client compatibility was independently tested.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Submit forms or otherwise mutate target apps; Potentially drive development/test actions against local/staging/production URLs. Recorded permission context: Browser-session authority over supplied URLs and any authenticated target session.

What data-handling boundary should I consider?

Data-handling/telemetry behavior was not fully disclosed in the reviewed official pages. Recorded sensitive-access context: Authenticated browser sessions; Internal web apps; Potential credentials/customer data.

What limitations and risks should I check before use?

Broad browser automation with incomplete disclosed isolation/data-handling boundaries; use isolated test accounts and non-production targets. No server authentication or hosted endpoint is documented. Browser interactions may mutate target applications. Privacy/retention/telemetry and browser isolation boundaries were not established. Exact MCP tool schemas are not listed in the reviewed README. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Atagon GmbH is listed as First-party MCP in MCP100’s current evidence.