Live security incidents, brewed hourly MCP server

Which MCP servers are Live security incidents, brewed hourly's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-02

← Back to Live security incidents, brewed hourly

Whose server it is

Registry namecoffee.pwned/pwned-coffeeverified in the MCP registry

The registry name sits under pwned.coffee. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-02

Stateanswerschecked 2026-11-02
Tools6
Server calls itselfpwned.coffee
Server version1.0.0
Protocol version2025-06-18

On 2026-11-02 the server answered initialize and tools/list without a sign-in. First answer in 94 ms.

Should an agent connect itNot proven either way yet

Its tools do every use case we checked: filter known exploited vulnerabilities down to software you run; check whether a fix or mitigation exists for each flaw; prioritise patching by severity and known-exploitation status.
Checked on 3 of the 7 days it takes to judge reliability.

Once connected

For "filter known exploited vulnerabilities down to software you run", the likely first call is todays_specials.
For "prioritise patching by severity and known-exploitation status", the likely first call is todays_specials.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-11-02

INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
What an agent can do with it3 of 3 use cases
Answeredmeasuring3 of the 7 daily checks it takes to print a share
Median first answer293 ms
Space in an agent's context≈ 1,175 tokensthe definitions of all its tools (6), which an agent carries on every turn
Tool definitionsA · 100 of 100
Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

Every tool passes all six checks.

What an agent can do with it

can do · filter known exploited vulnerabilities down to software you run
can do · check whether a fix or mitigation exists for each flaw
can do · prioritise patching by severity and known-exploitation status

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-11-02

todays_specials
Live security incidents right now (CVEs, breaches, supply-chain compromises) with severity, patch status, fixed versions and ids. Pass stack ids to see only what touches your stack. Known ids: nextjs, react, node, bun, php, python, ruby…
lookup_cve
The incident covering a CVE or GHSA id, or a named bug (e.g. HTTP2Shell): summary, severity, patch status, fixed versions, timeline and sources.
check_lockfile
Match the packages and versions in a lockfile against incidents that state fixed versions, and print a receipt: what you use, the version, affected or not, and the exact upgrade. Accepts package-lock.json, yarn.lock, pnpm-lock.yaml…
check_repo
Send the files that describe what a project runs (lockfiles, Dockerfiles, .github/workflows/*.yml, wrangler.toml, vercel.json, next.config.*, compose files) in one call. Returns one receipt: every affected package with the exact command…
whats_new
Incidents created or updated since a point in time, newest first. Use it to re-check only what changed since your last run. Accepts "24h", "7d", "90m" or an ISO timestamp.
diff_since
Every correction, new ticket and fix-status change since a point in time, each with the source behind it (the same log as /corrections). Use it to audit what the board changed since your last run. Accepts an ISO 8601 timestamp, or "24h"…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "pwned-coffee": {
      "type": "http",
      "url": "https://pwned.coffee/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http pwned https://pwned.coffee/mcp

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://pwned.coffee/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.