Skip to content

Add Who Got Hacked MCP server - #790

Open
joefulfill wants to merge 2 commits into
Kilo-Org:mainfrom
joefulfill:add-whogothacked-mcp
Open

joefulfill wants to merge 2 commits into
Kilo-Org:mainfrom
joefulfill:add-whogothacked-mcp

Conversation

@joefulfill

Copy link
Copy Markdown

Adds mcps/whogothacked/MCP.yaml: a remote, read-only MCP server for data breach records.

What it does: every incident links to its source record: a US state attorney general or HHS breach notice, an SEC Form 8-K Item 1.05 filing, or Have I Been Pwned. There are six read-only tools:

  • search_breaches
  • check_organization
  • get_organization
  • get_incident
  • recent_breaches
  • about_data

In Kilo it is useful for vendor and dependency risk checks, security reviews and incident research.

Category: search (information retrieval). The entry offers one installation option, because the server is hosted and has nothing to install.

Disclosure: I run whogothacked.com.

Comment thread mcps/whogothacked/MCP.yaml Outdated
@@ -0,0 +1,13 @@
id: whogothacked
name: Who Got Hacked
description: Data breach records at companies and organizations, each linked to its source (a US state attorney general or HHS breach notice, an SEC Form 8-K Item 1.05 filing, or Have I Been Pwned). Six read-only tools search organizations, check a domain or name, open an organization's or incident's record, and list recent incidents. No account or API key.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: Tool count does not match the capabilities listed

The description says "Six read-only tools" but then enumerates five actions: search organizations, check a domain or name, open an organization's record, open an incident's record, and list recent incidents. The sixth tool from the PR description (about_data) is not implied by any clause, so the listing copy reads as a mismatch.

Minimal fix: name the sixth capability, for example "...list recent incidents, and describe the dataset". This is the primary user-facing field in the generated catalog, so accuracy here matters more than elsewhere.

name: Who Got Hacked
description: Data breach records at companies and organizations, each linked to its source (a US state attorney general or HHS breach notice, an SEC Form 8-K Item 1.05 filing, or Have I Been Pwned). Six read-only tools search organizations, check a domain or name, open an organization's or incident's record, and list recent incidents. No account or API key.
author: Who Got Hacked
url: https://whogothacked.com/developers

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: url should reference the server's source repository

CONTRIBUTING.md documents url as "Link to the MCP server repository", and most listings point at the upstream repo or vendor docs for a service with no public source. This PR states the config repository is https://github.com/whogothacked/mcp, but the entry links only the marketing docs page, so there is no inspectable provenance for a remote server that receives every query an agent sends to it.

Minimal fix: use url: https://github.com/whogothacked/mcp (the docs page can stay reachable from the README of that repo), or note the repository in prerequisites. Docs links do appear in existing entries, so this is not a blocker.

@kilo-code-bot

kilo-code-bot Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Verification notes (click to expand)
  • Incremental review at cd28703 covers only the one-line description change in mcps/whogothacked/MCP.yaml; the rest of the entry is unchanged since 7717a53 and was reviewed there.
  • Previous finding 1 (six tools claimed, five capabilities listed) is fixed. The description now names the sixth capability, so all six PR-declared tools map to a clause: search_breaches (search organizations), check_organization (check a domain or name), get_organization and get_incident (open a record), recent_breaches (list recent incidents), about_data (describe the sources and last update times).
  • Previous finding 2 (url points at the docs page, not the config repository) is withdrawn. CONTRIBUTING.md describes url as the server repository, but the author states the server is hosted with no public source and https://github.com/whogothacked/mcp holds client configuration only. Hosted entries such as mcps/agent-platform-mcp also link vendor docs. This is a maintainer preference, not a defect.
  • The new line is a valid YAML plain scalar (no : sequence), single-line like other entries, and its ~437-character length is within existing precedent (mcps/laravel-boost ~300, mcps/openapi-mcp ~250). bin/generate-mcps-marketplace.ts enforces only required-string presence and the documented category set, with no description length cap.
  • Unchanged entry checks still hold: id matches the directory, category: search is valid, the content block uses the documented streamable-http remote form with no parameters or secrets, and mcps/marketplace.yaml is regenerated by .github/workflows/generate-marketplace.yml (pnpm exec tsx generate-mcps-marketplace.ts), so its absence from this PR is expected.
  • Unverified: the endpoint https://whogothacked.com/mcp, the docs page, and the six tool names could not be reached from the review sandbox because network access is blocked. Maintainer check: connect the entry in a Kilo client, or run curl -s -X POST https://whogothacked.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}', and confirm six read-only tools with no authentication.
Files Reviewed (1 file)
  • mcps/whogothacked/MCP.yaml
Previous Review Summary (commit 7717a53)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 7717a53)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 2
Issue Details (click to expand)

SUGGESTION

File Line Issue
mcps/whogothacked/MCP.yaml 3 Description claims "Six read-only tools" but enumerates only five capabilities; about_data is unrepresented.
mcps/whogothacked/MCP.yaml 5 url points at the marketing docs page, not the config repository named in the PR (https://github.com/whogothacked/mcp), so the listing has no inspectable provenance.

Verification notes

  • id whogothacked is unique across mcps/ and matches the directory name; category search is a valid marketplace category.
  • The content entry uses the documented remote form ("type": "streamable-http" with a url), matches the CONTRIBUTING.md remote example, and needs no parameters because the server takes no auth or config.
  • Adding only MCP.yaml without mcps/marketplace.yaml matches precedent (e.g. fe5abc7 for mcps/transform-mcp); the Generate Marketplace workflow regenerates and commits the catalog, and bin/generate-mcps-marketplace.ts accepts this entry (required fields present, valid category, no tags).
  • Unverified: the endpoint https://whogothacked.com/mcp and docs page could not be reached from the review sandbox (network access is blocked), so reachability, auth-free behavior, and the six advertised tool names are unconfirmed. Maintainer check: connect the entry in a Kilo client and confirm tools/list returns the six documented tools.
Files Reviewed (1 file)
  • mcps/whogothacked/MCP.yaml - 2 suggestions

Fix these issues in Kilo Cloud


Reviewed by deepseek-v4.1-flash-1017 · Input: 50.2K · Output: 10.8K · Cached: 878.1K

Review guidance: REVIEW.md from base branch main

@joefulfill

Copy link
Copy Markdown
Author

Thanks. On the two suggestions:

  1. Six tools: fixed. The description now names the sixth one (it describes the sources and when each was last updated).
  2. url: I've kept the docs page on purpose. The server is hosted and its source isn't public. whogothacked/mcp holds only client configuration, so it gives no more provenance than the docs. Those docs carry the tool list, the terms and the rate limits. mcps/agent-platform-mcp does the same with a hosted server, pointing url at the vendor's docs. If maintainers prefer the config repo, I'm glad to switch it.

You can check it with: curl -s -X POST https://whogothacked.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}', which returns the six tools.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant