Skip to content

RestoSignals

by restosignals.com · remote · no sign-in to list tools · v1.0.0 · published by com.restosignals

Pre-opening US restaurant and bar leads, scored from liquor, permit and business filings.

Changes · 1
CompareRegistry entry

4 tools: 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http restosignals https://api.restosignals.com/mcp --header 'X-API-Key: <your-x-api-key>'

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 1Claude Code: ask
  • watch_areaRegister a webhook that fires when a new matching venue opens in an area.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Register a webhook that fires when a new matching venue opens in an area. criteria = {state, city, signal_type, min_opening_score}. Free.
Only reads 3Claude Code: allow
  • coverageList the states RestoSignals currently has data for and how many scored venues each holds (with a count of hot leads, opening_score >= 80).No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List 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).No findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    Description, as the server wrote it
    Find 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 (call `coverage` for the current list). 1 credit per returned lead.
  • venue_signalsReturn the raw underlying signals (liquor/permit/business filings) that were fused into one venue, for transparency.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the raw underlying signals (liquor/permit/business filings) that were fused into one venue, for transparency. 1 credit.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http restosignals https://api.restosignals.com/mcp --header 'X-API-Key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__restosignals__coverage",
      "mcp__restosignals__new_openings",
      "mcp__restosignals__venue_signals"
    ],
    "ask": [
      "mcp__restosignals__watch_area"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as restosignals. Review it before you use it.