Koskamo

ListSignal MCP MCP server

ListSignal provides a native MCP server for B2B sales intelligence, allowing AI agents to access data on over 14 million online businesses. It enables retrieval of full company records including tech stacks, revenue estimates, hiring signals, and contact information, as well as searching for companies by specific technologies or criteria and monitoring real-time changes in business attributes.

Endpoint and access

API key: create a key with the vendor first; your client sends it as an authorization header on every request.

API keyEndpoint checked 2026-10-05Operated by Keybloc Pte Ltd
MCP endpoint (Streamable HTTP)
https://listsignal.com/mcp
Vendor documentation

What you can do with it

  • Retrieve full company records including tech stacks and revenue estimates
  • Search for companies by technology, country, or hiring status
  • Monitor real-time changes in business attributes like tech additions
  • Access live dataset statistics and tracked field definitions

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http listsignal-mcp https://listsignal.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add listsignal-mcp --url https://listsignal.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable listsignal-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "listsignal-mcp": {
      "url": "https://listsignal.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "listsignal-mcp": {
      "type": "streamableHttp",
      "url": "https://listsignal.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start listsignal-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "listsignal-mcp": {
      "type": "http",
      "url": "https://listsignal.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http listsignal-mcp https://listsignal.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "listsignal-mcp": {
      "url": "https://listsignal.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "listsignal-mcp": {
      "serverUrl": "https://listsignal.com/mcp"
    }
  }
}

Do you run ListSignal MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing