mcpbeat Sign in

pwned.coffee MCP Server

answering

pwned.coffee is answering right now. Last checked 13 min ago. It exposes 6 tools.

Live security incidents, updated hourly: fix status, fixed versions, lockfile and repo checks.

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
302 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check pwned.coffee 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 13 min ago.

run in your terminal
claude mcp add pwned-coffee --transport http https://pwned.coffee/mcp
Settings → Connectors → Add custom connector, then paste this address
https://pwned.coffee/mcp
~/.codex/config.toml
[mcp_servers.pwned-coffee]
url = "https://pwned.coffee/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "pwned-coffee": {
      "url": "https://pwned.coffee/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "pwned-coffee": {
      "type": "http",
      "url": "https://pwned.coffee/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

diff
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".
lockfile
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, go.sum, go.mod, Cargo.lock, Gemfile.lock, a Dockerfile, an .nvmrc / .node-version ("node") or a GitHub Actions workflow ("actions"). For several files at once, use check_repo.
lookup
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.
repo
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 to check, and live incidents for the detected stack that the files cannot rule out.
todays
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, dotnet, rust, npm, pypi, github-actions, docker, vscode, browser-ext, linux, linux-services, openssh, nginx, apache, kubernetes, postgres, mysql, redis, gitlab, ci, atlassian, self-hosted, selfhost-apps, paas, cloudflare, aws, gcp, azure, vps, databases-cloud, ai-gateways, ai-keys, ml-infra, mcp, chrome, apple, android, windows, office, password-managers, messaging, crypto-wallets, vpn-edge, ics, remote-support, vmware, security-tools, health-it, erp.
whats
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.

Endpoints

URLTransportStateLatencyChecked
https://pwned.coffee/mcp streamable-http answering 147 ms 13 min ago

Alternatives to pwned.coffee

same job, measured the same way
YoPingMe uptime monitoring
by yoping

Website uptime monitoring: live status, uptime reports, incidents, response times, failed checks

answering
Penthera
by danoszz

Offline, rule-based security checks for your repo, dependencies, AI agent config and local app.

1 877 installs/wk local only
SutramX
by sutramx

SutramX uptime monitoring: monitors, check results, incidents, status pages and uptime/SLO reports.

56 installs/wk local only
ProdForge
by cloudcorprecords

Connects MCP servers, packages, security checks, and release gates in one repo.

59 installs/wk local only
mcpprobe
by mcpprobe

Read-only MCP security data: check catalogue, public scan status and your own scan reports.

answering
T
Traceproof
by raised-traceproof

Search security findings and contribute versioned, evidence-backed reproduction reports.

answering
HTTP Inspector MCP
by mrfentmen

Fetch a URL and report its status, headers, and size. Runs locally.

54 installs/wk local only
Security Headers Csp Lint
by jmshinhwa

Reads security headers and CSP line by line in your config file and names the lines that silently do

134 installs/wk local only

pwned.coffee — questions

Answers built from our own checks of this server.

What can pwned.coffee do?
It exposes 6 tools, read directly from the server on our last check. Among them: check_lockfile, check_repo, diff_since, lookup_cve, todays_specials, whats_new. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is pwned.coffee 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 302 ms. The bar chart above shows every period we have measured.
How do I connect pwned.coffee?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does pwned.coffee need an API key?
No. pwned.coffee completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is pwned.coffee?
It answers our handshake in 302 ms on average, which is faster than 47% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.