Data Dc logo

Data Dc

Query Washington, DC open-data layers through ArcGIS REST tools for recent records, discovery, and filtered results.

Install Data Dc

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "data-dc": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-data-dc"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

Data Dc MCP server exposes Washington, DC open data from opendata.dc.gov through ArcGIS REST queries. Use friendly dataset names to retrieve recent crime, 311 service-request, and building-permit records, or discover and query other layers directly. It works through a hosted streamable HTTP endpoint or an npm-based local stdio bridge, with optional Pipeworx authentication. Reach for it when an agent needs structured DC public data rather than web-search results.

Use cases

  • Retrieve recent DC crime records
  • Filter Washington, DC 311 requests
  • Review recent building permits
  • Discover ArcGIS layers for a DC service
  • Query selected DC layers with field and sort controls

Key features

  • Recent crime, 311, and permit lookups
  • Washington, DC ArcGIS layer discovery
  • Filtered queries with where expressions
  • Selectable fields, ordering, and result limits
  • ISO conversion for ArcGIS epoch dates
  • Hosted HTTP and local stdio access

Tools3

What Data Dc lets your agent do. Expand a tool for its parameters.

Verified live~537 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

11/11 checks healthy over the last 62d

What it can do

From the 3 tools this server returned when we ran it.

Read-only tools · 3
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age124 days
Maintainers1

Observed 2026-10-24 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @pipeworx/mcp-data-dc (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads426Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Data Dc works

What Data Dc does

Data Dc provides MCP access to Washington, DC open data published through opendata.dc.gov and the ArcGIS REST API. Its main use cases are retrieving recent records from common datasets, finding available layers in a DC ArcGIS service, and running structured queries against a selected layer.

The shortcut path is dc_recent, which accepts friendly dataset names for crime, 311 service requests, and building permits. Results are returned newest first, and ArcGIS epoch timestamps are converted to ISO-formatted dates. For broader coverage, dc_layers supports service discovery and dc_query can address any Washington, DC ArcGIS layer when its service path and layer ID are known.

How it works

The hosted MCP endpoint is available at https://gateway.pipeworx.io/data-dc/mcp. An MCP client connects to that URL and can invoke the three Data Dc tools. The same gateway also exposes shared Pipeworx tools on the endpoint, including routing and discovery functions; the exact tool set is reported during MCP initialization.

A local npm package, @pipeworx/mcp-data-dc, acts as a stdio bridge. The client starts it with npx, and the bridge forwards requests to the hosted gateway, so network access is still required. The gateway can also be called directly over HTTP through its tool API.

Setup and configuration

For a hosted connection, add the endpoint to an MCP client configuration:

config.json
{
  "mcpServers": {
    "data-dc": {
      "url": "https://gateway.pipeworx.io/data-dc/mcp"
    }
  }
}

The npm bridge uses this configuration:

config.json
{
  "mcpServers": {
    "data-dc": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-data-dc"]
    }
  }
}

Anonymous use is available with a daily call limit. Setting PIPEWORX_API_KEY supplies a Pipeworx bearer token and increases the allowance for a free account. Set PIPEWORX_META_TOOLS=1 if the local bridge should also list the gateway-wide meta-tools. Requests require network access; the package has no offline mode.

Tools and capabilities

  • dc_recent retrieves recent rows from the crime, 311, or permits datasets. An ArcGIS where expression can narrow the result.
  • dc_layers lists layer IDs and names for known services or a supplied ArcGIS service path. Omit the service to list known DC services.
  • dc_query runs an ArcGIS layer query using a service path and layer ID. Supported query controls include where, out_fields, order_by, and limit.
  • Date values returned from ArcGIS epoch format are converted to ISO dates.

Limitations and notes

The friendly-name shortcut covers the listed common datasets; use dc_layers followed by dc_query for other layers. The integration is independent and unofficial, and is not affiliated with or endorsed by the upstream data provider. The npm bridge forwards calls to the hosted service rather than running an independent local data source. Anonymous calls are capped at 50 per day, while a free account raises the limit to 200 per day. The hosted and local routes expose the same underlying gateway and data sources, but the local bridge lists only this pack's tools unless meta-tools are enabled.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Data Dc

Data Dc is an MCP server that connects AI clients to Washington, DC open data from opendata.dc.gov through the ArcGIS REST API. Its main tools retrieve recent crime, 311, and permit records, discover service layers, and run filtered queries against selected DC ArcGIS layers.

Use the hosted MCP URL or run the npm stdio bridge with npx. Configure `https://gateway.pipeworx.io/data-dc/mcp` as the server URL, or start `@pipeworx/mcp-data-dc` with `npx -y`. The bridge forwards requests to the gateway and requires network access.

Data Dc provides friendly-name access to crime, 311 service requests, and building permits. For other ArcGIS layers, call `dc_layers` to discover service and layer identifiers, then use `dc_query` with the relevant service path and layer ID.

No, Data Dc can make anonymous calls. Anonymous usage is limited to 50 calls per day; setting `PIPEWORX_API_KEY` with a free Pipeworx account raises the allowance to 200 calls per day.

Yes, Data Dc can be configured in Cursor using its hosted MCP endpoint. The server also supports Claude Desktop and Windsurf, and its standard HTTP and stdio connection methods can be used by compatible MCP clients.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewData Dc AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/data-dc?style=directory)](https://allmcps.com/mcp/data-dc)
HTML Embed
<a href="https://allmcps.com/mcp/data-dc"><img src="https://allmcps.com/api/badge/data-dc?style=directory" alt="Data Dc on AllMCPs" /></a>