# pwned.coffee (remote · pwned.coffee)

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

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `pwned.coffee`: 65/100 (this document), [markdown](https://verifymcp.io/servers/coffee-pwned-pwned-coffee/pwned.md), [page](https://verifymcp.io/servers/coffee-pwned-pwned-coffee/pwned)

## Channel facts

- Endpoint: `https://pwned.coffee/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 879 tokens (~146/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_repo" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the pwned.coffee MCP server?

pwned.coffee is a hosted endpoint at https://pwned.coffee/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "coffee-pwned-pwned-coffee": {
      "url": "https://pwned.coffee/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "coffee-pwned-pwned-coffee": {
      "type": "http",
      "url": "https://pwned.coffee/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.coffee-pwned-pwned-coffee]
url = "https://pwned.coffee/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "coffee-pwned-pwned-coffee": {
      "type": "remote",
      "url": "https://pwned.coffee/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add coffee-pwned-pwned-coffee --url 'https://pwned.coffee/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  coffee-pwned-pwned-coffee:
    url: "https://pwned.coffee/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "coffee-pwned-pwned-coffee": {
      "Transport": "http",
      "Url": "https://pwned.coffee/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add coffee-pwned-pwned-coffee -t streamable-http -u 'https://pwned.coffee/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 64)

First indexed and scored.

## MCP tools (6)

### `todays_specials` (~243 tokens)

Today's 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.

Input parameters:

- `stack` (array): Stack ids to filter by, e.g. ["nextjs","npm"]. Omit for everything.

### `lookup_cve` (~77 tokens)

Look up a 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.

Input parameters:

- `id` (string, required): e.g. CVE-2026-12345, GHSA-xxxx-xxxx-xxxx or HTTP2Shell

### `check_lockfile` (~181 tokens)

Check a 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.

Input parameters:

- `content` (string, required): The lockfile text, as-is.
- `ecosystem` (string): Which reader to use. "auto" detects from the content. "node" is an .nvmrc or .node-version file, "actions" a GitHub Actions workflow.

### `check_repo` (~117 tokens)

Check a whole 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.

Input parameters:

- `files` (array, required): Up to 40 files. Paths matter: they pick the reader and the fix command.

### `whats_new` (~101 tokens)

What's new since

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.

Input parameters:

- `since` (string, required): "24h", "7d", or an ISO timestamp like 2026-10-23T08:00:00Z
- `stack` (array): Optional stack ids to filter by.

### `diff_since` (~124 tokens)

What changed since, with sources

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".

Input parameters:

- `since` (string, required): An ISO 8601 timestamp like 2026-10-24T00:00:00Z, or "24h", "7d"
- `stack` (array): Optional stack ids to filter by.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/coffee-pwned-pwned-coffee/pwned#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64

## Common questions

### What is the pwned.coffee MCP server?

pwned.coffee is an MCP server listed in the public MCP registry as coffee.pwned/pwned-coffee. Live security incidents, updated hourly: fix status, fixed versions, lockfile and repo checks. This page covers its hosted endpoint (https://pwned.coffee/mcp).

### Is the pwned.coffee MCP server safe to use?

pwned.coffee scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the pwned.coffee MCP server expose?

pwned.coffee exposes 6 tools: todays_specials, lookup_cve, check_lockfile, check_repo, whats_new, diff_since. Their descriptions and schemas cost roughly 843 tokens of context every time the server is loaded.

### Does the pwned.coffee MCP server require authentication?

No. We connected to pwned.coffee without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the pwned.coffee MCP server still maintained?

pwned.coffee is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the pwned.coffee MCP server?

VerifyMCP ran 12 checks on pwned.coffee, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about pwned.coffee: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://pwned.coffee/mcp
- Website: https://pwned.coffee/mcp
- Changelog RSS feed: https://verifymcp.io/servers/coffee-pwned-pwned-coffee/pwned.xml
- Changelog JSON feed: https://verifymcp.io/servers/coffee-pwned-pwned-coffee/pwned/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/coffee-pwned-pwned-coffee/pwned.json
- HTML version of this page: https://verifymcp.io/servers/coffee-pwned-pwned-coffee/pwned