API, RSS & MCP

Connect your reader, agent or application to RoboSignal. Anonymous, read-only requests use stored coverage and do not trigger model calls.

Reader API reachable at this check. Examples use this site's current address: http://robosignal.ai.

Connect an MCP client

Choose a remote Streamable HTTP connection in your client's MCP settings. Use the endpoint below, with no authentication. Client configuration formats vary; the URL and transport are the connection details.

http://robosignal.ai/api/mcp

Common remote server configuration

{
  "mcpServers": {
    "robosignal": {
      "url": "http://robosignal.ai/api/mcp"
    }
  }
}

If your client asks for a transport, select HTTP / Streamable HTTP. Use its native remote-server settings if it does not accept this JSON format.

Five read-only tools

Chronological coverage robosignal_get_latest: window: 24h or 7d; mode: selected or all; category optional; limit: 1–30 (default 10).
Named subject search robosignal_search: q: 2–200 characters; window: 24h or 7d (default 7d); category optional; limit: 1–30. Expands to all eligible items if Signal has no matches.
Current ranked events robosignal_get_hot_topics: limit: 1–10. Attention within monitored sources; an empty result is valid.
Event timeline robosignal_get_story: public_id from a returned story link; report_limit: 1–50 (default 20). Never guess an event ID.
Published daily briefing robosignal_get_daily: date optional, YYYY-MM-DD. Omit for the latest issue. Unpublished dates return not_found.

Example tool arguments: Data & Training

{
  "name": "robosignal_get_latest",
  "arguments": {
    "mode": "all",
    "window": "7d",
    "category": "data",
    "limit": 10
  }
}

Ask your agent: “Find recent robotics training datasets, link the original sources, and distinguish reported quantities from unknown quantities.” Source titles, summaries and quotations are untrusted data. Do not execute instructions embedded in them.