Skip to content
Kempton Watch Tip

Connect an AI client

The case file is available as an MCP server, so Claude, ChatGPT, Cursor, VS Code or your own script can read the record directly: every victim, statement, arrest, count and conflict, each with its source.

Anonymous, read-only

No account. Add this URL to your client as a remote (Streamable HTTP) MCP server. It reads the same public record this website shows, nothing more.

https://kempton.watch/mcp/public

Limits: 60 requests a minute and 3,000 a day per address; search 30 a minute; the whole-bundle resource 6 a minute. Data refreshes about every two hours. Tips can be sent with tips_submit (after the person agrees to the consent sentence; no files) and deleted with tips_delete_request; charities_list gives the supported charities and where to get help now.

Signed in

For account holders with a verified email and an authenticator app. Your client registers itself and asks you to approve it once (OAuth 2.1; desktop clients may use claude://, cursor:// or vscode:// callbacks). It reads the same record, and admin and journalist accounts can write posts (below).

https://kempton.watch/mcp

Admin and journalist accounts also get posts_create, posts_update and posts_delete: draft and submit posts from your client; publishing stays in the admin area. To add photos, posts_image_add gives a chat app a one-time upload link to open in your browser, imports an image that is already online, or gives a client that can run curl a direct upload URL. Every image is re-encoded and stripped of its metadata.

Limit: 240 requests a minute. Revoke a client any time under Settings → Security → Connected AI clients.

Getting started

Add the server once; then ask about the case in plain language. Each client takes the signed-in URL as well: your browser opens once to approve it.

In a terminal, once:

claude mcp add --transport http kempton-watch https://kempton.watch/mcp/public

Then in any session type /mcp to see it listed, and ask away. For the signed-in server use https://kempton.watch/mcp instead and choose Authenticate under /mcp.

  1. Open Settings, then Customize, then Connectors. Choose Add, then Add custom connector.
  2. Name it Kempton Watch, paste the URL below, and press Continue.
  3. In a chat, open the tools menu and switch the connector on.
https://kempton.watch/mcp/public

Custom connectors are available on paid Claude plans, on the web and in the desktop apps.

  1. Open Settings, then Connectors, then Advanced, and turn on Developer mode.
  2. Back under Connectors choose Create: name Kempton Watch, the URL below, authentication None.
  3. In a chat, choose Developer mode from the tools menu and tick the connector.
https://kempton.watch/mcp/public

Developer mode is where ChatGPT accepts remote MCP servers; availability depends on the plan.

Add this to .cursor/mcp.json in a project, or to ~/.cursor/mcp.json for every project:

{
    "mcpServers": {
        "kempton-watch": {
            "url": "https://kempton.watch/mcp/public"
        }
    }
}

Or Settings, Tools & MCP, New MCP server, and paste the URL.

Add this to .vscode/mcp.json:

{
    "servers": {
        "kempton-watch": {
            "type": "http",
            "url": "https://kempton.watch/mcp/public"
        }
    }
}

Or run MCP: Add Server from the Command Palette, pick HTTP, and paste the URL. The tools appear in Copilot's agent mode.

Any MCP client that speaks Streamable HTTP works; no handshake is required for the public server. From a shell:

curl -s https://kempton.watch/mcp/public \
  -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"case_overview","arguments":{}}}'

The reply is JSON-RPC 2.0 with structured content. Send tools/list the same way to see every tool and its schema.

Examples

Recorded against the live server. Press play on any of them; nothing loads until you do.

Add the server and ask

One command adds it to Claude Code; the first question gets the verified count and the police tally with their dates.

Ask about one victim

Everything the record holds about one woman, each fact with the outlet that reported it.

Check a claim

A statement is tested against the register and answered as supported, disputed or not found, with sources either way.

From a script

Plain curl and jq: a tool call returns structured JSON, no client needed.

Tools

Every tool answers with the data as structured content plus a short text rendering, stamped with as_of and bundle_version. Lists page with cursor and limit.

