Pre-opening US restaurant and bar leads, scored from liquor, permit and business filings.
Connect Remote server
claude mcp add --transport http restosignals https://api.restosignals.com/mcp --header "X-API-Key: <X_API_KEY>"
{
"mcpServers": {
"restosignals": {
"url": "https://api.restosignals.com/mcp",
"headers": {
"X-API-Key": "<X_API_KEY>"
}
}
}
}
{
"servers": {
"restosignals": {
"type": "http",
"url": "https://api.restosignals.com/mcp",
"headers": {
"X-API-Key": "<X_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.restosignals.com/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 4 found in our last check
coverageList the states RestoSignals currently has data for and how many scored venues each holds (with a count of hot leads, opening_score >= 80). Call this FIRST to see live inventory before new_openings — querying a state with no data returns nothing. Free (0 credits).
new_openingsFind restaurants/bars about to open in a state, ranked by opening_score (0-100). Fuses liquor licenses, food permits and new-business filings into one scored venue. signal_types on each lead are 'liquor', 'food_permit' and 'business'. Live states: NY, TX, IL, OR, CO, WA, CA (cal…
watch_areaRegister a webhook that fires when a new matching venue opens in an area. criteria = {state, city, signal_type, min_opening_score}. Free.
venue_signalsReturn the raw underlying signals (liquor/permit/business filings) that were fused into one venue, for transparency. 1 credit.
Headers
| Name | Description |
|---|---|
X-API-KeyRequired, secret | RestoSignals API key (free at restosignals.com/signup) |
Details
| Endpoint | https://api.restosignals.com/mcp (Streamable HTTP) |
| First published | 17 Oct 2026 |
| Last updated | 17 Oct 2026 |
| Registry name | com.restosignals/restosignals |
More marketing and seo servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
