mcpbeat Sign in

Signals MCP Server

answering

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

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

Uptime history 91 days of history · worst day 97%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
442 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 11 min ago.

run in your terminal
claude mcp add signals --transport http https://app.fintent.ai/api/v2/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "signals": {
      "type": "http",
      "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 513 ms 11 min ago

Alternatives to Signals

same job, measured the same way
Datamagnet
by datamagnet

Live LinkedIn people, company, post and job data, ICP search and job-change signals for AI agents.

answering
Xevol
by xevol

Search and read your Xevol contacts, companies and deals from your AI agent.

answering
Relm CRM
by relmcrm

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

41 tools answering
b2bsearch: B2B contacts and account signals
by keyvwin

B2B contacts and account signals on Apify: new hires, email format, lookalikes, decision makers.

358 installs/wk local only
b2bsearch: B2B contacts and account signals
by b2bsearch

B2B contacts and account signals on Apify: new hires, email format, lookalikes, decision makers.

local only
R
Resolve402
by charleskremer-hub

French directors, NACE company search (FR, NO, FI), KYB checks, contacts, hiring signals, x402.

87 installs/wk local only
Clef: Businesses for Sale
by tryclef

Search 125,000+ businesses for sale with financials and broker contacts. Requires Clef Dealmaker.

answering
Signal Tools
by craft-agent

Signal tools for coding agents: chats, messages, contacts, received files and sends.

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 442 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 in the form 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 442 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.