Datasignals Lab Events MCP Server

Connect this server

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

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

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

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

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

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

This one needs environment variables set before it will start: DATASIGNALS_KEY (Your Events API key, starting with 'ds_live_'. Two tools (list_event_types, feed_health) work without one, so a client can inspect the data before subscribing. Plans, including a free tier, are at https://datasignalslab.com/events-api.html). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Endpoints