Back to Browse

Nyc Record MCP Server

Developer ToolsModerate6.1MCP RegistryLocal
Free

Server data from the Official MCP Registry

Search NYC City Record notices: procurement, contract awards, open solicitations, public hearings

About

Search NYC City Record notices: procurement, contract awards, open solicitations, public hearings

Security Report

6.1
Moderate6.1Moderate Risk

The nyc-record-mcp server reads the public NYC Open Data City Record dataset and requires no credentials; an optional Socrata app token is read from an environment variable. The visible code shows no exfiltration, shell execution, or hardcoded secrets, and its network access matches its stated purpose. Some source files (src/city-record.ts, remainder of tools.ts) were truncated, so the review is partial, and the shared betanyc-tools module reads only a local WHATS-CHANGED.md file. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

4 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

What You'll Need

Set these up before or after installing:

Optional NYC Open Data (Socrata) app token for higher rate limits. Not needed for normal useRequired

Environment variable: SOCRATA_APP_TOKEN

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "nyc-record-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@betanyc/nyc-record-mcp@1.2.0"
      ],
      "env": {
        "SOCRATA_APP_TOKEN": "your-socrata-app-token-here"
      }
    }
  }
}

Some servers take additional arguments. See the repository for details.

Documentation

View on GitHub

From the project's GitHub README.

nyc-record-mcp

An MCP (Model Context Protocol) server for NYC City Record notices, powered by the NYC Open Data dataset.

The City Record is the official publication of the City of New York — procurement solicitations, contract awards, public hearings, and agency notices, all in one place.

Vibe coded with Claude by BetaNYC.

What's changed: new tools, changes to what the tools return, and corrections, newest first.

Where the data comes from: the source, its publisher, how current it is, its terms, and where to report an error. Also published as a DCAT-US 3.0 catalog, data.json.


API key

No API key is required. The City Record dataset is public and this server works out of the box — no signup, no token.

Optionally, you can set a free NYC Open Data (Socrata) app token to get higher rate limits under heavy use. It is not needed for normal use. To use one, set it as the SOCRATA_APP_TOKEN environment variable:

export SOCRATA_APP_TOKEN="your-app-token"

What it does

Exposes 10 tools over MCP:

ToolDescription
search_noticesFull-text search across all notices
get_notices_by_agencyNotices from a specific city agency
get_notices_by_typeFilter by notice type (Solicitation, Award, Public Hearings, etc.)
get_procurement_noticesRecent solicitations, awards, and intent-to-award notices
get_public_hearingsRecent public hearings, comment periods, and meetings
get_open_solicitationsActive RFPs/RFQs where the deadline has not passed
get_notices_by_date_rangeAll notices published within a date window
whats_changedWhat changed in this server, newest first, from WHATS-CHANGED.md (filter by date or tag)
about_betanycWho built this server, where to report a bug in this server or ask for a new feature, and BetaNYC's links
about_dataWhere the data comes from, from DATA-SOURCES.json: the publisher, whether it is an official record, how current it is, terms and credit line, where to check a notice and where to report an error

Tools reference

search_notices

Full-text search across notice titles, descriptions, and agency names.

ParameterTypeRequiredDefaultDescription
querystringyes—Search term
limitnumberno25Max results (max 100)
search_notices("affordable housing")
search_notices("cybersecurity", limit=50)

get_notices_by_agency

Get notices from a specific city agency. Accepts partial name matches.

ParameterTypeRequiredDefaultDescription
agency_namestringyes—Agency name or partial name
limitnumberno25Max results (max 100)
get_notices_by_agency("DCAS")
get_notices_by_agency("Department of City Planning")
get_notices_by_agency("Parks")

get_notices_by_type

Filter notices by type.

ParameterTypeRequiredDefaultDescription
notice_typestringyes—One of: Solicitation, Award, Intent to Award, Intent to Negotiate, Public Hearings, Public Comment, Meeting, Notice, Vendor List, Sale
limitnumberno25Max results (max 100)
get_notices_by_type("Solicitation")
get_notices_by_type("Public Hearings")
get_notices_by_type("Award", limit=50)

get_procurement_notices

Returns recent solicitations, awards, intent-to-award, and vendor list notices — the full procurement lifecycle.

ParameterTypeRequiredDefaultDescription
limitnumberno25Max results (max 100)
get_procurement_notices()
get_procurement_notices(limit=100)

get_public_hearings

