What is the key difference between Disruption Intelligence MCP and Realestateapi?

Disruption Intelligence MCP belongs to the Real Estate category with local stdio execution, while Realestateapi belongs to the Real Estate category with local stdio execution.

How do I install Disruption Intelligence MCP or Realestateapi in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Disruption Intelligence MCP and Realestateapi free or paid?

Disruption Intelligence MCP operates under a Free / Open Source model (No auth required). Realestateapi operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Disruption Intelligence MCP lists 14 tools with 2 views and 1 GitHub stars. Realestateapi lists 3 tools with 0 views and 0 GitHub stars.

Can I use both Disruption Intelligence MCP and Realestateapi together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Disruption Intelligence MCP vs Realestateapi

In-depth architectural comparison of the Disruption Intelligence MCP and Realestateapi MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Disruption Intelligence MCP

Real Estate · Local stdio

Quality: 63/100 (Good) | Auth: No auth required

Realestateapi

Real Estate · Local stdio

Quality: 53/100 (Good) | Auth: No auth required

Verdict Summary: Choose Disruption Intelligence MCP if you need specialized Real Estate tools running via a local process. Choose Realestateapi if your workspace requires Real Estate integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Disruption Intelligence MCP when:

You need dedicated capabilities in the Real Estate domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: DISRUPTION_API_BASE.
Primary tools included: get_api_status, get_discovery_metadata, inspect_x402_challenge.

Explore Disruption Intelligence MCP Details

Choose Realestateapi when:

You need dedicated capabilities in the Real Estate domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: realestateapi_property_search, realestateapi_property_detail, realestateapi_skip_trace.

Feature & Specification Comparison

Specification	Disruption Intelligence MCP forgemeshlabs Real Estate	Realestateapi Real Estate
Summary	AI-native commercial disruption intelligence for MCP clients and x402-powered agents. Supports WARN/layoff intelligence, company context, geospatial territory disruption, and x402 payment challenge inspection via the hosted Forgemesh API.	RealEstateAPI MCP — property search, detail, and skip-trace (realestateapi.com)
Category & Scope	Real Estate

Tools & Capabilities Breakdown

Disruption Intelligence MCP Tools (14)

get_api_status

Check the hosted Disruption Intelligence API health endpoint. Free.

get_discovery_metadata

Fetch free discovery metadata from index.json, llms.txt, openapi.json, and x402 well-known metadata. Free.

inspect_x402_challenge

Make an unpaid request to a paid endpoint and return the structured x402 payment challenge. Does not settle payment.

analyze_territory_disruption

Thin wrapper for GET /territory/:zip/disruption?radius=. Paid endpoint; returns x402 challenge in default non-settling mode.

search_company_context

Thin wrapper for GET /companies/search?q=. Paid endpoint; returns x402 challenge in default non-settling mode.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Disruption Intelligence MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "forgemeshlabs-disruption-intelligence-mcp": {
      "command": "npx",
      "args": [
        "@forgemeshlabs/disruption-intelligence-mcp"
      ],
      "env": {
        "DISRUPTION_API_BASE": "YOUR_DISRUPTION_API_BASE_HERE"
      }
    }
  }
}

Realestateapi Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "realestateapi": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-realestateapi"
      ]
    }
  }
}

Frequently Asked Questions

Disruption Intelligence MCP is categorized under Real Estate and uses a local stdio subprocess. In contrast, Realestateapi belongs to Real Estate using local stdio subprocess. Select Disruption Intelligence MCP when you need capabilities focused on real estate and Realestateapi when you require tools for real estate.

More alternatives to Disruption Intelligence MCP More alternatives to Realestateapi Real Estate category hub