Home / MCP registry index / properties.hercules/property-data

Hercules property data

properties.hercules/property-data in the official MCP registry. Endpoint https://app.hercules.properties/mcp.

The registry describes it as: NYC and US property records: owners, LLC officers, mortgages, pre-foreclosures and investors.

We read its 28 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http property-data https://app.hercules.properties/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "property-data": {
      "url": "https://app.hercules.properties/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"property-data","type":"http","url":"https://app.hercules.properties/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

get_hercules_overview buy_credits get_credit_balance search_nyc_preforeclosures run_nyc_preforeclosure_search get_nyc_preforeclosure_detail quote_national_property_search run_national_property_search get_property_detail quote_active_investor_search run_active_investor_search find_nyc_property get_nyc_property unlock_nyc_property_report unlock_nyc_owner_contacts search_nyc_owners get_nyc_owner_portfolio search_nyc_underused_properties run_nyc_underused_search search_nyc_signals run_nyc_signals_search get_nyc_unit search_nyc_properties quote_llc_owner_lookup run_llc_owner_lookup quote_investor_firm_search run_investor_firm_search top_up_credits

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): b8ae49db25f6d4d7. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/properties-hercules-property-data/badge.svg)](https://lazaretto.dev/mcp-registry/properties-hercules-property-data)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.