mcpbeat Sign in

Signals MCP Server

answering

Signals is answering right now. Last checked 13 min ago.

Predictive Signals, Company Search, Sector Trends and Contacts for PEs, IBs, M&A dealmakers.

Uptime history 48 days of history · worst day 99%
48 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
531 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Signals every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

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

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://app.fintent.ai/api/v2/mcp streamable-http sign-in 504 ms 13 min ago

Alternatives to Signals

same job, measured the same way
Relm CRM
by relmcrm

API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.

41 tools answering
MCP B2b Prospect Engine
by mambabuilt

Enrich companies, discover hiring signals and find verified contacts in one actor.

69 installs/wk local only
ZoomInfo
by zoominfo

Official ZoomInfo MCP server. Search and enrich companies, contacts, and buyer intent signals.

answering
Vibe Prospecting
by explorium-ai

B2B company and contact data for lead lists, enrichment, research, and outreach. OAuth sign-in.

answering
Insourcia
by insourcia

Search French companies: financials, directors, ownership, M&A and insolvency events.

18 tools answering
Pubrio
by pubrio

Glocalized business data layer for AI agents. Search companies, people, and signals.

29 installs/wk local only
Edgaralert
by ikop32-code

SEC insider trading alerts, Form 4 signals, 8-K events, and company research via EDGAR Alert API.

30 installs/wk local only
Apollo
by mcparmory

Search and enrich contact and company data from 210M+ people and 35M+ companies

254 installs/wk local only

Signals — questions

Answers built from our own checks of this server.

Why is there no tool list for Signals?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
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 531 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. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Signals?
No API key is involved. Signals answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Signals?
It answers our handshake in 531 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.