coffee.pwned/pwned-coffee · v1.0.0 · developer-tools
pwned.coffee is healthy: it completed an MCP handshake in 2463 ms and exposes 6 tools.
Live security incidents, updated hourly: fix status, fixed versions, lockfile and repo checks.
Endpoint: https://pwned.coffee/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 6 |
| Latency | 2463 ms |
| Last checked (UTC) | 2026-11-02T20:05:26.688Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-02T20:05:26.688Z | Healthy | 2463 |
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, go, java, wordpress, drupal, magento, perl, proof-tools, dotne |
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, requirements.txt, poetry.lock, uv.lock, Pipfile.lock, composer.lock |
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 to fix it in the tool the repo already uses, actions and images |
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", "7d", "90m". |