DataSignals Lab MCP server
Which servers in the official MCP registry are DataSignals Lab's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-19
- Registry namecom.datasignalslab/datasignals-events-mcpverified in the MCP registry
The registry name sits under datasignalslab.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Staterequires sign-inchecked 2026-10-19
On 2026-10-19 the server answered and asked for a sign-in with a DataSignals Lab account (OAuth). It shows its tool list only to signed-in users, so we list none here.
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer219 ms
- Sign-inOAuth: the client signs you in
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"datasignals-events-mcp": {
"type": "http",
"url": "https://mcp.apify.com/?tools=datasignalslab/datasignals-events-mcp"
}
}
}The first time it connects, the client opens a DataSignals Lab sign-in.
Also shipped through: pypi
- com.datasignalslab/datasignals-lab-events-mcpanswers, requires sign-inverified in the MCP registry
- com.datasignalslab/datasignals-lab-mcpanswers, requires sign-inverified in the MCP registry
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.