mcpbeat Sign in

Fuzz-Breaker MCP Server

answering

Fuzz-Breaker is answering right now. Last checked moments ago.

Automated API pentesting and structural fuzzing proxy.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
90 ms
Response time
average over 24h
authentication required
Access
sse

Nothing serious here today

Today is the operative word: we check Fuzz-Breaker every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 0 min ago.

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

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://fuzz-breaker-mcp.vercel.app/api/mcp sse needs auth 44 ms 0 min ago

Alternatives to Fuzz-Breaker

same job, measured the same way
Browserbase
by mcparmory

Create and control browser sessions for web automation, testing, and AI agent tasks

241 installs/wk local only
HasData Booking.com
by hasdata

Booking.com stays by destination and dates, and full property details, as structured JSON.

151 installs/wk answering
Real Estate Listings
by dataleadspro

Pull property listings, prices, and details from real-estate sites as structured JSON.

1 tools answering
MCP Sap Gui
by kts982

SAP GUI for Windows automation for AI agents - 59 structured tools via SAP GUI Scripting API

273 installs/wk local only
Pare Lint
by dave-london

Pare Lint ג€” Structured linting and formatting (ESLint, Prettier, Biome, Oxlint) as typed JSON.

145 installs/wk local only
Httpstatus
by httpstatus

AI-callable tools for API mocking, testing, monitoring, security, and automation.

answering
SelfHeal MCP
by carsonroell-debug

Self-healing proxy for MCP servers with retry, circuit breaker, and observability

31 installs/wk local only
StyleForge-AI
by evozim

Automated design token builder producing clean CSS and Sass assets.

answering

Fuzz-Breaker — questions

Answers built from our own checks of this server.

Why is there no tool list for Fuzz-Breaker?
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 Fuzz-Breaker working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 90 ms. The bar chart above shows every period we have measured.
How do I connect Fuzz-Breaker?
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 will need your own credentials: it refuses anonymous clients.
Does Fuzz-Breaker need an API key?
Yes. Every time we knock, Fuzz-Breaker answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Fuzz-Breaker?
It answers our handshake in 90 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.