pwned.coffee
coffee.pwned/pwned-coffeepwned.coffeestreamable-httpv1.0.0Scanned
Live security incidents, updated hourly: fix status, fixed versions, lockfile and repo checks.
6 tools: 1 do something that can't be undone, 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- 1 finding
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Can't be undone 1Claude Code: ask
check_repoSend the files that describe what a project runs (lockfiles, Dockerfiles, .github/workflows/*.yml, wrangler.toml, vercel.json, next.config.*, compose files) in one call.Can send data out1 finding
Why it is in this group
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe description's first verb is "send": it sends or publishes something to other people.
Findings
- Warn
The server marks "check_repo" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Changes things 3Claude Code: ask
check_lockfileMatch 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
todays_specialsLive security incidents right now (CVEs, breaches, supply-chain compromises) with severity, patch status, fixed versions and ids.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
whats_newIncidents created or updated since a point in time, newest first.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
diff_sinceEvery correction, new ticket and fix-status change since a point in time, each with the source behind it (the same log as /corrections).Reads text others writeNo findings
Why it is in this group
- The name "diff_since" says "diff": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
Description, as the server wrote it 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".
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
lookup_cveThe incident covering a CVE or GHSA id, or a named bug (e.g.No findings
Why it is in this group
- The name "lookup_cve" says "lookup": a word for reading.
Description, as the server wrote it The incident covering a CVE or GHSA id, or a named bug (e.g. HTTP2Shell): summary, severity, patch status, fixed versions, timeline and sources.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_repo
The server marks "check_repo" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http pwned-coffee https://pwned.coffee/mcpclaude mcp add --transport http pwned-coffee https://pwned.coffee/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pwned-coffee__lookup_cve",
"mcp__pwned-coffee__diff_since"
],
"ask": [
"mcp__pwned-coffee__todays_specials",
"mcp__pwned-coffee__check_lockfile",
"mcp__pwned-coffee__check_repo",
"mcp__pwned-coffee__whats_new"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pwned-coffee. Review it before you use it.
Capability tags behind 2 rules
- mcp__pwned-coffee__check_repo outbound
- mcp__pwned-coffee__diff_since untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/coffee.pwned/pwned-coffee/verify?hash=8e4cb94994003ddfbfad7d0ed6e84a94fbdee37bbb2b360573c24738ee551ca4" | jq -e '.changed == false'Pinned hash 8e4cb9499400, from Nov 2, 2026, 16:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/coffee.pwned/pwned-coffee/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/coffee.pwned/pwned-coffee)Source: MCP Registry. Synced Nov 2, 2026, 16:17 UTC.