Police Transparency MCP server

by mrfentmen·io.github.mrfentmen/police-transparency-mcp·v1.0.0

No reviews yet

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

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

New

0 stars

Reviews

Write one

Nobody has reviewed Police Transparency yet.

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

Police Transparency tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

summarize_complaints
Return aggregate historical NYPD complaint counts grouped by borough, broad law category, or offense description. No names, addresses, coordinates, demographics, incident rows, live dispatch, or person lookup are exposed.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings

Code scan8 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 85 days ago12/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Police Transparency compares

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

Safety score: 85/100; higher than 70% of 48,255 servers
Tools: 1; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 1 read

Install Police Transparency in Claude Code, Cursor or VS Code

Runs npx -y police-transparency-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add police-transparency-mcp -- npx -y police-transparency-mcp

Add to Cursor

What the publisher says

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

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

npm install
npm run build
node dist/index.js

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

Police Transparency: common questions

Is Police Transparency MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the Police Transparency safety report
How do I install Police Transparency?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Police Transparency need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Police Transparency maintained?: The last commit was 87 days ago (2026-08-08). The latest release is v1.0.0.
How does Police Transparency compare with other MCP servers?: safety score 85/100 (higher than 70% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.