← Registry

Security & Testing

clip.qa

An MCP server for accessing and managing bug reports, including report details, captured network requests, console logs, and screenshots from web recordings.

1 endpoint15 known toolsFirst detected May 29, 2026Last detected September 21, 2026

ENDPOINT 1

https://mcp.clip.qa/mcp

No auth detected

MCP server metadata

Name
clip-qa-mcp-remote
Version
1.0.0
Capabilities
tools
Server instructions

clip.qa remote MCP server. OAuth 2.1 PKCE at /.well-known/oauth-authorization-server; register at /oauth/register. 15 tools for reading bug reports (reports:read), analyzing video, and linking fixes (reports:write).

Known tools 15

listReports

List bug reports with title, severity, project, and creation date.

Inferred read-only
getDetails

Get a single report's full structured details: steps to reproduce, expected vs actual behavior, environment.

Inferred read-only
getNetworkRequests

Get the network requests captured during a web report recording.

Inferred read-only
getConsoleLogs

Get console log entries captured during a web report recording.

Inferred read-only
getScreenshots

Get screenshot URLs extracted from a report's key frames.

Inferred read-only
getVideoTranscript

Get the narrated transcript of a report recording, with timestamps.

Inferred read-only
analyzeVideo

Run AI analysis over a report's video frames (counts against the monthly AI quota).

Inferred read-only
searchReports

Full-text search across stored bug reports.

Inferred read-only
getReportDiff

Compare two versions of a report.

Inferred read-only
getProjectSummary

Get counts and health summary for one project.

Inferred read-only
getFrameAnalysis

Get per-frame OCR, change, and confidence analysis for a report.

Inferred read-only
getReportRaw

Get the raw stored report document as JSON, bypassing summarization.

Inferred read-only
createComment

Add a comment to a report (requires reports:write).

Potential side effects
linkFix

Link a fix (commit/PR) to a report (requires reports:write).

Potential side effects
linkFixAttempt

Record the outcome of a fix attempt (requires reports:write).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.clip-qa-mcp-remote]
url = "https://mcp.clip.qa/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "clip-qa-mcp-remote": {
      "type": "http",
      "url": "https://mcp.clip.qa/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: clip-qa-mcp-remote
Remote MCP URL: https://mcp.clip.qa/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "clip-qa-mcp-remote": {
      "url": "https://mcp.clip.qa/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "clip-qa-mcp-remote": {
      "type": "http",
      "url": "https://mcp.clip.qa/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "clip-qa-mcp-remote",
  "transport": "streamable-http",
  "url": "https://mcp.clip.qa/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.