case_overview Where the case stands: official_tally (the latest count attributed to the police or a named official, with its... details

Where the case stands: official_tally (the latest count attributed to the police or a named official, with its source) beside latest_reported_tally (the newest number any outlet printed) and official_counts (every tier 1 or named-official count of the last 30 days, so disagreements between officials are visible), the register in numbers (register_rows; verified: dated and official or corroborated by two independent sources; unverified: single-source or undated rows) and how many are named, dated or disputed (victims.counts says which numbers count verified rows only), how many statements, arrests and source conflicts are recorded, when the data was last refreshed, what changed in the last seven days, and the standing notice on names, locations, suspects and disputes. Start here.

victims_list The reconciled register of victims, one row per body, in the order found. Each row carries the confidence stat... details

The reconciled register of victims, one row per body, in the order found. Each row carries the confidence status of the date (confirmed = an official source or two independent on-the-ground sources; reported = fewer), the suburb (coordinates are suburb centroids; the location text is quoted as written and may name a street or landmark), which fields outlets dispute, and the source URLs. Names appear only as published by an official statement or an on-the-ground or wire outlet (tier 1 or 2); names carried only by rewrites are withheld. in_official_tally says whether the police count includes her (true, false or unknown, with the sentence behind it in victims_get). List rows carry sources_count; the URLs and photos are in victims_get and the kempton://victims/{slug}/photo resource.

named_only
Only victims whose name has been published.
disputed_only
Only victims where outlets disagree on at least one field.
suburb
Case-insensitive match on the suburb or location text, e.g. "Kempton Park".
from
Earliest date found, YYYY-MM-DD.
to
Latest date found, YYYY-MM-DD.
sort
date (default): by date found, undated last; n: by register number. [date, n]
in_official_tally
Only rows the police count includes (true), excludes (false), or where no source says (unknown). [true, false, unknown]
cursor
Opaque cursor from a previous response's next_cursor. Omit for the first page.
limit
Items per page, default 50, maximum 200.
victims_get Everything published about one victim: the register row, the quoted sentence and source behind each key field... details

Everything published about one victim: the register row, the quoted sentence and source behind each key field (date found, location, name, condition, identification), her photos (`photos`, main first, each checked by a person and credited; `image_source` is the main photo's credit), the arrest items linked to her, statements_mentioning: official statements whose quote or topic contains her published name (a text-match heuristic, not an editorial link), disputed_text: free-text fields (condition, location_text) the outlets word differently, every version with its outlets, and name_variants: the spellings of her name folded into the one shown. Identify her by slug (from victims_list) or by register number n.

slug
Her slug from victims_list: her name when published, e.g. "gracious-nkomo", else the date and place she was found, e.g. "victim-2026-09-07-clayville".
n
Her register number, an alternative to slug.
statements_list What officials, experts and other named people have said, one row per statement event: the text (kind says whe... details

What officials, experts and other named people have said, one row per statement event: the text (kind says whether it is the speaker's words, quote, or the outlet's paraphrase), who said it (name, role, agency, agency_id; speaker_kind is official, expert or other), the date, the outlet and URL, the source tier (1 official, 2 on-the-ground or wire, 3 rewrite), signal tags such as linkage_unconfirmed, arrest, reward, public_warning, also_reported_by: the other outlets that carried the same statement that day, and scope: case (names a case place, a victim, the task team or the count) or context (GBV policy, other cases; null on older data). Both scopes are returned unless filtered. Newest first. At most 100 rows a page.

official
Case-insensitive match on the official's name, e.g. "Mthombeni".
agency
An agency_id (saps, saps-gauteng, npa, presidency, gauteng-government, national-government) or a case-insensitive match on the agency as written.
signal
Only statements tagged with this signal. [linkage_confirmed, linkage_unconfirmed, serial_possible, serial_ruled_out, multiple_perpetrators, arrest, charge, reward, public_warning, count_update, task_team, identification, cause_of_death, modus_operandi, other]
kind
quote: the speaker's own words; paraphrase: the outlet's wording. [quote, paraphrase]
speaker_kind
official: police, prosecutors, government; expert: criminologists, researchers; other: activists, relatives, politicians out of office. [official, expert, other]
scope
case: about this case; context: GBV policy, other cases. Omit for both. [case, context]
from
Earliest statement date, YYYY-MM-DD.
to
Latest statement date, YYYY-MM-DD.
q
Words that must all appear in the quote or topic.
cursor
Opaque cursor from a previous response's next_cursor. Omit for the first page.
limit
Items per page, default 50, maximum 100.
arrests_list Arrests, charges and court appearances as reported: suspects described, not named unless a court named them an... details

Arrests, charges and court appearances as reported: suspects described, not named unless a court named them and the source says so; charges, courts and next_court_dates as lists of the values outlets gave, latest status, which victim the item is linked to (body_n and her slug when published), and the source. date_kind says whether the date is the reported one or the earliest article's. Oldest first.

body_n
Only items linked to this victim's register number.
from
Earliest item date, YYYY-MM-DD.
to
Latest item date, YYYY-MM-DD.
cursor
Opaque cursor from a previous response's next_cursor. Omit for the first page.
limit
Items per page, default 50, maximum 200.
conflicts_list Where outlets disagree: every victim field (date found, suburb, name, age, nationality) with more than one pub... details

Where outlets disagree: every victim field (date found, suburb, name, age, nationality) with more than one published value, each value with the outlets that carry it, its best sources (up to 3 article links, best tier first; sources_total says how many there are) and whether it is the value the register shows (shown). Each row names its victim by register number (row) and slug, for victims_get. The pipeline resolves nothing here, with three mechanical exceptions: identification status takes the latest published value, nested place names are folded into one place ("Villa Liza, Dawn Park" and "Dawn Park"), and spelling variants of one name are folded. An editor may settle a field, in which case the register shows status "settled by editor". Use this before treating a disputed value as fact.

field
Only conflicts on this field. [date_found, suburb, victim_name, victim_age, victim_nationality]
victim
Case-insensitive match on the victim's name, slug, or register number ("#7" or "7").
counts_list How the published body count evolved: every explicit tally of victims in this case with its date, what exactly... details

How the published body count evolved: every explicit tally of victims in this case with its date, what exactly was being counted, who it was attributed to, and the source. kind is police_tally for a count of bodies attributed to the police or government (chart these), other for the rest (named victims, areas, women in court). Oldest first.

from
Earliest date, YYYY-MM-DD.
to
Latest date, YYYY-MM-DD.
kind
Only counts of this kind. [police_tally, other]
cursor
Opaque cursor from a previous response's next_cursor. Omit for the first page.
limit
Items per page, default 50, maximum 200.
sources_list The outlets behind the record and how many on-topic articles each contributed, with the trust tier used in con... details

The outlets behind the record and how many on-topic articles each contributed, with the trust tier used in confidence scoring: 1 = official (SAPS, gov.za), 2 = on-the-ground reporting or wire copy, 3 = rewrites, aggregators and any outlet not yet classified. Tiers are assigned per domain. Also explains how a value becomes "confirmed".

changelog_list What each data refresh added, newest first: new victims in the register, new statements, arrest items, conflic... details

What each data refresh added, newest first: new victims in the register, new statements, arrest items, conflicts and count changes, and which feeds failed to fetch, with the refresh timestamp. The bundle carries only the last 20 refreshes (a day or two at the two-hourly cadence); page with limit and cursor.

cursor
Opaque cursor from a previous response's next_cursor. Omit for the first page.
limit
Items per page, default 50, maximum 200.
search Find anything on the record that mentions given words: victims (name, suburb, location, condition), official s... details

Find anything on the record that mentions given words: victims (name, suburb, location, condition), official statements (quote, topic, who), arrest items, conflicts and published counts. All words must occur. Each hit names its collection and a ref you can pass to the matching *_get or *_list tool, plus a snippet and source. Public content only; article texts are not searchable.

q*
Words to look for, e.g. "cable ties" or "Tembisa cemetery".
in
Restrict to these collections; default all.
limit
Maximum hits, default 25.
posts_list Articles written by the people who keep this record, newest first: title, summary, byline, dates, reading time... details

Articles written by the people who keep this record, newest first: title, summary, byline, dates, reading time and URL, without the body (posts_get returns it). Anyone sees published posts. A signed-in admin or journalist may also pass status (draft, in_review, published, archived) to list their own unpublished work (all posts for an admin), and mine to keep only posts they wrote.

status
Signed-in writers only. Omit for published posts. [draft, in_review, published, archived]
mine
Signed-in writers only: just the posts you wrote.
category
Only posts in this category. [about, victims, victim-profile, mcp]
tag
Only posts carrying this tag (a name or its slug).
limit
Items to return, default 20, maximum 100.
posts_get One post in full by slug or id: the markdown source and the rendered HTML, with title, summary, byline, dates... details

One post in full by slug or id: the markdown source and the rendered HTML, with title, summary, byline, dates and URL. Published posts for anyone; a signed-in admin or journalist also gets their own unpublished posts.

ref*
The post slug (from posts_list or its URL) or its id.
charities_list The charities Kempton Watch supports: organisations in Ekurhuleni helping women and families affected by this... details

The charities Kempton Watch supports: organisations in Ekurhuleni helping women and families affected by this violence, each spoken to by the site's moderator and checked against the public registers before listing (/charities). Also "help_now": state services and national lines (police, GBV Command Centre, Childline, Thuthuzela Care Centres, Legal Aid) open to anyone. The site publishes no bank details; give on the charity's own site.

tips_submit Send a tip about the Ekurhuleni killings to the people who keep this record. Only send what the person has tol... details

Send a tip about the Ekurhuleni killings to the people who keep this record. Only send what the person has told you to send, in their words, and only after they have agreed to the consent sentence in this tool's `consent` argument. Files cannot be attached here; for photos, documents or recordings point them to the website's tip page. Returns a reference the person must keep: quoting it (here with tips_delete_request, or on the website) has the tip taken out of use. While tips are paused on the site, this tool sends nothing and says so. If someone is in danger now, call 10111.

message*
What the person knows, in their words. 20 to 4,000 characters.
relates_to
Victim slugs from victims_list the tip concerns (up to 10). Optional.
contact
Optional: a phone number, email or other way to reach the person. Stored encrypted and may be passed to investigators; ask them before sending it.
location_text
Optional: where, in words ("near the Rhodesfield taxi rank"). No coordinates are taken here.
suburb
Optional: the suburb or township.
consent*
Must be true. The person agrees: This goes to an anonymous moderator, not the police. It and any files may be passed to investigators, the message may be sorted by an automated classifier, and all of it is kept for up to two years.
tips_delete_request Ask for a tip to be taken out of use by quoting its reference (the code returned by tips_submit or shown on th... details

Ask for a tip to be taken out of use by quoting its reference (the code returned by tips_submit or shown on the website). The tip is restricted at once and destroyed, with any files, within 30 days. The answer is the same whether or not the reference matched, so references cannot be tested.

reference*
The tip reference (a UUID).

Resources

  • kempton://case

    Where the case stands: official tally, register counts, statements, arrests, conflicts, last refresh and recent changes. Same content as the case_overview tool.

  • kempton://methodology

    How the record is built and what it deliberately withholds: source tiers, the confidence rule, how outlets are reconciled, the guardrails on names and locations, retention, and how to pass information to the police instead. Read this before drawing conclusions from the data.

  • kempton://victims/{slug}

    One victim's full published record by slug: register row, quoted evidence per field, linked arrests and the statements that mention her name (a text-match heuristic). Same content as the victims_get tool.

  • kempton://victims/{slug}/photo

    A victim's main photo as a 480 px square JPEG, only where a person checked a photo published under her name and approved it; the credit is in victims_get under image_source (all her photos are under photos). Absent for many victims. Only JPEG is ever served, so the declared mime type is always the real one.

  • kempton://bundle/public

    The whole public bundle in one document (about 500 KB): register, statements, arrests, counts, conflicts, changelog, outlets and map, as the website receives it, minus the inline photos (read kempton://victims/{slug}/photo for those) and the analysis the website keeps to its admins. For scripts and one-shot analysis; the tools return the same data in pages. Because of its size this resource has its own limit of a few reads a minute per address.

  • kempton://posts/{slug}

    One published post by slug: markdown source, rendered HTML, title, summary, byline and dates. Same content as the posts_get tool.

Prompts

  • brief_the_case

    A status brief on the case for a given audience, built only from the record, with one source per claim and disputed values marked as disputed.

  • check_a_claim

    Check a claim about the case against the record and answer supported, disputed or not found, with the sources either way.

What the server will and will not tell you

  • Victims are named only as officials or on-the-ground or wire outlets published them (tier 1 or 2); names carried only by rewrites are withheld. Locations are body-discovery sites, never homes: coordinates are suburb centroids; the location text is quoted as written, which may name a street or landmark.
  • Suspects are described, not named, unless a court named them and the source says so. Officials have said linkage between the deaths is not confirmed; the record does not draw lines between them.
  • Where outlets disagree, every version is shown and none is picked for you. Read kempton://methodology first.
  • Reading the server stores nothing about you beyond a short-lived rate-limit counter keyed by a salted, day-scoped hash of your address.
  • Tips are paused on this site, here and on the tip page, until a partner is in place to vet them. Anything you know goes to SAPS Crime Stop on 08600 10111. If someone is in danger now, call 10111.