MCP.Market

RestoSignals MCP server

online · 100% uptime
by restosignals.com·com.restosignals/restosignals·v1.0.0

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

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed RestoSignals yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

RestoSignals tools (4)

write = sends, deletes, buys or posts
  • coverageFree

    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_openingsFree

    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_signalsFree

    Return the raw underlying signals (liquor/permit/business filings) that were fused into one venue, for transparency. 1 credit.

  • watch_areaFree

    Register a webhook that fires when a new matching venue opens in an area. criteria = {state, city, signal_type, min_opening_score}. Free.

Public scan report

scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 762ms20/20
  • Tool poisoning4 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 11 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How RestoSignals compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
176 ms
faster than 68% of 30,031 servers

What its tools let an agent do: 3 read · 1 create

Install RestoSignals in Claude Code, Cursor or VS Code

claude mcp add --transport http restosignals https://api.restosignals.com/mcp
Add to Cursor

What the publisher says

From the RestoSignals repository's README, as published. We do not edit it. Read it on GitHub

RestoSignals MCP — restaurants and bars before they open

Remote MCP server, REST API and agent skill for pre-opening restaurant leads in the US. RestoSignals fuses public liquor-license applications, food-service permits and new-business filings into one deduped venue, scores how close it is to opening (opening_score 0–100), and attaches the owner contact found in those filings.

Built for anyone who sells to new restaurants — POS and merchant-services resellers, beverage distributors, insurers, equipment suppliers — and for agents that prospect on their behalf.

  • MCP endpoint: https://api.restosignals.com/mcp (Streamable HTTP)
  • Auth: API key in X-API-Key (or Authorization: Bearer pk_...)
  • Free key: https://restosignals.com/signup (100 lead credits, no card)
  • Docs: https://restosignals.com/restoapi · OpenAPI: https://api.restosignals.com/openapi.json
  • Website: https://restosignals.com

Quick start

Add the server to Claude Desktop / Claude Code, Cursor, Windsurf or any MCP client:

{
  "mcpServers": {
    "restosignals": {
      "url": "https://api.restosignals.com/mcp",
      "headers": { "X-API-Key": "pk_YOUR_KEY" }
    }
  }
}

Claude Code one-liner:

claude mcp add --transport http restosignals https://api.restosignals.com/mcp --header "X-API-Key: pk_YOUR_KEY"

Then ask: "Which restaurants are about to open in New York? Strongest leads first."

Tools

Coverage

Live with hot leads: NY, TX, IL, CA, OR. CO and WA have venues but are still thin. Refreshed daily. Always call coverage for the current list; nothing outside it is claimed.

Contact depth (subscribers): owner name from the filing everywhere, owner mailing address in TX and NY, phone in NYC. Free keys see that a contact exists, not the contact itself.

Install as an agent skill / Claude Code plugin

This repo is also a Claude Code plugin marketplace with the restosignals skill:

/plugin marketplace add paperandbeyond23-gif/restosignals-mcp
/plugin install restosignals@restosignals

Or copy skills/restosignals/SKILL.md into your agent's skills folder.

REST

curl -s "https://api.restosignals.com/v1/openings?state=NY&min_opening_score=40&limit=5" \
  -H "X-API-Key: pk_YOUR_KEY"

Endpoints: /v1/openings, /v1/openings/latest, /v1/signals, /v1/export (CSV), /v1/webhooks, /v1/account. Full spec in the OpenAPI file.

Notes

Data comes from public government open-data. RestoSignals is not affiliated with any government agency. This repo holds the client config, skill and docs; the server is hosted.

License: MIT (this repo's contents).

Nothing above is checked by us. What we check is on the safety report.

RestoSignals: common questions

Is RestoSignals MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the RestoSignals safety report
How do I install RestoSignals?
It runs remotely at api.restosignals.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does RestoSignals need an API key?
Yes. The registry entry asks for X-API-Key.
Is RestoSignals maintained?
The last commit was 18 days ago (2026-10-17). The latest release is v1.0.0.
Is RestoSignals up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does RestoSignals compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.