Skip to content

MCP servers › io.github.BetaNYC › nyc-charter-laws-rules

MCP server · registry snapshot 2026-11-14 · last checked 2026-11-14

nyc-charter-laws-rules MCP server

Registry name io.github.BetaNYC/nyc-charter-laws-rules

NYC Charter, Laws and Rules — the publisher's title

by BetaNYC · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗

Search and read the NYC Charter, Administrative Code and Rules of the City of New York — the publisher's description

8 of 9 record checks metversion 0.5.0JavaScriptMITstandard input/output

Summary

io.github.BetaNYC/nyc-charter-laws-rules is a local MCP server listed in the official MCP registry at version 0.5.0, under the namespace of the GitHub account BetaNYC. Its linked repository, github.com/BetaNYC/nyc-charter-laws-rules, belongs to the same GitHub account.

Record checks

8 of 9 record checks met

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • met: npm package carries build provenance (attestation)
  • not met: No known critical or high advisory in the package or its dependencies
  • #1,962 of 20,610 packages by monthly downloads, tied with 1 other
  • #3,108 of 28,859 repositories by GitHub stars, tied with 180 others

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
npm · listed version behind the latest release
License
MIT
Dependencies
3 packages with a critical or high advisory (0 critical, 3 high)
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

Worth knowing before you connect it

  • The registry lists 0.5.0; 0.5.1 is newer (1 release).
  • 3 packages with a critical or high advisory (0 critical, 3 high) in its dependencies (as resolved on 2026-11-14).
  • Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.5.0, published 2026-11-13 (registry, as of the 2026-11-14 snapshot)
First listed version
2026-11-09 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-11-09 to 2026-11-13; 2 in the 90 days before the 2026-11-14 snapshot.
Most recent 2 versions
  • 0.5.0 · 2026-11-13
  • 0.4.4 · 2026-11-09
(versions still listed in the registry only)
Registry data
snapshot 2026-11-14
Package and repository
checked 2026-11-14

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.4.4 (published 2026-11-09) → 0.5.0 (published 2026-11-13), between the registry lists of 2026-11-13 and 2026-11-14.

The publisher’s GitHub release note for v0.5.0, published 2026-11-13.

Read the release note (the publisher’s text, shown as plain text)
## What's Changed
* What's changed: whats_changed and about_betanyc tools, WHATS-CHANGED.md (0.5.0) by @noneck in https://github.com/BetaNYC/nyc-charter-laws-rules/pull/34
* Release day: date 0.5.0 (2026-11-13) by @noneck in https://github.com/BetaNYC/nyc-charter-laws-rules/pull/35


**Full Changelog**: https://github.com/BetaNYC/nyc-charter-laws-rules/compare/v0.4.5...v0.5.0

The release on GitHub

Source: the official MCP Registry list on 2026-11-13 and on 2026-11-14; release notes from the GitHub Releases API, checked 2026-11-14.

What it is

How do I add it to my client?

Config from the registry entry

