Skip to main content

BatchData MCP Server Now Available - November 2025

Announcing the general availability (GA) release of the BatchData MCP server

Written by Charles Parra
Updated over 3 months ago

Release Date: November 2025

We're excited to announce the launch of the BatchData MCP (Model Context Protocol) Server, a new way to access BatchData's real estate property intelligence capabilities through AI assistants and large language models.

What is the BatchData MCP Server?

The BatchData MCP Server exposes BatchData's powerful property data APIs through a standardized protocol that AI assistants can use to help you with property research, skip tracing, phone verification, and address validation tasks.

MCP Server Endpoint: https://mcp.batchdata.com

Key Features

9 Specialized Tools Across 5 Categories

Property Intelligence (2 tools)

  • Property Lookup: Get comprehensive property details including lot characteristics, sale history, valuations, liens, mortgages, tax assessments, and building permits

  • Comparable Property Analysis: Perform comparative market analysis (CMA) with automated valuation, average prices, and comparable property details

Skip Tracing (1 tool)

  • Property Skip Trace: Find contact information for property owners including phone numbers, email addresses, and mailing addresses with full TCPA and DNC compliance flags

    • Powered by V3 Skip Trace API: Returns up to 3 persons per property (vs. 1 person in V1)

    • Enhanced Data Coverage: Multiple household members and property owners

    • Flexible TCPA Handling: Phone numbers include a tcpa boolean flag for programmatic filtering

    • Compliance by Default: TCPA-restricted phones are included with clear indicators, allowing you to implement your own compliance logic

Phone Verification (3 tools)

  • Full Phone Verification: Complete verification details including carrier, type, reachability, DNC status, and TCPA status

  • DNC Status Check: Quick Do Not Call registry lookup

  • TCPA Status Check: Quick TCPA litigator list verification

Address Verification (3 tools)

  • Address Verification: Normalize and verify addresses to USPS standards with detailed address components

  • Geocoding: Convert addresses to geographic coordinates

  • Reverse Geocoding: Convert coordinates to street addresses

How to Get Started

Authentication

All MCP tools require authentication using your BatchData API token. Include your API token in the Authorization header:

Authorization: Bearer YOUR_API_KEY

Using the MCP Server

You can integrate it with:

  • AI assistant platforms that support the Model Context Protocol

  • Custom applications using the MCP protocol

  • LLM-powered workflows requiring property data access

Example Use Cases

  1. Property Research Lookup comprehensive property details for investment analysis by providing an address or parcel number. Get instant access to property characteristics, sale history, liens, and market data.

  2. Market Analysis Find comparable properties for accurate valuation and pricing strategies. The tool returns aggregated metrics including estimated value, average price per square foot, and detailed comparable property information.

  3. Owner Contact Discovery Skip trace properties to find owner contact information for marketing campaigns. Using our new V3 Skip Trace endpoint, results include up to 3 persons per property with multiple phone numbers and email addresses. Each phone number includes clear TCPA and DNC compliance flags, giving you complete visibility while maintaining regulatory compliance.

  4. Phone Verification Verify phone numbers before making calls to ensure compliance with regulations. Check for TCPA litigators and DNC registry status to avoid potential violations.

  5. Address Validation Normalize and verify addresses for accurate data processing and mail delivery. Get USPS-validated addresses with ZIP+4, county information, and geocoded coordinates.

Compliance Features

The MCP Server includes built-in compliance indicators to help you stay compliant with regulations:

  • TCPA Litigator Flags: Identify phone numbers belonging to known TCPA litigators

  • DNC Registry Status: Check if numbers are on the Do Not Call registry

  • Phone Reachability: Verify numbers are active before attempting contact

  • Address Validity: Ensure addresses meet USPS delivery standards

Technical Details

Authentication: Bearer token (BatchData API token)

Rate Limits: Subject to standard BatchData API rate limits

Transport: Streamable HTTP

Common Response Codes

  • 200: Success - request processed successfully

  • 401: Authentication failed - invalid or missing API token

  • 429: Rate limit exceeded - retry after delay

  • 400/422: Invalid input - check request format

  • 500+: Service temporarily unavailable

Pricing

The MCP Server uses your existing BatchData API subscription. Each tool call counts as a standard API request based on the underlying endpoint being accessed. Refer to your BatchData pricing plan for details.

Resources

Getting Your API Token

If you don't already have a BatchData API token:

  1. Log in to your BatchData account

  2. Navigate to API Tokens/Server side Token - https://app.batchdata.com/api-tokens/server-side-token

  3. Add new token and grant it the permissions for the API end-points you want to expose to the MCP server. The applicable permissions are:

    1. Address

      1. address-geocode

      2. address-reverse-geocode

      3. address-verify

    2. Phone

      1. phone-verification

    3. Property

      1. property-lookup-all-attributes

        1. Enable all the datasets that you want to make available

      2. property-search

      3. property-skip-trace-v3

        1. Contact your Account Manager to enable access to the V3 Skiptrace API end-point.

  4. Use the key with the Authorization: Bearer header

What's Next: Product Roadmap

We're actively developing additional features to make the BatchData MCP Server even more powerful and easier to use:

Enhanced Account-Based Authentication (Coming Soon)

We're building an improved authentication system that will eliminate the need for API token configuration:

Simpler Setup:

  • No API token or local configuration needed

  • Users just provide the MCP server URL: https://mcp.batchdata.com

  • Your AI assistant will prompt you to log into your BatchData account

Better Security & Control:

  • Account-based authentication with automatic permission verification

  • Individual user tracking - know exactly who is using the MCP Server

  • Team owners can grant or revoke MCP Server access through the BatchData platform

  • No need to share API tokens across team members

  • Better visibility and control over team access

