lookup_propertyLABSCO SUMMARY
Count first, page later — a wide data set made conversational.
This is the vendor's own server, and its shape follows how the underlying API is actually used: ask for a count, glance at a preview, then page through the detail. That means an agent can size a property question before it drags the full answer into context, which is what makes a data set this wide usable in a conversation at all.
What it is
A hosted endpoint at https://mcp.batchdata.com that you connect to as a remote server over Streamable HTTP; there is nothing to install. It covers the work the BatchData API is used for — property lookup, comparables, criteria search, owner skip tracing, phone compliance and address processing — and each of the heavy result sets is offered three ways, as a count, a short preview, or full paginated detail.
What you get
- A property's detail by address, ID or parcel number
- Comparable properties as a count with aggregate metrics, a short preview, or paginated full detail by offset or cursor
- Property search by criteria the same three ways, with quicklist breakdowns on the count
- Owner and contact information for a property, by address or parcel number
- Phone verification covering reachability, carrier, Do Not Call status and TCPA litigator status
- Do Not Call and TCPA litigator checks on their own, when that is all you need
- Addresses standardised to USPS form, geocoded to coordinates, or reverse-geocoded back from them
Requirements
A BatchData account. OAuth is the vendor's recommended route — a browser login by email or Google, tokens that refresh themselves and a connector that follows you to mobile — and needs no configuration beyond the server URL. The alternative is a bearer API token from the BatchData web app, bridged through mcp-remote, which wants Node.js 22 because the bundled runtime in some clients is older. Two things stop people at the door: in Claude a connector you have just added stays off until you toggle it on from the chat's connector list, and skip tracing has to be switched on for your team by an admin before it returns anything. One older tool, comparable_property, is marked deprecated — it returns every comparable at once, and the count, preview and page trio replaces it.
Setup effort
One command, then sign in — claude mcp add --transport http BatchData https://mcp.batchdata.com, then approve the OAuth sign-in
USE CASES
01
Pricing a house against what sold nearby
Pull the subject property, get the comparable count with its aggregate metrics to see whether the set is worth reading, then preview and page through the actual comps.
02
Building a target list from search criteria
Count the properties matching your criteria with quicklist breakdowns first, preview the head of the list, then page through the full detail once the criteria look right.
03
Finding an owner and checking you may call them
Skip trace the property for owner and contact details, then run the number for reachability and carrier, and check Do Not Call and TCPA litigator status before anyone dials.
04
Cleaning up a messy address list
Standardise free-typed addresses to USPS form, get coordinates for the ones you need to map, and turn coordinates back into an address where that is what you have.
15 tools
Listed in project docs. Your client may show a different list.
comparable_property_countcomparable_property_previewcomparable_property_pagecomparable_propertysearch_properties_countsearch_properties_previewsearch_properties_pageskip_trace_propertyverify_phonecheck_dnc_statuscheck_tcpa_statusverify_addressgeocode_addressreverse_geocode_addressBEFORE YOU INSTALL
What to know first
Tools you get
15 tools named in the project's documentation. comparable_property is deprecated in favour of the count, preview and page tools. skip_trace_property returns 403 unless an admin enables SkipTracing v3 for your team and your token has the permission.
Requires
- A BatchData account, signed in through your client when it connects
- Node.js 22+ and an AUTH_HEADER only on the token-bridge route, which the vendor does not recommend
INSTALLATION
Connect your client
Server setup
claude mcp add
Claude Code — OAuth
TERMINAL
claude mcp add --transport http BatchData https://mcp.batchdata.comHosted endpoint
ENDPOINT URL
https://mcp.batchdata.comAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Claude.ai — OAuth, Claude Desktop — OAuth
Settings → Connectors
Add Connector
URL
https://mcp.batchdata.comsign in
toggle the connector on in the + menu
approve the first tool use
Cursor — OAuth
Cursor Settings
MCP configuration
Add MCP Server
CURSOR — OAUTH · URL
https://mcp.batchdata.comauthenticate in the browser popup
ChatGPT — OAuth
Connector name: BatchData
MCP Server URL: https://mcp.batchdata.com
Claude Desktop — Token, macOS
CLAUDE DESKTOP — TOKEN, MACOS · JSON
{
"mcpServers": {
"BatchData": {
"command": "/Users/<YOUR_USERNAME>/.volta/bin/npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.batchdata.com",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer <YOUR_API_TOKEN>"
}
}
}
}This command path assumes Node.js 22 installed with Volta, as the vendor's token guide does: curl https://get.volta.sh | bash, restart the terminal, then volta install node@22; whoami prints the name for <YOUR_USERNAME>. If Node.js 22 came from somewhere else, set command to that npx instead. <YOUR_API_TOKEN> is your BatchData API token.
Claude Desktop — Token, Linux
CLAUDE DESKTOP — TOKEN, LINUX · JSON
{
"mcpServers": {
"BatchData": {
"command": "/home/<YOUR_USERNAME>/.volta/bin/npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.batchdata.com",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer <YOUR_API_TOKEN>"
}
}
}
}This command path assumes Node.js 22 installed with Volta, as the vendor's token guide does: curl https://get.volta.sh | bash, restart the terminal, then volta install node@22; whoami prints the name for <YOUR_USERNAME>. If Node.js 22 came from somewhere else, set command to that npx instead. <YOUR_API_TOKEN> is your BatchData API token.
Claude Desktop — Token, Windows
CLAUDE DESKTOP — TOKEN, WINDOWS · JSON
{
"mcpServers": {
"BatchData": {
"command": "C:\\Program Files\\nodejs\\npx.cmd",
"args": [
"-y",
"mcp-remote",
"https://mcp.batchdata.com",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer <YOUR_API_TOKEN>"
}
}
}
}Any MCP client
Server URL: https://mcp.batchdata.com
Transport: Streamable HTTP
Authentication: Bearer token via Authorization header
