Code Violation Property Leads

io.github.Nero-EnginePublished by GitHub account Nero-Enginev0.1.0Updated Nov 4, 2026

Properties cited for code violations in 7 US cities, scored as distressed leads with NYC owner

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Apify-hosted MCP server that gives an assistant access to scored property leads cited for code violations in seven US cities, including NYC owner data.

What you can do
  • Retrieve property records cited for code violations across seven US cities.
  • Work with distressed-lead scores attached to those properties.
  • Look up owner information for New York City properties.
  • Access the dataset through an Apify actor exposed over a remote MCP endpoint.
When to use it
Useful for real-estate, investment or research work where you want an assistant to pull code-violation property leads and owner details without building your own scraper.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. An Apify account and API token are required, sent as a Bearer token in the Authorization header. Network access to Apify is needed.
Before you install
The server requires an Apify API token in the Authorization header; treat it as a secret. Apify usage may consume paid platform credits depending on your plan. Property and owner records are third-party data, so verify accuracy and check that your use complies with applicable rules before acting on leads.

Installation

In SourceWeft

  1. Open Code Violation Property Leads in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Nero-Engine%2Fcode-violation-leads/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "code-violation-property-leads": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=nerolabs/code-violation-leads"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestNov 4, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.