Skip to content

RestoSignals MCP server

com.restosignals/restosignalsrestosignals.comstreamable-httpv1.0.0Scanned

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

4 tools: 1 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 1 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RestoSignals MCP server can do

The RestoSignals MCP server is published by restosignals.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: watch_area), but cannot delete data. 3 tools only read.

1 tool can send data out of your system (watch_area).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

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

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    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 3Show 3 read-only tools
  • 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:45 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.restosignals.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.restosignals.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.restosignals.com/mcp: tools/list returned 5 tools to an anonymous client, including watch_area (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Protocol version: 2024-11-05 to 2025-06-18
    • RFC 9728 protected resource metadata: none to https://api.restosignals.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://api.restosignals.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Protocol version: 2024-11-05 -> 2025-06-18; RFC 9728 protected resource metadata: none -> https://api.restosignals.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://api.restosignals…View diff
    • Protocol version: 2024-11-05 to 2025-06-18
    • RFC 9728 protected resource metadata: none to https://api.restosignals.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://api.restosignals.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

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>'
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as restosignals. Review it before you use it.

Capability tags behind 1 rule
  • mcp__restosignals__watch_area outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.restosignals/restosignals/verify?hash=2d9be8da893ab3eb8e67cb1d70a134626141068acb668d9ea2d01647aede2d50" | jq -e '.changed == false'

Pinned hash 2d9be8da893a, from Nov 11, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.restosignals/restosignals/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.restosignals/restosignals
[![Anlyon Radar](https://radar.anlyon.com/badge/com.restosignals/restosignals.svg)](https://radar.anlyon.com/servers/com.restosignals/restosignals)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:02 UTC.

RestoSignals MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RestoSignals MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RestoSignals MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RestoSignals MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the RestoSignals MCP server have?

4 tools: 1 write, 3 read. watch_area, coverage, new_openings and venue_signals.

Does the RestoSignals MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RestoSignals MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): watch_area.

Has the RestoSignals MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.