mcpbeat

Signals MCP Server

com.rivalsweeper/signals
answering

Signals is answering right now. Last checked 15 min ago. It exposes 7 tools.

Beta. Pay-per-call eCommerce competitive intel: pricing, promotions, history, AI-readiness.

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
120 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add signals --transport http https://mcp.rivalsweeper.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "signals": {
      "url": "https://mcp.rivalsweeper.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.signals]
url = "https://mcp.rivalsweeper.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "signals": {
      "url": "https://mcp.rivalsweeper.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "signals": {
      "url": "https://mcp.rivalsweeper.com/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

brand
get_brand_snapshot
Bundle: all current signals for one brand-day - promotions, price stats + samples, AI-readiness - in one call. 15 credits; no data = no charge.
competitor
get_competitor_price
Price statistics (min/max/avg/median) plus recent product samples for a brand, optionally filtered by product-name query. Freshness-stamped. 1 credit; no data = no charge.
coverage
get_coverage
Check which competitive signals RivalSweeper has for an eCommerce domain, with per-signal freshness. Free and non-billable - call this before any billable tool so you never pay for a domain we do not cover.
history
get_history
Monthly time-series of price changes (drops/rises/avg delta) or stock-status flips for a brand. Depth-tiered: up to 3 months = 5 credits, 4-12 months = 8, 13-24 months = 13. No data = no charge.
promotions
get_promotions
Active promotions/discount codes for a brand: code, discount type/value, min order, validity window. Freshness-stamped. 1 credit; no data = no charge.
readiness
get_readiness_score
RivalSweeper 6-pillar AI/agent-readiness score for a domain (schema.org, technical access, content quality, trust, AI-specific, entity recognition) with tier and highlights. Uniquely RivalSweeper data. 1 credit; no data = no charge.
request
request_monitoring
Ask RivalSweeper to add a domain to monitoring. Free, but requires an account with a positive prepaid balance. First data typically lands within 24-72h.

Endpoints

URLTransportStateLatencyChecked
https://mcp.rivalsweeper.com/mcp streamable-http answering 120 ms 15 min ago

Signals — questions

Answers built from our own checks of this server.

What can Signals do?
It exposes 7 tools, read directly from the server on our last check. Among them: get_brand_snapshot, get_competitor_price, get_coverage, get_history, get_promotions, get_readiness_score and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Signals working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 120 ms. The bar chart above shows every period we have measured.
How do I connect Signals?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Signals need an API key?
No. Signals completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Signals?
It answers our handshake in 120 ms on average, which is faster than 80% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.