MCP.Market

Police Shootings MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/police-shootings·v0.2.1

Police Shootings MCP — The Washington Post, Fatal Force database

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Police Shootings yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Police Shootings tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Police Shootings compares

Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 40% of 802 Databases servers
Uptime
100%
of our recent checks; the typical remote Databases server answers 100%
Response time
59 ms
faster than 94% of 292 Databases servers

Release history: 3 versions in the registry since 2026-10-13, latest 2026-11-04, typically one every 15 days.

Install Police Shootings in Claude Code, Cursor or VS Code

claude mcp add --transport http police-shootings https://gateway.pipeworx.io/police-shootings/mcp
Add to Cursor

What the publisher says

From the Police Shootings repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/police-shootings

U.S. fatal police shootings since 2015 — aggregate counts, individual incident records (including the name of the person killed, as published), and per-agency breakdowns, proxied live from The Washington Post's Fatal Force database.

Part of Pipeworx — an MCP gateway connecting AI agents to 1784+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

(by state, year, race, armedwith, threattype, gender, mentalillness, or bodycamera). Never returns names.

  • policeshootingssummary(group_by?, state?, year?) — aggregate counts

— individual incident records, including the name of the person killed. Small by default (limit 25, max 200); a truncated response carries truncated:true, total_matching, and a narrowing hint.

  • policeshootings(state?, city?, year?, armedwith?, race?, limit?, offset?)

fatal-shooting count and breakdown by year/race/armed_with. Matches on a name fragment; returns a small list of candidates when more than one agency matches, rather than guessing.

  • agency_shootings(agency, state?) — one law-enforcement agency's

Auth

Keyless. The upstream is a public CSV with no registration, key, or login.

Data sources

police officers in the United States since Jan. 1, 2015, plus the roster of law-enforcement agencies involved. Published under Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0); every tool response carries license and attribution fields so the terms travel with the data. This pack is a LIVE PROXY — it fetches the Post's published files fresh on every cache miss (6h edge cache, same as any normal client would cache) and never commits the dataset into this repo (CLAUDE.md "mirror-needs-grant-proxy-does-not": a per-request proxy call is not redistribution; bulk-copying the dataset would be, and the licence forbids that). Human-facing page: . Routes live only in src/index.ts.

  • The Washington Post, Fatal Force database — fatal shootings by on-duty

Notes

published file this pack reads currently ends 2024-12-31 (verified live 2026-10-13) — there is no newer data to proxy. Every response's dataasof / datasetcoverage.maxdate reflects whatever the Post has actually published at call time, not a fixed claim.

  • The Post's own README states the data is "updated regularly," but the

Brown case — not deaths in custody, off-duty shootings, or non-shooting deaths. It is not comprehensive beyond that scope (the Post itself notes undercounting is possible before reporting catches up).

  • The Post tracks only on-duty police shootings paralleling the Michael

semicolon-separated in the source (e.g. "W;B", "gun;knife"). The race and armedwith filters in policeshootings/policeshootingssummary match if the requested value is ANY one of the semicolon-separated tokens.

  • race and armed_with can carry more than one value per incident,

(semicolon-separated) when multiple departments were involved; agency_shootings joins on that list.

  • agency_ids on an incident can list more than one agency

publishes them — nothing is added, inferred, or joined against any other people-data source.

  • Names, ages, and other person-level fields are served exactly as the Post

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "police-shootings": {
      "url": "https://gateway.pipeworx.io/police-shootings/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Police Shootings: common questions

Is Police Shootings MCP server safe?
Mostly: it is graded B (77/100). Read the Police Shootings safety report
How do I install Police Shootings?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Police Shootings need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Police Shootings maintained?
The last commit was 21 days ago (2026-10-13). The latest release is v0.2.1.
Is Police Shootings up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Police Shootings?
Servers from other publishers that do the same job: CogniCore MCP server, DBHub MCP server and Neo4j Cypher MCP server.
How does Police Shootings compare with other Databases MCP servers?
safety score 77/100 (higher than 40% of 802 Databases servers); uptime 100% (of our recent checks; the typical remote Databases server answers 100%); response time 59 ms (faster than 94% of 292 Databases servers). Full comparison.

Alternatives to Police Shootings

Same job from other publishers: the closest match first, then the best rated.

  • CogniCore
    Memory, reflection and safety for AI agents. Hosted or local, no vector database.
    A
  • DBHub
    Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite
    A
  • Neo4j Cypher
    A simple Neo4j MCP server that allows you to run Cypher queries against a Neo4j database.
    A
  • Appwrite
    Build and deploy backends: auth, Postgres/MySQL/vector databases, storage, functions, hosting, CDN
    A
  • Airtable
    Read and write access to Airtable database schemas, tables, and records.
    B

More from pipeworx-io →