_ registry / mcp streamable-http · checked 19h ago

whogothacked

https://whogothacked.com

Registry code: c69cfa853b693786

api record

Using this server means accepting the terms: https://whogothacked.com/terms (reference: https://whogothacked.com/developers). Each IP address can make 120 requests a minute to the JSON API and, counted separately, 300 to the MCP server. Over that, the answer is HTTP 429 Too Many Requests: wait 60 seconds before trying again. whogothacked.com is a public record of data breaches at companies and organizations, each verified against a source record a reader can open. Use search_breaches or check_organization to find an organization, then get_organization or get_incident for detail;…

endpoint
https://whogothacked.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is whogothacked live?
Yes — it answered the hub's last check (checked 19h ago). It answered 100% of checks over the last 30 days.
Is whogothacked free to use?
Yes — the hub reached it with no key and no payment.
What tools does whogothacked have?
6 tools: check_organization, get_organization, search_breaches, get_incident, recent_breaches, about_data.
Is whogothacked safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
257ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
2 open 4 never probed 2 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • recent_breaches open 19h ago

    Incidents newest first by the date they were first on record, optionally within a date range. That date is a filing's date, or the day Have I Been Pwned added an entry to its catalog, and each incident's firstDateKind says which; it is not when the breach happened. Records are verified from regulator filings and Have I Been Pwned; a threat actor's claim is never a source. A miss means there is no record here, not that no breach happened. Counts from different sources are not additive.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 100,
          "minimum": 1,
          "description": "1 to 100, default 25."
        },
        "since": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "YYYY-MM-DD, inclusive."
        },
        "until": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "YYYY-MM-DD, inclusive."
        }
      }
    }
    arguments 23 lines
  • about_data open 19h ago

    How whogothacked.com verifies records, which sources it reads, how many records it holds and when each source was last read: the data's coverage and freshness. Records are verified from regulator filings and Have I Been Pwned; a threat actor's claim is never a source. A miss means there is no record here, not that no breach happened. Counts from different sources are not additive.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • check_organization unknown 19h ago

    Answers 'is there anything on record for this organization: a breach notice, an 8-K disclosure or a catalog entry?' from a domain or a name. At least one is required; a domain is tried first. found is true only for an exact domain or an exact name (case, punctuation and legal forms such as Inc. are ignored), and then every incident and its sources are returned. A parent domain or a similar name is never treated as the answer: those organizations are listed under candidates. Records are verified from regulator filings and Have I Been Pwned; a threat actor's claim is never a source. A miss means there is no record here, not that no breach happened. Counts from different sources are not additive.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 300,
          "minLength": 2,
          "description": "An organization name. This or `domain` is required."
        },
        "domain": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "A domain such as example.com. This or `name` is required."
        }
      }
    }
    arguments 18 lines
  • get_organization unknown never probed

    Full record for one organization by slug (as this server's results give it): every incident with its tier, dates, figures, data exposed, summary and the source records behind it. A California source record can carry `noticeLetter`, a passage quoted from its notice letter, with a credit line. A slug can be retired, for example when its organization is merged into another, or replaced after a rollback; a retired slug returns the current organization, with redirectedFrom naming the slug asked for. A slug that named a person who is not the organization (for example, an officer named in the filer's name) is withdrawn, not retired: it is not found (the API answers 404, with no redirect), and its organization goes on under another slug. Records are verified from regulator filings and Have I Been Pwned; a threat actor's claim is never a source. A miss means there is no record here, not that no breach happened. Counts from different sources are not additive.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Organization slug, as this server's results give it."
        }
      }
    }
    arguments 15 lines
  • search_breaches unknown never probed

    Searches whogothacked.com's record for organizations by name or domain. Returns each match with its slug, incident count, the date its latest incident was first on record, the tier of that incident and source links. Records are verified from regulator filings and Have I Been Pwned; a threat actor's claim is never a source. A miss means there is no record here, not that no breach happened. Counts from different sources are not additive.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "1 to 50, default 10."
        },
        "query": {
          "type": "string",
          "maxLength": 300,
          "minLength": 2,
          "description": "Organization name or domain."
        }
      }
    }
    arguments 22 lines
  • get_incident unknown never probed

    One incident by id (as this server's results give it) with its tier, dates, figures, summary and the source records that establish it. A California source record can carry `noticeLetter`, a passage quoted from its notice letter, with a credit line. An id can be retired, for example when its incident is merged into another, re-minted under its own organization, or replaced after a rollback; a retired id returns the current incident, with redirectedFrom naming the id asked for. An incident id made from a slug that named a person who is not the organization (for example, an officer named in the filer's name) is withdrawn, not retired: it is not found (the API answers 404, with no redirect), and its incident goes on under another id. Records are verified from regulator filings and Have I Been Pwned; a threat actor's claim is never a source. A miss means there is no record here, not that no breach happened. Counts from different sources are not additive.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "maxLength": 320,
          "minLength": 1,
          "description": "Incident id."
        }
      }
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c69cfa853b693786.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c69cfa853b693786/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c69cfa853b693786/badge.svg)](https://brick.blue/agent/c69cfa853b693786?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.