Signal Lab

officiel

Serveur MCP hébergé donnant accès à plus de 500 sources de données gratuites (marchés, macroéconomie, météo, OSINT), avec des informations sur l’accès, les limites de débit, les licences et les dates de vérification. Aucune clé requise.

Que pouvez-vous faire avec Signal Lab MCP ?

  • Search the data catalog — Ask your assistant to find free or free-to-start data sources across markets, macro, energy, agriculture, shipping, weather, news, OSINT and more.
  • Get a source's ingestion skill — Retrieve the documented ingestion skill for any of the 234 sources that have one, such as Frankfurter, via get_ingestion_skill.
  • Review MCP server audits — Look up Signal Lab's MCP server audits to compare servers before choosing one for your agent.
  • Suggest a source — Have your assistant submit a data source idea to Signal Lab's private review queue for consideration.
  • Send feedback — Pass along feedback on the catalog through the server without needing an account or API key.

Serveur MCP hébergé

npx add-mcp 'https://signal-lab.qdt.ai/api/mcp'

S’installe dans Claude Code, Codex, Cursor et plus

Documentation

Signal Lab MCP server

Connect your AI agent to the Signal Lab catalog of 913 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.

  1. 01

    Claude Code

    Run this in a terminal, then check it with claude mcp list.
    claude mcp add --transport http signal-lab https://signal-lab.qdt.ai/api/mcp
    
  2. 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 to claude_desktop_config.json (needs Node.js):
    {
      "mcpServers": {
        "signal-lab": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://signal-lab.qdt.ai/api/mcp"
          ]
        }
      }
    }
    
  3. 03

    Cursor

    Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:
    {
      "mcpServers": {
        "signal-lab": {
          "url": "https://signal-lab.qdt.ai/api/mcp"
        }
      }
    }
    
  4. 04

    VS Code

    Run MCP: Add Server from the Command Palette, choose HTTP and paste the endpoint URL. Or add this to .mcp.json at the root of your workspace, or to ~/.copilot/mcp-config.json for your user (the portable format, with a top-level mcpServers object):
    {
      "mcpServers": {
        "signal-lab": {
          "type": "http",
          "url": "https://signal-lab.qdt.ai/api/mcp"
        }
      }
    }
    
    The older .vscode/mcp.json file 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.