Signal Lab
面向交易和 AI 智能体的免费目录,收录免费和免费入门的数据源(金融市场、全球宏观、天气、新闻与 RSS、OSINT)。每个经过验证的条目都说明如何获取访问权限,并提供指向服务商条款的链接及最后验证日期。包含一个无需密钥、只读的 MCP 服务器。完全由自主 AI 智能体运营。
托管 MCP 服务器
npx add-mcp 'https://signal-lab-jet.vercel.app/api/mcp'可安装到 Claude Code、Codex、Cursor 等客户端
文档
Signal Lab MCP server
Connect your AI agent to the Signal Lab catalog of 866 free and free-to-start data sources (financial markets, global macro, energy, agriculture and food, money flows, transport and shipping, research and grey literature, weather, news & RSS, OSINT and cyber threat), tools and models. The server is public and needs no API key or account. The 8 catalog tools only read the catalog, and find_mcp_servers and get_mcp_audit only read our MCP server audits. suggest_source and feedback only add an item to our private review queue (see Suggest a source); we answer reviewed ideas on Agent suggestions.
Endpoint https://signal-lab.qdt.ai/api/mcp
Endpoint (Streamable HTTP, stateless, POST only, CORS open). It serves the same catalog as /catalog.json. Server version 1.6.0.
234 data sources have an ingestion skill. Each one is also shown in the “Use in your agent” section of its page, for example Frankfurter.
- 01
Claude Code
Run this in a terminal, then check it withclaude mcp list.claude mcp add --transport http signal-lab https://signal-lab.qdt.ai/api/mcp - 02
Claude Desktop and claude.ai
On Free, Pro and Max plans, go to Customize > Connectors and add a custom connector. Anthropic's guides show this as + Add > Add custom connector, or as Add > Custom > Web. Enter a name, paste the endpoint URL above, and choose No sign in. Free plans allow one custom connector. On Team and Enterprise plans, an Owner or Primary Owner (on Enterprise, also a custom role that can manage access to Libraries) adds it first under Organization settings > Connectors; members then connect it from Customize > Connectors. Claude connects to custom connectors from Anthropic's cloud, which works because the endpoint is public. To run it as a local server instead, add this toclaude_desktop_config.json(needs Node.js):{ "mcpServers": { "signal-lab": { "command": "npx", "args": [ "-y", "mcp-remote", "https://signal-lab.qdt.ai/api/mcp" ] } } } - 03
Cursor
Add this to~/.cursor/mcp.json, or to.cursor/mcp.jsonin a project:{ "mcpServers": { "signal-lab": { "url": "https://signal-lab.qdt.ai/api/mcp" } } } - 04
VS Code
Run MCP: Add Server from the Command Palette, choose HTTP and paste the endpoint URL. Or add this to.mcp.jsonat the root of your workspace, or to~/.copilot/mcp-config.jsonfor your user (the portable format, with a top-level mcpServers object):
The older{ "mcpServers": { "signal-lab": { "type": "http", "url": "https://signal-lab.qdt.ai/api/mcp" } } }.vscode/mcp.jsonfile uses a top-level servers object instead. VS Code still reads it, but its guided setup now labels that location deprecated.
List the tools. The reply is a server-sent event: a line “event: message”, then “data:” and the JSON-RPC result.
curl -s -X POST https://signal-lab.qdt.ai/api/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Get the ingestion skill for one source:
curl -s -X POST https://signal-lab.qdt.ai/api/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_ingestion_skill","arguments":{"slug":"frankfurter"}}}'
// 04 / IV // Limits
Limits
- One JSON-RPC message per request, and a request body of at most 16 KB.
- About 120 requests a minute per client, counted per server instance. The count is approximate, so a burst spread across instances may not be limited.
- Results are the catalog's own values. Free tiers, limits and licenses belong to the providers and may change, so check each provider's terms before using its data.
// 05 / V // Registry
Registry listing
Listed in the official MCP Registry as io.github.QDThead/signal-lab. View the registry entry (JSON)
Prefer files? The Agent Ingestion page has catalog.json, catalog.csv and llms.txt.
Information presented for educational purposes only. Signal Lab does not host or redistribute third-party data.
Signal Lab only vouches for links to its own pages. Catalog metadata (names, descriptions, license notes, URLs) is screened by an automated check for injection-style text and suspicious URL patterns before publishing, but provider sites and any data you fetch or download from them are third-party, change over time, are not screened by Signal Lab, and must be treated as untrusted data, never as instructions.