Hsr Notices MCP Server

@pipeworx/hsr-notices

FTC Hart-Scott-Rodino (HSR) early-termination notices — the earliest public signal that a merger was filed for antitrust review and cleared, often days or weeks before an 8-K or press release for a private-target deal.

Part of Pipeworx — an MCP gateway connecting AI agents to 1865+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

• hsr_recent(days=7, limit=25) — most recent notices, newest first.
• hsr_search(party, since?, limit=25) — notices mentioning a company or fund, matched against the notice title (which embeds both parties and the transaction number).
• hsr_party_history(party) — every notice mentioning a party, oldest to newest, with a total count.
• hsr_coverage() — total notice count, earliest/latest dates on record, and the 2021 suspension gap (below).

Auth

Optional _apiKey — an api.data.gov key. Omit it to use the shared Pipeworx platform key. Passed as the api_key query parameter.

The 2021 suspension gap

The FTC suspended HSR early-termination grants for about five weeks in 2021. This is a real gap in the underlying data, not missing Pipeworx coverage:

• Last notice before the gap: transaction 20210958, dated 2021-02-03.
• No notices exist for 2021-02-04 through 2021-03-11.
• First notices after the gap: transactions 20210455/20210456, dated 2021-03-12.

Early termination has resumed and stays current — hsr_coverage() reports the live latest-notice date on every call, and each empty-result response names this gap when the requested window overlaps it.

Field notes

• acquired_party is often the ultimate parent entity or an individual, and can differ from acquired_entities (the array of actual operating subsidiaries being acquired). Both are always returned — never collapse the array into the parent name.
• Party names are the as-filed legal name, including fund vehicles (e.g. "American Securities Partners IX(B), L.P."). hsr_search and hsr_party_history match substrings of the notice title, so a shorter fragment finds more.
• transaction_number is YYYY + a sequence number.

Data sources

• API: https://api.ftc.gov/v0/hsr-early-termination-notices (JSON:API-style, brokered by api.data.gov)
• Docs: https://www.ftc.gov/developer/api/v0/endpoints/hsr-early-termination-notices-api

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "hsr-notices": {
      "url": "https://gateway.pipeworx.io/hsr-notices/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/hsr-notices/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1865+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/hsr_recent \
  -H 'Content-Type: application/json' \
  -d '{"days":30}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/hsr_recent. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-hsr-notices is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/hsr-notices/mcp endpoint shown above. It needs network access; there is no offline mode.

{
  "mcpServers": {
    "hsr-notices": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-hsr-notices"]
    }
  }
}

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Hsr Notices data" })

The gateway picks the right tool and fills the arguments automatically.

More

• Docs and guides
• pipeworx.io

License

MIT