new-york-code
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
New York Code — New York statutes by citation
The New York Consolidated Laws. Give it PEN and 125.25, get back murder in
the second degree.
Part of Pipeworx — an MCP gateway connecting AI agents to 1867+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Auth
Needs a key, unlike the other state packs. NY Senate's Open Legislation
requires one — free from https://legislation.nysenate.gov/. Pipeworx fronts
one; pass _apiKey to use your own.
Related MCP server: American Samoa Code
The one state source that tells the truth about a miss
Every other state statute site returns HTTP 200 with an empty page when a
section does not exist, so each pack has to detect emptiness structurally. New
York returns success: false. That is worth knowing when comparing behaviour
across the state packs — here the not-found is the upstream's own verdict, not
our inference.
Tools
Tool | Returns |
| Full statutory text, heading, and the date that version took effect |
| The 137 NY law corpora, filterable ("labor" → |
Caveats
The API returns literal
\nsequences, not newlines. This pack unescapes them; raw callers of the API will see them.effective_datematters. New York versions its statutes, so the text you get is as of a date — check it before relying on wording.Section numbers are not contiguous; repealed sections are normal.
Data source
NY Senate Open Legislation API. New York statutes are public record.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"new-york-code": {
"url": "https://gateway.pipeworx.io/new-york-code/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/new-york-code/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1867+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/ny_law_section \
-H 'Content-Type: application/json' \
-d '{"law":"PEN","section":"125.25"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/ny_law_section. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Run it from npm
@pipeworx/mcp-new-york-code is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/new-york-code/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"new-york-code": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-new-york-code"]
}
}
}Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about New York Code data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Resolve, search and verify legal citations against the official sources, with provenance.
Search and read U.S. Code statutes with legal and inline citations linking to uscode.ecfr.io.
New Jersey Statutes (N.J.S.A.) — section by citation (with amendment history), plus topic search.
U.S. law library for AI: court decisions, statutes, court rules and citation checks. Read-only.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables users to retrieve full current statutory section text by citation and search official section and chapter catchlines by topic or keyword. It also surfaces enactment/amendment history and repealed or transferred section dispositions when available.93 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve the full text of annotated statutory sections by citation, search the statutes by topic or keyword, and list all published titles, returning chapter, amendment history, and case-note annotations. Keyless access with citation-to-URL resolution handled internally, including ambiguous citation candidates.82 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to look up individual sections by citation — returning catchline, statutory text, history line, and a dated, linked list of later-enacted amendments kept separate from the 2020 snapshot — and to search official section catchlines by topic across all 28 titles. Keyless, with every response explicitly dated so callers know how current the text is.90 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables users to retrieve statutory section text by citation and search official section catchlines by topic or keyword, using live sources with archived fallback when unavailable.145 npmMIT