mcpbeat Sign in

Cybret findings MCP Server

answering

Cybret findings is answering right now. Last checked 13 min ago.

Validated API and app vulnerability findings with remediation guidance.

Uptime history 4 days of history · worst day 97%
4 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
318 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Cybret findings does not always answer

Over the last week it answered 99.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add findings --transport http https://mcp.cybret.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "findings": {
      "url": "https://mcp.cybret.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.findings]
url = "https://mcp.cybret.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "findings": {
      "url": "https://mcp.cybret.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "findings": {
      "url": "https://mcp.cybret.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.cybret.ai/mcp streamable-http sign-in 846 ms 13 min ago

Alternatives to Cybret findings

same job, measured the same way
Vulnerability Scanner
by 4hmetuyar

Triggers GuardBee scans, queries findings, AI-assisted remediation guidance

43 installs/wk local only
Snyk API & Web MCP Server
by snyk

MCP server for Snyk API & Web — DAST scanning, findings management, and vulnerability triage

138 installs/wk local only
V
Vaast
by xtrinel

Read-only access to VAAST vulnerability scan findings, workspaces, and targets for AI agents

47 installs/wk local only
Bright Security
by neuralegion

AI-powered application security testing — scan APIs, discover endpoints, and find vulnerabilities.

answering
MCP Code Sanitizer
by notasandy

Strict AI code reviewer powered by Groq. Finds bugs and vulnerabilities.

113 installs/wk local only
Cisa Kev MCP
by csoai-org

CISA Known Exploited Vulnerabilities feed + remediation deadlines for US federal + critical infr...

172 installs/wk local only
Nvd
by pipeworx-io

NVD MCP — wraps the NIST National Vulnerability Database API.

39 tools answering
PkgSeek Linux Intelligence
by yeagoo

Linux package, file, command, vulnerability, lifecycle, migration, and repository intelligence.

23 tools answering

Cybret findings — questions

Answers built from our own checks of this server.

Why is there no tool list for Cybret findings?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Cybret findings working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 318 ms. The bar chart above shows every period we have measured.
How do I connect Cybret findings?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Cybret findings?
No API key is involved. Cybret findings answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Cybret findings?
It answers our handshake in 318 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.