Police Transparency Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Nov 5, 2026

Use this MCP server to Aggregate historical NYC police complaint statistics with no person...

VerifiedSTDIODesktop onlyKnowledge & MemoryData & Analytics

Overview

AI-generated overview

A narrow local MCP server that lets an assistant count historical NYPD complaint statistics by borough, law category, or offense, with optional year and…

What you can do
  • Summarize complaints: count historical NYPD complaint records grouped by borough, broad law category, or offense description, optionally filtered by year and borough.
  • Aggregate-only output: results are grouped counts, with groups under five records suppressed.
  • No person-level data: no names, addresses, coordinates, demographics, incident rows, or person lookup.
When to use it
For journalism, civic research, and year-over-year trend exploration of aggregate NYC police complaint statistics. Not intended for operational policing or for inferring anything about an individual.
Requirements
Runs as a local process over stdio; install the npm package and build it, then start the compiled entry point with Node.js. No authentication, environment variables, or headers are declared.
Before you install
The data is historical and reported, with known limitations and possible classification or reporting bias, so figures should be read with that in mind. It must not be used to infer individual behavior or to make decisions about a person. It only returns aggregates and suppresses small groups.

Installation

In SourceWeft

  1. Open Police Transparency Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

police-transparency-mcp

A deliberately narrow public-data server for aggregate historical NYC police complaint statistics. It is intended for journalism, civic research, and year-over-year trend exploration, not operational policing.

Tool

  • summarize_complaints: count historic NYPD complaints grouped by borough, broad law category, or offense description, with an optional year and borough filter.

The server does not expose names, addresses, coordinates, demographics, incident rows, live dispatch, surveillance, targeting, person lookup, or operational controls. Aggregate groups with fewer than five records are suppressed. NYPD complaint data is historical, reported data with known limitations and potential classification or reporting bias. It should not be used to infer individual behavior or make decisions about a person.

Run

bash
npm installnpm run buildnode dist/index.js

Source: README.md at commit 9aae791

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.