SERVER

Datasignals Lab MCP Server

Rank #39,197

com.datasignalslab/datasignals-lab-mcp

Hiring signals, SEC, Congress, FDA, crypto and app reviews: scored signals. 19 tools, free flagship.

8 versions

First listed

Jun 16, 2026

Last publish date

Sep 13, 2026

PURPOSE

What you can do with Datasignals Lab MCP Server

Datasignals Lab MCP Server is a Model Context Protocol (MCP) server. It ranks #39,197 of 150,963 active servers on MCP Toplist. Datasignals Lab MCP Server is listed on Official MCP, with 8 tracked versions. It was first listed on Jun 16, 2026 and most recently updated on Sep 13, 2026.

Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. Its registry listings below are the authority on what it does.

CAPABILITIES AND LIMITATIONS

What Datasignals Lab MCP Server can and cannot do

Not verifiedMCP Toplist has not catalogued this server's tools or limitations. Check its registry listings below.

REQUIREMENTS

What you need before using Datasignals Lab MCP Server

DeclaredRemote authHosted remote, sign-in declared

The hosted endpoint is declared as gated by authentication — connect via its URL and authenticate with the provider (OAuth flow or an API key/header, per its docs).

Declared by the Official MCP Registry, last synced Oct 22, 2026. Not independently verified by MCP Toplist.

Declared in the registry install config

2 hosted endpoints declared as requiring authentication.

INSTALLATION AND FIRST TASK

Connect Datasignals Lab MCP Server and confirm it works

Remote · HTTP

claude mcp add --transport http datasignals-lab-mcp https://mcp.apify.com/?tools=datasignalslab/datasignals-mcp

This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

claude mcp add --transport http datasignals-lab-mcp https://datasignalslab--datasignals-mcp.apify.actor/mcp

This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

[mcp_servers.datasignals-lab-mcp]
url = "https://mcp.apify.com/?tools=datasignalslab/datasignals-mcp"

Add to ~/.codex/config.toml. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

[mcp_servers.datasignals-lab-mcp]
url = "https://datasignalslab--datasignals-mcp.apify.actor/mcp"

Add to ~/.codex/config.toml. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

https://mcp.apify.com/?tools=datasignalslab/datasignals-mcp

Settings → Connectors → “Add custom connector”, then paste this URL. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

https://datasignalslab--datasignals-mcp.apify.actor/mcp

Settings → Connectors → “Add custom connector”, then paste this URL. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "mcpServers": {
    "datasignals-lab-mcp": {
      "url": "https://mcp.apify.com/?tools=datasignalslab/datasignals-mcp"
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "mcpServers": {
    "datasignals-lab-mcp": {
      "url": "https://datasignalslab--datasignals-mcp.apify.actor/mcp"
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "servers": {
    "datasignals-lab-mcp": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=datasignalslab/datasignals-mcp"
    }
  }
}

Save as .vscode/mcp.json in your workspace. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "servers": {
    "datasignals-lab-mcp": {
      "type": "http",
      "url": "https://datasignalslab--datasignals-mcp.apify.actor/mcp"
    }
  }
}

Save as .vscode/mcp.json in your workspace. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "mcpServers": {
    "datasignals-lab-mcp": {
      "serverUrl": "https://mcp.apify.com/?tools=datasignalslab/datasignals-mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "mcpServers": {
    "datasignals-lab-mcp": {
      "serverUrl": "https://datasignalslab--datasignals-mcp.apify.actor/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "mcpServers": {
    "datasignals-lab-mcp": {
      "url": "https://mcp.apify.com/?tools=datasignalslab/datasignals-mcp"
    }
  }
}

This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "mcpServers": {
    "datasignals-lab-mcp": {
      "url": "https://datasignalslab--datasignals-mcp.apify.actor/mcp"
    }
  }
}

This endpoint requires authentication — see the server’s docs for credentials.

First successful task

After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.

MAINTENANCE AND EVIDENCE

What changed, and when this was checked

First listed: Jun 16, 2026
Latest version published: Sep 13, 2026
Version history: 8 versions tracked (below)
Requirements evidence: Declared by the Official MCP Registry, last synced Oct 22, 2026. Not independently verified by MCP Toplist.
Profile checked: Not yet — purpose, capabilities and requirements above come from registry data only
Ranking data as of: Sep 13, 2026

Registry sightings

Official MCP ↗listed since Jul 19, 2026 · still listed

Do you maintain Datasignals Lab MCP Server? to correct or enrich this profile.

VERSIONS

Available versions (8)

Version	Published
1.7.0	Sep 13, 2026
1.6.0	Aug 4, 2026
1.5.0	Jul 25, 2026
1.4.1	Jul 19, 2026
1.4.0	Jul 15, 2026
1.3.0	Jul 12, 2026
1.1.0	Jun 23, 2026
1.0.0	Jun 16, 2026

STANDING

#39,197of 150,963 active serversTop 50%

Ranks ahead of 111,766 of 150,963 servers on MCP Toplist.

BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

Markdown

[![MCP Toplist](https://mcptoplist.com/badge/com.datasignalslab%2Fdatasignals-lab-mcp.svg)](https://mcptoplist.com/server/com.datasignalslab%2Fdatasignals-lab-mcp)

HTML

<a href="https://mcptoplist.com/server/com.datasignalslab%2Fdatasignals-lab-mcp"><img src="https://mcptoplist.com/badge/com.datasignalslab%2Fdatasignals-lab-mcp.svg" alt="MCP Toplist: Top 50% of 150,963" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

FAQ

Frequently asked questions

Is Datasignals Lab MCP Server listed on the Official MCP Registry?: Yes — Datasignals Lab MCP Server is listed on the Official MCP Registry.
How many versions does Datasignals Lab MCP Server have?: MCP Toplist tracks 8 versions of Datasignals Lab MCP Server, most recently published on Sep 13, 2026.

Used in projects

Do you run this server?

Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.

EXPLORE

All MCP Servers Official MCP Servers Best MCP Servers Most Active MCP Servers New MCP Servers Best New MCP Servers