Returns recent public hearings, public comment periods, agency meetings, and general notices.

ParameterTypeRequiredDefaultDescription
limitnumberno25Max results (max 100)
get_public_hearings()

get_open_solicitations

Returns active solicitations where the due date has not yet passed, sorted by soonest deadline first.

ParameterTypeRequiredDefaultDescription
limitnumberno25Max results (max 100)
get_open_solicitations()
get_open_solicitations(limit=50)

get_notices_by_date_range

Get all City Record notices published within a date range.

ParameterTypeRequiredDefaultDescription
start_datestringyes—Start date, YYYY-MM-DD
end_datestringyes—End date, YYYY-MM-DD
limitnumberno50Max results (max 200)
get_notices_by_date_range("2026-05-01", "2026-05-19")
get_notices_by_date_range("2026-01-01", "2026-03-31", limit=200)

whats_changed, about_betanyc and about_data

BetaNYC adds these three tools to each of its MCP servers, with the same inputs and output. whats_changed reads WHATS-CHANGED.md, which ships in the package, and never touches the network.

ParameterTypeRequiredDefaultDescription
sincestringno—Changes on or after this date, YYYY-MM-DD
tagstringno—Site, Data, MCP or Correction
limitnumberno10Max results (max 50)

about_betanyc takes no parameters. It names the server and its version, who built it, where to report a bug in this server or ask for a new feature, and BetaNYC's links.

about_data answers from DATA-SOURCES.json, which ships in the package, and never touches the network. Its one optional parameter, topic, takes the source's name (city-record) or a tool name. It says who publishes the data, whether it is an official record, how it reaches the server, how current it is, what it covers and leaves out, the terms of use and credit line, where to check a notice and where to report an error, and BetaNYC's address for questions about the data, lab@beta.nyc. The same facts are published as a DCAT-US 3.0 catalog, data.json, generated from DATA-SOURCES.json with python3 scripts/whats_changed.py about-data catalog DATA-SOURCES.json (never edit it by hand).

whats_changed(tag="Correction")
about_betanyc()
about_data(topic="get_open_solicitations")

src/betanyc-tools.ts, scripts/whats_changed.py, scripts/tests/catalog_validate.py and scripts/mcp_shared/ are copies of shared files in BetaNYC's workspace: never edit them here.


Common workflows

Track open RFPs before they close

get_open_solicitations()        → sorted by due date — soonest first
search_notices("technology")    → filter by topic to narrow scope

Monitor a specific agency's procurement activity

get_notices_by_agency("DOITT")           → all recent notices
get_notices_by_type("Solicitation")      → open bids from any agency

Research recent contract awards

get_notices_by_type("Award")             → recent contract awards
search_notices("cybersecurity award")    → keyword-filtered awards

Find public comment opportunities

get_public_hearings()                    → hearings, meetings, comment periods
get_notices_by_date_range("2026-05-01", "2026-05-31")   → by month

Prerequisites

  • Node.js 18 or later
  • No API key required — the dataset is public
  • Optional: NYC Open Data app token for higher rate limits (set as SOCRATA_APP_TOKEN)

Installation

From v1.1.1 the server is also published to the official MCP Registry as io.github.BetaNYC/nyc-record-mcp.

Option 1 — npx (no install required)

npx @betanyc/nyc-record-mcp

Option 2 — global install

npm install -g @betanyc/nyc-record-mcp
nyc-record-mcp

Option 3 — build from source

git clone https://github.com/BetaNYC/nyc-record-mcp.git
cd nyc-record-mcp
npm install
npm run build
npm start