From the npm package @betanyc/nyc-charter-laws-rules

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "nyc-charter-laws-rules": {
      "command": "npx",
      "args": [
        "-y",
        "@betanyc/nyc-charter-laws-rules@0.5.0"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "nyc-charter-laws-rules": {
      "command": "npx",
      "args": [
        "-y",
        "@betanyc/nyc-charter-laws-rules@0.5.0"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "nyc-charter-laws-rules": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@betanyc/nyc-charter-laws-rules@0.5.0"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"nyc-charter-laws-rules","type":"stdio","command":"npx","args":["-y","@betanyc/nyc-charter-laws-rules@0.5.0"]}'
Claude Code
claude mcp add --transport stdio nyc-charter-laws-rules -- npx -y @betanyc/nyc-charter-laws-rules@0.5.0
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "nyc-charter-laws-rules": {
      "command": "npx",
      "args": [
        "-y",
        "@betanyc/nyc-charter-laws-rules@0.5.0"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "nyc-charter-laws-rules": {
      "command": "npx",
      "args": [
        "-y",
        "@betanyc/nyc-charter-laws-rules@0.5.0"
      ]
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.nyc-charter-laws-rules]
command = "npx"
args = ["-y", "@betanyc/nyc-charter-laws-rules@0.5.0"]
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "nyc-charter-laws-rules": {
      "command": "npx",
      "args": [
        "-y",
        "@betanyc/nyc-charter-laws-rules@0.5.0"
      ]
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @betanyc/nyc-charter-laws-rules@0.5.0
  • Optional settings the entry also lists (left out above): NYC_LAWS_INDEX_DIR, NYC_CLR_FOOTER.
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.5.0
Latest stable
0.5.1
Status
behind the latest release (1 releases, 1 days)
Withdrawn
no

Source: registry.npmjs.org · 2026-11-14. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high3moderate0low0

Counted in the full dependency tree as resolved on 2026-11-14 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-+dWDTK9KNuAndb7vJ…
Signature
signed and attested
License
MIT

Source: the package registry · 2026-11-14.

Usage

Downloads
1,751 in the last month

Source: api.npmjs.org · 2026-11-14.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • Install-time script (npm). No install-time script in the published package.json (version 0.5.0). Source: read 2026-11-14.
  • Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: read 2026-11-14.
  • Node.js version (npm). Needs Node 20 or later (engines.node >=20). Source: read 2026-11-14.
  • MCP SDK in the package files. Lists @modelcontextprotocol/sdk as a dependency (package.json). Source: read 2026-11-14.
  • Build workflow. Built and published by GitHub Actions workflow .github/workflows/release.yml in https://github.com/BetaNYC/nyc-charter-laws-rules (npm provenance). Source: read 2026-11-14.

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-14.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-14. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-14. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-14. Source: read 2026-11-14.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-14. Source: read 2026-11-14.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Version 0.5.0 on npmExists and can be installedmatchesnpm · 2026-11-14
Repository github.com/BetaNYC/nyc-charter-laws-rulesOpens publiclymatchesapi.github.com · 2026-11-14

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.BetaNYC · 8 servers
GitHub owner
an organization (BetaNYC)
Build record
signed and attested
Repository
github.com/BetaNYC/nyc-charter-laws-rules
Stars
10
Repository age
91–180 days
Last push
0–30 days ago
Archived
no
Security policy
owner's .github/SECURITY.md

Source: the registry entry and api.github.com · 2026-11-14; security policy read from GitHub · 2026-11-12.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

8 of 9 record checks met

  • #1,962 of 20,610 packages by monthly downloads, tied with 1 other
  • #3,108 of 28,859 repositories by GitHub stars, tied with 180 others
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists; a newer one is out.
  • Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
  • Not metNo known critical or high advisory in the package or its dependencies3 packages in its dependencies with a critical or high advisory (npm audit counts packages, not advisories).What changes this check: npm's documentation describes listing a project's dependency advisories with npm audit and applying compatible dependency updates. npm: npm audit

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-14 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.BetaNYC/nyc-charter-laws-rules

Answered from the data above

Who publishes io.github.BetaNYC/nyc-charter-laws-rules?

The registry ties the namespace io.github.BetaNYC to the GitHub account BetaNYC; only its owner can publish under it. Its linked repository, github.com/BetaNYC/nyc-charter-laws-rules, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.BetaNYC/nyc-charter-laws-rules safe to install?

We do not rate servers as safe or unsafe. 8 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. A newer stable release exists than the one listed. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has packages with advisories (3 high; npm audit). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.BetaNYC/nyc-charter-laws-rules been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does io.github.BetaNYC/nyc-charter-laws-rules publish a security policy?

Yes: its repository has a public security policy (github.com/betanyc/.github/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

No. The registry lists 0.5.0; the latest stable release on npm is 0.5.1.

Where is the source code of io.github.BetaNYC/nyc-charter-laws-rules?

In github.com/BetaNYC/nyc-charter-laws-rules, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-14; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
api.github.com · 2026-11-14
Hosting type
registry · 2026-11-14
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-14
Required credentials
none declared
registry · 2026-11-14 · no declaration is not a guarantee
Package registry
registry · 2026-11-14
Freshness
0–30 days
registry updatedAt · 2026-11-14
Lifecycle status
registry · 2026-11-14
License class
package registry · 2026-11-14
Integrity hash
declared (sri)
package registry · 2026-11-14
Signature / provenance
package registry · 2026-11-14
Dependency advisories
high
npm audit · 2026-11-14
Latest published version 0.5.1: 3 packages with an advisory (3 high) (npm audit · 2026-11-15)
Popularity
1,751 downloads a month
package registry · 2026-11-14
Publisher signals
owner: an organization · repository age: 91–180 days · stars: 10–99 · build record: signed and attested
api.github.com · 2026-11-14
Maintenance
api.github.com · 2026-11-14
Environment
your machine
where it runs, from the hosting type · 2026-11-14

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.BetaNYC/nyc-charter-laws-rules: MCP server record.” Data checked 2026-11-14. https://protocolprobe.com/mcp/servers/io.github.BetaNYC/nyc-charter-laws-rules

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 8 of 9 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.BetaNYC/nyc-charter-laws-rules)](https://protocolprobe.com/mcp/servers/io.github.BetaNYC/nyc-charter-laws-rules)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology