Global law
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
Find New York open data: which portal covers a place or topic, how to query it, datasets and columns
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 18/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 30/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 8 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 NY Data Registry。按照 https://mcp.popnx.com/i/betanyc-ny-data-registry-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server NY Data Registry,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "ny-data-registry": { "command": "npx", "args": [ "-y", "@betanyc/ny-data-registry-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NY Data Registry 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"ny-data-registry": {
"command": "npx",
"args": [
"-y",
"@betanyc/ny-data-registry-mcp"
]
}
}
}用 NY Data Registry 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 NY Data Registry,或回答中出现 NY Data Registry 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
NY_DATA_INDEX_AUTO_DOWNLOAD 设为 0 可停止首次运行时下载数据集索引。 SOCRATA_APP_TOKEN 可选的 Socrata 应用令牌,仅在构建你自己的索引时使用 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 NY Data Registry
NY Data Registry 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 NY Data Registry 的应用
B · 法律与政府数据 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server NY Data Registry,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user ny-data-registry -- npx -y @betanyc/ny-data-registry-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NY Data Registry 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user ny-data-registry -- npx -y @betanyc/ny-data-registry-mcp应能看到 NY Data Registry 在列表中并显示已连接
用 NY Data Registry 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 NY Data Registry,或回答中出现 NY Data Registry 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
NY_DATA_INDEX_AUTO_DOWNLOAD 设为 0 可停止首次运行时下载数据集索引。 SOCRATA_APP_TOKEN 可选的 Socrata 应用令牌,仅在构建你自己的索引时使用 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server NY Data Registry,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "ny-data-registry": { "command": "npx", "args": [ "-y", "@betanyc/ny-data-registry-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NY Data Registry 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 NY Data Registry 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 NY Data Registry,或回答中出现 NY Data Registry 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
NY_DATA_INDEX_AUTO_DOWNLOAD 设为 0 可停止首次运行时下载数据集索引。 SOCRATA_APP_TOKEN 可选的 Socrata 应用令牌,仅在构建你自己的索引时使用 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server NY Data Registry,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "ny-data-registry": { "type": "stdio", "command": "npx", "args": [ "-y", "@betanyc/ny-data-registry-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NY Data Registry 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 NY Data Registry 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 NY Data Registry,或回答中出现 NY Data Registry 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
NY_DATA_INDEX_AUTO_DOWNLOAD 设为 0 可停止首次运行时下载数据集索引。 SOCRATA_APP_TOKEN 可选的 Socrata 应用令牌,仅在构建你自己的索引时使用 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user ny-data-registry -- npx -y @betanyc/ny-data-registry-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"ny-data-registry": {
"command": "npx",
"args": [
"-y",
"@betanyc/ny-data-registry-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ny-data-registry": {
"command": "npx",
"args": [
"-y",
"@betanyc/ny-data-registry-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"ny-data-registry": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@betanyc/ny-data-registry-mcp"
]
}
}
}NY_DATA_INDEX_AUTO_DOWNLOAD envSOCRATA_APP_TOKEN 机密 env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 BetaNYC 验证,该账户拥有此仓库
代码最后更新于3天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 @betanyc/ny-data-registry-mcp@0.3.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/betanyc-ny-data-registry-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于3天前,最新版本(0.3.0)于5天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
German court decisions (Rechtsprechung) and laws (Gesetze) with citation graph and citation checks.
Search French-language and European case law and French legal texts (codes, statutes, treaties).
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.
Search Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint.
| 本项 NY Data Registry | Global law | Open Legal Data (Germany) | LibreJustice | InfraNode | Fedlex Connector | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | NOASSERTION | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An MCP (Model Context Protocol) server that finds open data across every New York data portal in BetaNYC's NY data portal registry: which portal covers a place or topic, how to query it, and, with the harvested index, which datasets and columns exist and in what formats.
It complements the socrata MCP rather than replacing it. This server knows *where* data is (224 sources across state, county, city, agency, library and nonprofit portals) and hands the agent the right Socrata domain or ArcGIS service. Querying the data stays with socrata and the other BetaNYC MCPs.
Built by BetaNYC. Status: 0.3.0. Package: @betanyc/ny-data-registry-mcp.
What changed in this server, newest first, including corrections: WHATS-CHANGED.md.
Thirteen tools, in three groups.
Registry tools (work out of the box, no index needed):
| Tool | What it answers |
|---|---|
find_sources | Which portals cover this topic or place? Filters: place, tier, platform family, has API, key required, status (default live) |
list_sources_for_place | Everything for one county, city, NYC borough or region. Says whether the place has a portal, was checked and has none, or is not in the registry (unchecked, not absent) |
how_to_query | Endpoint (verbatim from the registry, never guessed), API type, key and env var, example request, and which MCP to hand off to. Flags UNCONFIRMED, undocumented, gated, dead and no-portal rows |
check_source | One live request to a portal URL: status, redirect, response time, and whether that matches the registry |
registry_info | Row counts, registry date and origin, unmapped platform strings, index size and last harvest |
Index tools (need the harvested SQLite index):
| Tool | What it answers |
|---|---|
search_datasets | Dataset titles, descriptions, tags and column names across Socrata and ArcGIS portals. Filters: topic, place, portal, platform family, format (csv, geojson, shapefile, kml, api, xlsx …), updated since. One call gives the whole answer: the true number of matches, a count per portal when they don't all fit, the best rows, and a CSV file with every match. group_by summarizes by entity, county or platform family instead |
list_topics | The 24 shared topics, with how many datasets and portals each has, and the share of datasets with a topic. Filter: portal |
get_dataset_columns | Fields and types, every distribution (format + URL), license, publisher, extent, and per-field provenance. With standard, the dataset's description as Croissant or DCAT-US instead |
find_joinable | Datasets sharing a join key (BBL, BIN, borough, community district, council district, census tract, SWIS, FIPS, ZIP), from a curated key-column map, not raw name equality |
whats_new | Datasets added, changed or removed since a date |
About this server (the three tools BetaNYC is adding to each of its MCP servers; no index needed):
| Tool | What it answers |
|---|---|
whats_changed | What changed in this server, newest first, from WHATS-CHANGED.md: new tools, fixes and corrections. Filters: since, tag (Site, Data, MCP, Correction), limit. For datasets that are new on the portals, use whats_new |
about_betanyc | Who built the server, its version, where to report a bug in this server or ask for a new feature, and BetaNYC's links |
about_data | Where each kind of data comes from, from DATA-SOURCES.json: the source, its publisher and a link, whether it is an official record, what BetaNYC changed, how current it is on this server, terms of use, and where to report an error. Ask for one topic or one tool's sources |
These three come from src/betanyc-tools.ts, a copy of a file BetaNYC is adding to each of its MCP servers: change it in the BetaNYC workspace, never here. They answer in plain text plus structuredContent matching a declared outputSchema.
All tool inputs are strict: an unknown parameter is rejected by name, never silently dropped (same rule as nyc-311-mcp).
How `search_datasets` answers. One call gives the whole answer. total_matches counts every dataset that matches, with no cap. If they all fit in the reply (10 rows by default, up to 50), the reply lists them. If they don't, the reply does three things at once: it counts every match by portal (auto_grouped: true, with each portal's top titles), it lists the best-ranked rows that fit, and it writes every match to a CSV file on your computer (export.path, plus an MCP resource_link). So "which portals have tax lot data?" comes back complete in one call, and the CSV holds the full list for a spreadsheet. group_by summarizes by entity, county or platform family instead of portal. Replies stay under about 20 KB so they fit in an AI client's tool-result limit. Each reply also lists the registry portals the index does not search (no portal, not harvested, or a failed harvest), so an empty result is not read as "no such data".
`registry_id`: joining a data site to its government. Each registry row can carry a registry_id, the id of its government body in BetaNYC/ny-gov-web-registry (data/registry.json). Use it to join a data site to that registry's record of the government. Several data sites can share one id (a city's main portal and its GIS site, say). Not every row has one yet; ids are copied from the registry and never made up.
find_sources, list_sources_for_place, how_to_query and check_source always include registry_id, null when the row has none.search_datasets compact rows, its portal groups and coverage list, and find_joinable's by_portal include it only when there is one, to keep replies small. Full rows (detail: "full"), get_dataset_columns, find_joinable's dataset and the CSV always include it (an empty cell when there is none).how_to_query and check_source accept registry_id (when several sources share it, the reply lists them), and portal in search_datasets and whats_new accepts it to mean every data site of that government. registry_info counts the rows that carry one.`runs_it`: who runs this data site. Source rows from find_sources, list_sources_for_place, how_to_query and check_source also carry runs_it: the government body that runs the site, looked up by registry_id in the master list of government bodies (BetaNYC/ny-gov-web-registry data/registry.json). It gives the body's name, government_level (state, city, county, authority…), classification and website (its current primary domain, as the list writes it, such as mta.info). short_name appears when the list has one, and status when the body is not active.
registry_id means runs_it: null. Nothing is guessed from names.runs_it: { "found": false, "note": … }.runs_it_source block: which list, which copy (fresh, cache or bundled) and how current it is. registry_info adds a master_list block that lists the row ids the loaded list lacks.The CSV files. One row per matching dataset, best-ranked first: id, name, portal, portal id, registry_id, type, update date, link, formats, API endpoint, Socrata domain and 4x4, platform, counties, geometry type and column count. Standard CSV (RFC 4180), UTF-8, values as the portal published them, with one safety exception: a text value that starts with =, +, -, @, a tab or a carriage return gets a leading ', so a spreadsheet shows it as text instead of running it as a formula. Numbers are never changed. They go in ${HOME}/.cache/betanyc/ny-data-registry/exports/ (change with NY_DATA_EXPORT_DIR). The newest 50 are kept, none older than 7 days; nothing else in that folder is touched. export: "never" turns the file off and export: "always" writes one even for a short answer. offset still pages by hand for clients that need it, but nothing depends on it.
Topics. Every dataset gets topics from one shared list of 24, such as Housing and homelessness, Transportation or Elections and civic participation. A dataset can have several. They come from the dataset's own categories, tags and department, so the same topic finds the same kind of data on every portal, whatever each portal calls it. Pass topic to search_datasets, alone or with a query; a topic alone lists that topic, most-viewed first. Rows carry their topic ids. list_topics gives the list with counts. On the 2026-11-05 index, 8,910 of 9,569 datasets (93.1%) get at least one topic; the rest carry no label that fits the list, and text search still finds them. Each published index comes with topic-crosswalk.csv: every label on every portal, and the topics it gives. How it works and how to change it: docs/topics.md.
Standard metadata. get_dataset_columns with standard: "croissant" returns one dataset's description as Croissant 1.1, read by AI and ML tools. standard: "dcat-us" returns it as DCAT-US 3.0, read by government catalogs and data.gov. Each published index also comes with two statewide files: ny-data-dcat-us.json.gz (one DCAT-US catalog with every dataset, about 3 MB) and ny-data-croissant.jsonl.gz (one Croissant document per line, about 3 MB). ny-data-registry standards builds them from your installed index. Metadata only, as everywhere here. Licenses are never inferred. About 72% of datasets get no license from their portal. Where there is none, the reply links the portal's terms-of-use page if we have one, labeled "terms page, not a license". The registry has no terms-of-use field yet, so these come from links a portal put in a dataset's own license text, or from data/terms-pages.json, which lists a portal only after someone has opened its page (10 of the 35 portals harvested have one, checked 2026-11-14). Other text a portal puts in its license field, such as a disclaimer, is kept word for word as a rights statement, not as a license. Fields the standards require that portals do not give are left out and listed in missing: DCAT-US's contact email always, and a description for about 13% of datasets. Field mapping and validation: docs/standard-metadata-plan.md.
Ask your AI assistant these once the server is connected. Where we ran a question on 2026-11-05, what it found is noted. Portals change, so your results may differ.
Which datasets match my words? (search_datasets)