Run the test suite (builds first, then runs the Node test runner against test/*.test.mjs):

npm test

Configuration

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "nyc-record": {
      "command": "npx",
      "args": ["-y", "@betanyc/nyc-record-mcp"]
    }
  }
}

With an optional app token:

{
  "mcpServers": {
    "nyc-record": {
      "command": "npx",
      "args": ["-y", "@betanyc/nyc-record-mcp"],
      "env": {
        "SOCRATA_APP_TOKEN": "your_token_here"
      }
    }
  }
}

Claude Code

Add it with the CLI:

claude mcp add nyc-record -- npx -y @betanyc/nyc-record-mcp

Or add to your project's .mcp.json (checked in, shared with your team):

{
  "mcpServers": {
    "nyc-record": {
      "command": "npx",
      "args": ["-y", "@betanyc/nyc-record-mcp"]
    }
  }
}

Example usage

Once connected, you can ask your AI assistant things like:

  • "What RFPs are currently open from the Department of City Planning?"
  • "What contracts did DCAS award this month?"
  • "Are there any public hearings about zoning this week?"
  • "What solicitations related to cybersecurity are still open?"
  • "Show me all City Record notices from Parks Department in April 2026."

Data source

All data comes from the NYC City Record Online dataset on NYC Open Data, published by the NYC Department of Citywide Administrative Services (DCAS). The dataset is updated daily. Its notices go back to 2003. About 88% of them are "Changes in Personnel" listings (City staff appointments, departures and pay changes), which start in July 2013 and have no notice type, so the tools that pick notices by type never return them, while keyword, agency and date searches can be mostly personnel listings. DATA-SOURCES.json has the details.


Related projects

If you're looking for broader access to NYC Open Data — or Socrata-powered portals in other cities — check out Nathan Storey's socrata-mcp-server. It connects AI assistants to any Socrata portal with tools for dataset discovery and SoQL queries, including NYC, Chicago, San Francisco, and New York State's open data portal (data.ny.gov), among hundreds more. The SODA API pattern in this project was informed by Nathan's work.

About BetaNYC

This project is built and maintained by BetaNYC, New York's civic technology and open-data community. We work to improve lives in New York through civic design, technology, data, and public-interest technology.

Come do civic tech with us. We run public events, meetups, and hands-on data classes throughout the year — including NYC School of Data and CityCamp NYC, and we host frequent civic-tech gatherings. See what's coming up on our events calendar.

Sustain this work. These MCP servers are free and open source. To help keep this work going and find BetaNYC's tools, please consider donating and becoming a Beta Builder.

Building on this? Tell us!

If you build something with this project, we'd love to hear about it. We can help other New Yorkers find it. BetaNYC publishes a weekly newsletter, This Week in NYC's Civic Technology and Open Data.

Related BetaNYC MCP servers

BetaNYC maintains a suite of open-source MCP servers for NYC and NYS civic data. See the full directory, with install details for each, at beta.nyc/ai-tools.

This server pairs directly with:

  • nyc-checkbook-mcp: move from a procurement solicitation or award notice to the resulting registered contract, payments, and agency spending in Checkbook.

Working with the wider NYC Open Data portal? This server reads the City Record dataset on NYC Open Data. To search the full catalog or run ad-hoc SoQL queries across other datasets, pair it with socrata-mcp-server (socrata-mcp-server on npm), a third-party MCP by Nathan Storey.


Contributing

Issues and pull requests welcome at github.com/BetaNYC/nyc-record-mcp.


Releases

Releases are automated. Pushing a tag matching v* (e.g. v1.0.2) runs tests, verifies the tag matches the package.json version, publishes to npm with provenance, and creates a GitHub Release with generated notes. See CHANGELOG.md for version history, and WHATS-CHANGED.md for the record written for everyone else. Requires the NPM_TOKEN repository secret.

Release day. A version bump merges with its WHATS-CHANGED.md entry headed ## Unreleased: Title and its CHANGELOG.md heading undated (## [X.Y.Z] - Unreleased), the entry's MCP version linking to CHANGELOG.md with no anchor. On the day the tag goes on, make one commit that:

  1. changes ## Unreleased: Title to ## YYYY-MM-DD: Title (same title, today's date in New York; check rejects a future date);
  2. gives the CHANGELOG.md heading the same date (## [X.Y.Z] - YYYY-MM-DD);
  3. adds the dated anchor to the MCP version link, computed with the script, never by hand: python3 -c "import sys; sys.path.insert(0,'scripts'); import whats_changed as w; print(w.github_slug('[X.Y.Z] - YYYY-MM-DD'))";
  4. runs python3 scripts/whats_changed.py check WHATS-CHANGED.md --release.

That commit may also reword the entry's body, since an entry counts as published only once it has a date, so no Whats-changed-edit: trailer is needed. Its title may never change, while Unreleased or when dated: CI checks it. Then tag that commit vX.Y.Z and push the tag. The Release workflow runs the same check --release before npm publish and stops while an Unreleased entry is left. A release that changes nothing a reader would notice (metadata only) gets no entry; its commit carries a No-whats-changed: <reason> trailer instead.


Support our work

Freedom isn't free. Support BetaNYC.

License

MIT License

Copyright (c) 2026 BetaNYC

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Reviews

No reviews yet

Be the first to review this server!