Funding Signals

official

Sales signals from every funding round

What can you do with Funding Signals MCP?

  • Query recent funding rounds — Ask your assistant for the latest funding events, returned newest first, with company, website, LinkedIn, amount, currency, and stage.
  • Filter by date range — Request funding events recorded between two UTC dates, inclusive.
  • Filter by amount range — Narrow results to events within a minimum and maximum funding amount in whole currency units.
  • Page through results — Retrieve later pages of funding events, up to 100 per page and through the first 10,000 events.

Hosted MCP Server

npx add-mcp 'https://api.tadasignals.com/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

What Tadasignals is and how to get funding events into your tools. The API works without a sign-up.

About

Tadasignals

Tadasignals is a free feed of funding rounds. Our signals engine collects funding events: the company, its website and LinkedIn page, and the amount raised. New events show up in the feed as soon as the engine saves them.

  • Website

    Browse the live feed and search the archive on the recent rounds page.
  • API

    Request funding events over HTTP. No sign-up needed.
  • MCP

    Let your AI assistant query the same data as the API.
  • Webhooks

    Get each new funding event sent to your endpoint.

The service is free. It shows what our team can do with data collection. If you need signals about other events, tell us and we will build custom signals for you.

API

No sign-up needed

Request

Send a GET request to get the latest funding events. No key is needed:

https://api.tadasignals.com/v1/fundings

Query parameters

All parameters are optional. Combine any of them:

q

Search in company names and domains, case-insensitive.

date_from, date_to

Dates in UTC, YYYY-MM-DD, both inclusive.

currency

Three-letter currency code, e.g. USD.

min_amount, max_amount

Amounts in whole currency units, both inclusive. Amounts are not converted between currencies, so set currency too.

sort

Sort order: -created_at (newest first, the default), created_at (oldest first), -funding_amount (highest amount first) or funding_amount (lowest amount first). Events without an amount come last.

page, page_size

Page number, starting at 1. Page size is 20 by default, 100 at most. You can page through the first 10,000 events.

https://api.tadasignals.com/v1/fundings?currency=USD&min\_amount=10000000&date\_from=2026-10-01

Headers

Log in to get a free API key and higher limits. Send the key in the X-Account-Token header, without a Bearer prefix:

X-Account-Token: YOUR_API_KEY

Example request

curl -H "X-Account-Token: YOUR_API_KEY" \
  "https://api.tadasignals.com/v1/fundings?page=1"

Rate limits

Without a key: 30 requests per minute, with bursts of up to 5 requests in a row. With a key: 300 requests per minute, with bursts of up to 50 requests in a row. Over the limit the API returns 429 with a Retry-After header.

Response

Events come newest first. A response looks like this:

{
  "items": [
    {
      "id": "6e6c4ae3-ea0b-403f-9001-2a441e0f76e9",
      "created_at": "2026-10-08T08:12:37.288Z",
      "company_name": "Tokidos",
      "company_website_url": "www.tokidos.com",
      "company_linkedin_url": "https://www.linkedin.com/company/tokidos",
      "event_type": "funding",
      "funding_amount": 3150000,
      "funding_currency": "CAD",
      "funding_stage": "seed"
    }
  ],
  "page": 1,
  "page_size": 1,
  "total": 1
}

Response fields

items

Funding events on the requested page, newest first.

page

Number of the returned page.

page_size

Maximum number of events per page.

total

Total number of events that match the request.

Each item in items is a funding event with these fields:

id

Unique identifier of the event.

created_at

Time the signals engine recorded the event, in ISO 8601 format, UTC.

company_name

Name of the funded company.

company_website_url

Website of the company, as a domain or a URL. May be null.

company_linkedin_url

URL of the company's LinkedIn page. May be null.

event_type

Type of the event, e.g. funding.

funding_amount

Amount raised, in whole currency units. May be null.

funding_currency

Three-letter ISO 4217 currency code. May be null.

funding_stage

Round of the funding: pre_seed, angel, seed, series_a to series_e, or other. Null when the source does not state it.

Errors

400 for invalid filters or pagination, 401 for an invalid key, 429 when you are over the rate limit, 503 when the API is busy. Retry 429 and 503 later.

MCP

AI assistants

Connect

The MCP server gives your AI assistant the same data as the API. Add it to your MCP client's configuration, then ask your assistant about new funding rounds:

{
  "mcpServers": {
    "tada": {
      "url": "https://api.tadasignals.com/mcp"
    }
  }
}

Headers

Log in to get a free MCP key and higher limits. Send the key in the Authorization header with a Bearer prefix. Your account shows the config with the key:

Authorization: Bearer YOUR_MCP_KEY

Rate limits

Without a key: 30 requests per minute, with bursts of up to 5 requests in a row. With a key: 300 requests per minute, with bursts of up to 50 requests in a row. The limits are counted separately from the API. Every request counts, including initialize and ping. Over the limit the server returns 429 with a Retry-After header.

Tool

The server has one tool, get_funding_events. It returns funding events, newest first.

Arguments

All arguments are optional. Combine any of them:

date_from, date_to

Dates in UTC, YYYY-MM-DD, both inclusive.

amount_min, amount_max

Amounts in whole currency units, both inclusive. Amounts are not converted between currencies, and there is no currency filter, so the results mix currencies.

page, page_size

Page number, starting at 1. Page size is 25 by default, 100 at most. You can page through the first 10,000 events.

There is no search by company name and no currency filter. Use the API for them.

Response

The tool returns the same object as the API: items, page, page_size and total, with the same event fields.

Errors

400 for a malformed request, 401 for an invalid key, 413 for a request over 16 KiB, 429 when you are over the rate limit, 503 when the server is busy. Retry 429 and 503 later. Invalid arguments come back as a JSON-RPC error with code -32602.

Webhooks

Account

A webhook sends each new funding event to your endpoint as soon as our engine saves it. Webhooks need an account: log in and set your endpoint on the Webhooks page. One endpoint per account. Only new events are sent, past ones are not.

Request

Your endpoint gets a POST with these headers:

Content-Type: application/json
X-Signals-Signature: sha256=<hex digest>

The body has an events array with one or more funding events:

{
  "events": [
    {
      "id": "6e6c4ae3-ea0b-403f-9001-2a441e0f76e9",
      "created_at": "2026-10-08T08:12:37.288Z",
      "event_type": "Funding",
      "company_name": "Tokidos",
      "company_domain": "www.tokidos.com",
      "company_linkedin_url": "https://www.linkedin.com/company/tokidos",
      "message": "Tokidos raised CAD 3.15 million.",
      "funding_amount": 3150000,
      "funding_currency": "CAD",
      "funding_stage": "seed"
    }
  ]
}

Each event has the same fields as in the API, plus message, a short summary of the event.

Signature

Check the X-Signals-Signature header to make sure the request came from us. Compute an HMAC-SHA256 of the raw request body, keyed with your signing secret as UTF-8 text, and encode it as lowercase hex with the sha256= prefix:

sha256=<lowercase hex of HMAC-SHA256(signing secret, raw body)>

Use the body bytes as they arrive, before you parse the JSON. Compare the values in constant time. The signing secret is on the Webhooks page.

Responses and retries

Answer with any 2xx status within 10 seconds. Otherwise we retry: up to 4 attempts in total, after 1, 2 and 4 seconds.

The order of events is not guaranteed, and the same event can arrive more than once. Deduplicate by id.

Test event

Send test event on the Webhooks page sends one sample event to your endpoint. Its body has "test": true next to events.