In-depth architectural comparison of the Public Tools and Disruption Intelligence MCP 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
Public Tools
Real Estate · Remote HTTP/SSE
Quality: 44/100 (Fair) | Auth: No auth required
Disruption Intelligence MCP
Real Estate · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Public Tools if you need specialized Real Estate tools running via a hosted cloud SSE transport. Choose Disruption Intelligence MCP 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 Public Tools when:
You need dedicated capabilities in the Real Estate domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
French rental tools: create & e-sign a lease, rent control, IRL, deposit, receipts (France).
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.
Public Tools is categorized under Real Estate and uses a remote streaming HTTP/SSE transport. In contrast, Disruption Intelligence MCP belongs to Real Estate using local stdio subprocess. Select Public Tools when you need capabilities focused on real estate and Disruption Intelligence MCP when you require tools for real estate.
Create a lease draft → returns a link to finalize & **e-sign** it (advanced eIDAS, PAdES-B-LT) on FairePlace
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.
get_company_risk_summary
Thin wrapper for GET /companies/:id/intelligence. Paid endpoint; returns x402 challenge in default non-settling mode.
get_event_severity
Thin wrapper for GET /events/:id/severity. Paid endpoint; enriched paid responses include industry_classification with method, confidence, and coverage_note. Returns x402 challenge in default non-settling mode.
get_event_company_intel
Thin wrapper for GET /events/:id/company-intel. Paid endpoint; enriched paid responses include event industry_classification with method, confidence, and coverage_note. Returns x402 challenge in default non-settling mode.
get_event_timeline
Thin wrapper for GET /events/:id/timeline. Paid endpoint; returns x402 challenge in default non-settling mode.
search_gold_inventory
Compatibility tool for free inventory-only Ripple Signal search. Returns counts and unlock pricing without revealing signal details.
get_ripple_index
Thin wrapper for GET /ripple/index. Paid endpoint currently priced at $0.01; returns location-only Ripple index cards with signal IDs, bands, and unlock URLs while withholding companies, employee counts, commercial angles, and impact paths.
get_gold_signals
Compatibility tool for GET /ripple/signals. Paid endpoint currently priced at $0.10; returns Ripple Signals and Ripple Path inventory, challenge-first by default.
+2 more tools listed on main page
Disruption Intelligence MCP vs Dealflowpro MCP Server