list_open_issues — NYC Property Facts MCP Tool Read-only
list_open_issues
(list open issues) is one of 5 tools on the
NYC Property Facts
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_open_issues from your client
- Claude Code NYC Property Facts list_open_issues run in your project directory
- Claude Desktop NYC Property Facts list_open_issues ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NYC Property Facts list_open_issues ~/.cursor/mcp.json
- VS Code NYC Property Facts list_open_issues .vscode/mcp.json
- Zed NYC Property Facts list_open_issues ~/.config/zed/settings.json
- Windsurf NYC Property Facts list_open_issues ~/.codeium/windsurf/mcp_config.json
- Cline NYC Property Facts list_open_issues ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NYC Property Facts list_open_issues ~/.gemini/settings.json
- Grok NYC Property Facts list_open_issues .mcp.json (in your project root)
- ChatGPT NYC Property Facts list_open_issues Settings → Connectors → Advanced → Developer mode
- Claude.ai NYC Property Facts list_open_issues Settings → Connectors → Add custom connector
- LangChain NYC Property Facts list_open_issues pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nyc-property-facts https://nycpropertyfacts.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.