Broader Platform Support:

  • Enable support for additional AI platforms beyond Claude Desktop

  • Standardized OAuth authentication flow across all AI assistants

Property Search API Support (Planned)

We're planning to add comprehensive property search capabilities to the MCP Server:

Advanced Search Tools:

  • Search properties by location, price range, and property characteristics

  • Apply complex filter criteria (quicklists) for targeted searches

  • Access 140+ million properties across the United States

Investor-Focused Filters:

  • Find properties matching specific investment criteria

  • Filter by equity, vacancy, ownership type, and more

  • Support for 35+ property type classifications

Batch Operations:

  • Retrieve paginated results for large property datasets

  • Export property lists for further analysis

  • Integrate property search into AI-powered investment workflows

These enhancements will make the BatchData MCP Server the most comprehensive real estate intelligence platform for AI assistants.

Frequently Asked Questions

How is this different from your regular API?

API: Built for developers to integrate into software applications

MCP Server: Built for AI assistants to use on behalf of people

Both access the same BatchData intelligence, just different interfaces.

The regular API requires developers to write code that calls our endpoints, handles authentication, processes responses, and integrates the data into applications. The MCP Server allows AI assistants to directly access the same data through natural language conversations, handling all the technical details automatically.

What AI assistants work with MCP?

Currently Supported:

  • Claude Desktop (Anthropic) - Full support with API token configuration

Coming Soon (After Account-Based Authentication Launch):

  • ChatGPT and other AI platforms will be supported once we complete the enhanced account-based authentication system

  • The current API token method is optimized for Claude Desktop application

Is the data the same as your regular API?

Yes, 100%. The MCP Server uses the exact same BatchData intelligence that powers all our products. Same data quality, same coverage, same reliability. You're accessing the same 140+ million property records with the same comprehensive information.

How does authentication work currently?

The BatchData MCP Server currently uses API Token-Based authentication:

  • Use your existing BatchData API token to authenticate

  • Provide your API token when configuring your AI assistant

  • The same token used for our regular API works with the MCP Server

  • No additional credentials needed - if you have BatchData API access, you can use MCP

What security considerations should customers know about API tokens?

API tokens should be treated as sensitive credentials:

Important Security Notes:

  • Protect your token: Anyone with access to your API token can use the MCP Server

  • Manage access carefully: The token bypasses individual user access controls, so control who has access to it

  • Monitor usage: The account owner is responsible for all costs associated with token usage

  • Don't share publicly: Never commit tokens to code repositories or share them in unsecured channels

  • Think of it like a master key - secure it accordingly

Are there plans to improve authentication and access control?

Yes! We're actively developing an enhanced account-based authentication system (see the "What's Next: Product Roadmap" section above for details).

The improved system will provide:

  • No API token or local configuration needed

  • Account-based authentication with automatic login prompts

  • Individual user tracking

  • Centralized team access management through the BatchData platform

  • Better security and visibility

This enhanced authentication will be rolled out to customers once development is complete.

How do I configure the Claude Desktop application to work with the BatchData MCP server?

Setting up Claude Desktop requires two main steps: installing Node.js 22 and configuring Claude Desktop with your BatchData API token.

Step 1: Provision a BatchData API Token

  1. Log into https://app.batchdata.com/ and go to the Server Side Token provisioning page, https://app.batchdata.com/api-tokens/server-side-token

  2. Click on + ADD NEW TOKEN and enable the following permissions:

    1. Address

      1. address-geocode

      2. address-reverse-geocode

      3. address-verify

    2. Phone

      1. phone-verification

    3. Property

      1. property-lookup-all-attributes

        1. Enable all the datasets that you want to make available

      2. property-search

      3. property-skip-trace-v3

        1. Contact your Account Manager to enable access to the V3 Skiptrace API end-point.

Step 2: Install Node.js 22

Claude Desktop's bundled Node.js version is outdated. The BatchData MCP Server requires Node.js 22.

For macOS/Linux:

  1. Open Terminal

  2. Install Volta (Node.js version manager):

    curl https://get.volta.sh | bash
  3. Close and reopen Terminal

  4. Install Node.js 22:

    volta install node@22
  5. Find your username by running

    whoami 

    (you'll need this for Step 2)

For Windows:

  1. Download and install Node.js 22.x LTS from nodejs.org

  2. Note the installation path (typically C:\Program Files\nodejs)

  3. Restart your computer after installation

Step 3: Configure Claude Desktop

  1. Open Claude Desktop → Settings → Developer → Edit Config

  2. Add the following configuration to the JSON file:

For macOS:

{
"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_SERVER_SIDE_API_TOKEN_HERE"
}
}
}
}

For Linux:

{
"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_SERVER_SIDE_API_TOKEN_HERE"
}
}
}
}

For Windows:

{
"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_SERVER_SIDE_API_TOKEN_HERE"
}
}
}
}

Important:

  • Replace YOUR_USERNAME with your actual username

  • Replace YOUR_SERVER_SIDE_API_TOKEN_HERE with your BatchData API token

  • Adjust paths if you installed Node.js in a different location

  1. Save the file and restart Claude Desktop

  2. You should see "BatchData" in the extensions list

  3. Enable the server and select "Always Allow" when prompted for permissions

Verification: After setup, Claude will automatically detect and use BatchData tools when you ask real estate-related questions or request property data lookups.

You can confirm the installation by providing this prompt to Claude "What tools does the BatchData MCP server support?"


Questions? Contact our support team at support@batchservice.com or visit https://help.batchdata.io for more information.

Did this answer your question?