Data Collection
businesschanges.dev
Provides access to business change leads, event evidence, location timelines, delta feeds, and coverage metadata for tracking business changes.
ENDPOINT 1
https://api.businesschanges.dev/mcp
MCP server metadata
- Name
- business-change-intelligence
- Version
- 1.0.0
Use these read-only tools to research evidence-backed business changes across supported jurisdictions. Start with compact lead search, expand only selected event IDs into primary-source evidence, and inspect coverage before treating no-match as no activity. Effective time is when an event happened; observed time is when this platform learned it. Preserve exact suites by default. Request building scope only when the user wants all premises at one property. Opening signals are leads, not proof of public opening; use publicStatus and evidence before making that claim. Find restaurant opening leads in Orlando observed this month. -> find_business_change_leads({"jurisdictions":["US-FL"],"geography":{"cities":["Orlando"]},"intents":["opening_leads"],"industries":["restaurant"],"observedAfter":"2026-07-01T00:00:00.000Z","projection":"compact","limit":25}) Show everything newly discovered since my previous run. -> get_changes_since({"cursor":"<cursor from previous response>","limit":50}) Verify these three leads with their original public records. -> get_business_event_evidence({"eventIds":["<event uuid 1>","<event uuid 2>","<event uuid 3>"]})
Known tools 5
find_business_change_leadsFind previously unknown businesses or locations with recent license, permit, inspection, ownership, opening, closure, or tenant-transition signals.
Inferred read-onlyget_business_event_evidenceExpand selected business event IDs into dated, versioned primary-source evidence.
Inferred read-onlyget_location_timelineRetrieve chronological business-change events for an exact premises or, when explicitly requested, its parent building.
Inferred read-onlyget_changes_sincePoll a compact, stable delta feed of events first observed since a timestamp or prior cursor, including superseded and retracted events.
Inferred read-onlyget_business_change_coverageInspect supported sources, jurisdictions, freshness, successful collection windows, and known limitations before interpreting a result or no-match.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.business-change-intelligence]
url = "https://api.businesschanges.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"business-change-intelligence": {
"type": "http",
"url": "https://api.businesschanges.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: business-change-intelligence
Remote MCP URL: https://api.businesschanges.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"business-change-intelligence": {
"url": "https://api.businesschanges.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"business-change-intelligence": {
"type": "http",
"url": "https://api.businesschanges.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "business-change-intelligence",
"transport": "streamable-http",
"url": "https://api.businesschanges.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.