Data Collection
nycticketfacts.com
A server that retrieves and analyzes NYC parking and camera violation data from public city records.
ENDPOINT 1
https://mcp.nycticketfacts.com/mcp
MCP server metadata
- Name
- nycticketfacts
- Version
- 1.0.0
Known tools 3
plate_lookupLook up every OPEN parking and camera violation for a New York plate, live from the City of New York's public Open Data API.
Inferred read-onlyviolation_dismissal_ratesHow New York City parking and camera tickets are actually decided at hearing, violation type by violation type — the share dismissed outright and the share dismissed or reduced, computed from the City's own published hearing records (119.8M rows).
Inferred read-onlyborough_oddsNYC hearing outcomes by borough/county: the share of decided hearings dismissed outright and dismissed-or-reduced in each borough, from the City's own records.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.nycticketfacts]
url = "https://mcp.nycticketfacts.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"nycticketfacts": {
"type": "http",
"url": "https://mcp.nycticketfacts.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: nycticketfacts
Remote MCP URL: https://mcp.nycticketfacts.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"nycticketfacts": {
"url": "https://mcp.nycticketfacts.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"nycticketfacts": {
"type": "http",
"url": "https://mcp.nycticketfacts.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "nycticketfacts",
"transport": "streamable-http",
"url": "https://mcp.nycticketfacts.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://nycticketfacts.com
MCP server metadata
- Name
- WebMCP
Known tools 0
No tool metadata was available in the registry cache.
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.webmcp]
url = "https://nycticketfacts.com"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"webmcp": {
"type": "http",
"url": "https://nycticketfacts.com"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: webmcp
Remote MCP URL: https://nycticketfacts.com
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"webmcp": {
"url": "https://nycticketfacts.com"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"webmcp": {
"type": "http",
"url": "https://nycticketfacts.com"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "webmcp",
"transport": "streamable-http",
"url": "https://nycticketfacts.com"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.