Skip to content
Back to the index

data-detroit

pipeworx.ioInfrastructure🇺🇸

No liveness check has reached it yet; it has been in the index since 9 Oct 2026. How this is checked

Data Detroit is an MCP server that exposes tools for discovering and querying Detroit open-data services. It provides recent records, ArcGIS layer discovery, and flexible layer queries for developers and AI agents.

Inferred · not functionally tested

WebAPICloud-managed
data-detroit preview
Visit pipeworx.io
2alternatives
6features
2026since

Overview

6 features

Purpose: Finding and querying Detroit open-data records without manually navigating ArcGIS services.

Inferred · not functionally tested

Audience: Developers and AI agents working with Detroit public data

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

data-detroit sits in PulseGate's API design, testing & docs category. Inferred · not functionally tested: It focuses on finding and querying Detroit open-data records without manually navigating ArcGIS services. Inferred · not functionally tested: It is built as a B2B product for developers and AI agents working with Detroit public data. Basis unknown · not verified: It ships for the web and API.

It is developed by Pipeworx (United States). Inferred · not functionally tested: Among its 6 catalogued features are recent records, layer discovery, and arcGIS queries. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Recent records
  • Layer discovery
  • ArcGIS queries
  • JSON-RPC endpoint
  • MCP tools
  • TypeScript examples

Topics: Inferred · not functionally tested

Tags
detroit-open-dataarcgis-queryingmcp-serverpublic-data-api

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCPAPI
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed9 Oct · 18:01 UTC
    Data Detroit seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about data-detroit

What does data-detroit do?
Inferred · not functionally tested: Data-detroit focuses on finding and querying Detroit open-data records without manually navigating ArcGIS services. It is catalogued under API design, testing & docs on PulseGate.
Who is data-detroit for?
Inferred · not functionally tested: data-detroit is a B2B product built for developers and AI agents working with Detroit public data.
What platforms does data-detroit run on?
Basis unknown · not verified: data-detroit runs on the web and API.
Is data-detroit still active?
Unverified. data-detroit has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What are alternatives to data-detroit?
Similar projects tracked by PulseGate include arcgis-detroit, data-michigan, and data-dc.arcgis-detroitdata-michigandata-dc
Who develops data-detroit?
data-detroit is developed by Pipeworx, based in the United States.
Does data-detroit have an API or integrations?
Inferred · not functionally tested: Yes — data-detroit exposes an MCP server and a public API.

Similar projects

Closest matches by what these projects do