Health · Remote MCP server

Datasignals Lab MCP

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

Visit Datasignals Lab MCP's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
com.datasignalslab/datasignals-lab-mcp
Version
1.7.0
Status
Active
Category
health
Transport
Streamable HTTP
Published
2026-09-13
Updated
2026-09-13
Publisher
com.datasignalslab · 2 servers with pages here
Namespace
Namespace verified by the MCP Registry via the domain datasignalslab.com · how
Website
datasignalslab.com
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.apify.com/?tools=datasignalslab/datasignals-mcpAuthorization (required, secret)
Streamable HTTPhttps://datasignalslab--datasignals-mcp.apify.actor/mcpAuthorization (required, secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Endpoint
https://mcp.apify.com/?tools=datasignalslab/datasignals-mcp (HTTP)
Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; a Bearer token is asked for
Checked on
2026-10-05
Endpoint
https://datasignalslab--datasignals-mcp.apify.actor/mcp (HTTP)
Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401
Checked on
2026-10-05

How the live check works

How to connect Datasignals Lab MCP

Datasignals Lab MCP is a remote MCP server: there is nothing to install. Its endpoints are https://mcp.apify.com/?tools=datasignalslab/datasignals-mcp and https://datasignalslab--datasignals-mcp.apify.actor/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from com.datasignalslab

All 2 →
ServerRunsEndpoint or package
Datasignals Lab Events MCPTwelve US filing and career-site streams in one schema: SEC, FDA, NIH, contracts, Congress, hiring.Remote & Local · HTTP, stdioLive check: sign-in requiredmcp.apify.com

More health servers

All 381 →
ServerRunsEndpoint or package
DailymedDailyMed MCP - FDA Structured Product Labels via NLM.Remote · HTTPLive check: ✓ handshakegateway.pipeworx.io
DailymedSearch DailyMed drug labels, SPLs, NDCs and packaging.Remote · HTTPLive check: ✓ handshakedailymed.usefulapi.io
Dailymed MCPFDA drug label information from DailyMed. No key required.Local · stdionpm: dailymed-mcp
DeepDNACited gene, variant (rsID) and CPIC drug-gene lookups for AI agents. Read-only, no key.Remote · HTTPLive check: ✓ handshakedeepdna.ai
DICOM/HL7/FHIR Interoperability MCP ServerBridges DICOM, HL7v2, and FHIR with cross-standard mapping and optional PACS connectivity.Local · stdioPyPI: dicom-hl7-mcp
DietBoxPatient, prescription, anthropometry, scheduling, chat and food diary management for dietitians.Remote · HTTPLive check: ✓ handshakeapi.mcp.ai
Dingdawg Healthcare AgentHIPAA-aware healthcare AI. Clinical documentation, compliance checks, audit prep. Free local tier.Local · stdionpm: dingdawg-healthcare-agent