{
  "markdown": "# DataSignals Events MCP server\n\n<!-- mcp-name: com.datasignalslab/datasignals-lab-events-mcp -->\n\nAsk an AI assistant about US regulatory filings and have it answer from the\nfilings themselves, with a link back to each one.\n\nThis is a small MCP server that runs on your own machine and talks to the\n[DataSignals Events API](https://datasignalslab.com/events-api.html) with your\nkey. Twelve streams in one schema: insider buying clusters, planned insider sales\n(Form 144), activist stakes (13D/G), institutional holdings (13F), material\ncorporate events (8-K), private capital raises (Form D), FDA actions, biotech\ntrial catalysts, NIH grants, federal contract awards and congressional trades.\n\nThere is nothing to sign up for beyond the API key you already have, and nothing\nis billed twice: a call here spends one thing, the monthly event allowance on\nyour plan.\n\n## Install\n\n```bash\npip install datasignals-events-mcp\n```\n\n## Configure your client\n\nAdd this to your MCP client configuration, with your own key. In Claude Desktop\nthe file is `claude_desktop_config.json`; Cursor, Zed and the others use the same\nshape.\n\n```json\n{\n  \"mcpServers\": {\n    \"datasignals-events\": {\n      \"command\": \"datasignals-events-mcp\",\n      \"env\": {\n        \"DATASIGNALS_KEY\": \"ds_live_your_key_here\"\n      }\n    }\n  }\n}\n```\n\nRestart the client. Ask it to run `check_setup` and it will tell you whether the\nkey is configured and whether the feed answers.\n\nNo key yet? Two of the tools, `list_event_types` and `feed_health`, work without\none, so you can see the shape of the data and how fresh it is before you decide.\nPlans, including a free one, are at\n<https://datasignalslab.com/events-api.html>.\n\n## What you can ask\n\nThe tools are built around questions rather than endpoints:\n\n| Tool | Answers |\n|---|---|\n| `search_events` | \"Which FDA actions this week scored above 70?\" |\n| `company_events` | \"What has been filed on NVDA lately, across all streams?\" |\n| `get_event` | \"Show me everything on this one event.\" |\n| `list_event_types` | \"Which fields does the Form D stream actually carry?\" |\n| `feed_health` | \"How current is this data right now?\" |\n| `usage` | \"How much of my allowance is left, and when does it reset?\" |\n| `check_setup` | \"Is this thing configured correctly?\" |\n\nEvery record carries the URL of the filing it was parsed from. Where a record has\na score, it also carries the terms that score was built from and a flag saying\nwhether those terms were complete; when a term is missing from the published\nsource that flag is `false` rather than a number being invented.\n\n## Honest limits\n\n- **Not real time.** Sources refresh once a night, congressional trades weekly\n  and 13F quarterly, because that is how often they are published. The freshest\n  an event can be is this morning's round.\n- **Published filings only.** The archive holds what was published, not\n  everything a source ever had.\n- **Not investment advice.** This is data for research and monitoring.\n\n## Environment variables\n\n| Variable | Meaning |\n|---|---|\n| `DATASIGNALS_KEY` | Your API key, starting with `ds_live_`. Required for everything except `list_event_types` and `feed_health`. |\n| `DATASIGNALS_BASE_URL` | Override the API base URL. You will not normally need this. |\n\nThe key is sent as an `Authorization` header and never as a query parameter, so\nit does not end up in server logs or browser history. Keep it server-side;\nanyone holding it can spend your allowance.\n\n## Development\n\n```bash\npython3 -m venv .venv\n.venv/bin/pip install -e . pytest\n.venv/bin/python -m pytest tests -q\n```\n\nThe tests use a mock transport and never touch the network, except for the\nhandshake tests, which start the server for real and speak MCP to it over stdio\nagainst a deliberately unreachable endpoint.\n\n## Support\n\n<support@datasignalslab.com>, or the quickstart at\n<https://datasignalslab.com/events-api-quickstart.html>.\n\nMIT licensed.",
  "bytes": 3914,
  "sha": "0ff7f0a4284c32504165549101f0f525dae2e9f1877e5a77a2f59f01670667bc",
  "repo_slug": "",
  "fonte": "pypi",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_com_datasignalslab_datasignals_lab_event_45ecf1e1/readme"
}