Hsr Notices
NPM · @PIPEWORX/MCP-HSR-NOTICES · 2 COMPONENTS
HSR Notices MCP — FTC Hart-Scott-Rodino early-termination notices (api.ftc.gov, brokered by…
Available components
Last scanned (9 hours ago)
Scores higher than 76% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-hsr-notices). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 798 tokens (~199/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +27
- Known CVEs: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 2 Nov 26 −26
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-hsr-notices@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-hsr-notices |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-hsr-notices/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637394285 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2733de035d62f6f9216975bacd4e429914d4999f749c9d4d6f29eafa7cf182355125905a8d23acfeb68aacf54d79a7e14c74830d03eae0a9b5efd1df5 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
hsr_coverage ~141
Report the size and date range of the FTC Hart-Scott-Rodino (HSR) early-termination notice dataset — total notice count, earliest and latest dates on record, and the 2021 suspension gap when the FTC paused granting early terminations for about five weeks. Call this before treating an empty hsr_recent, hsr_search, or hsr_party_history result as "no data" — it confirms whether the requested window actually falls inside FTC coverage. Example: hsr_coverage({})
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional — your own api.data.gov key for higher limits; omit to use the shared Pipeworx key. |
No output schema declared.
No examples provided.
hsr_party_history ~153
Get every FTC Hart-Scott-Rodino (HSR) early-termination notice mentioning a given company or fund, oldest to newest, with a total count — a full antitrust-clearance history for that party across every deal the FTC granted early termination on. Example: hsr_party_history({ party: "Carl C. Icahn" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional — your own api.data.gov key for higher limits; omit to use the shared Pipeworx key. |
| party | string | yes | Company or fund name to search for, e.g. "Carl C. Icahn" or "American Securities Partners". Matches anywhere in the notice title (as-filed legal name). |
No output schema declared.
No examples provided.
hsr_recent ~207
Get the most recent FTC Hart-Scott-Rodino (HSR) early-termination notices, newest first. When a merger clears HSR antitrust review early the FTC publishes a notice — for a private-target deal this is the earliest public signal the merger was filed and cleared, ahead of any 8-K or press release. Returns acquirer, target, transaction number and filing date. Answers "what mergers got antitrust clearance recently" or "which deals received HSR early termination this week." Example: hsr_recent({ days: 7, limit: 25 })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional — your own api.data.gov key for higher limits; omit to use the shared Pipeworx key. |
| days | number | – | How many days back from today to look. Default 7. |
| limit | number | – | Max notices to return, newest first (paged from the source in batches of 50). Default 25, max 100. |
No output schema declared.
No examples provided.
hsr_search ~241
Search FTC Hart-Scott-Rodino (HSR) early-termination notices by acquirer or target company name. Matches against the notice title, which embeds both parties and the transaction number, so a partial or one-sided company/fund name finds every notice that mentions it. Use this to check "did this merger get antitrust clearance" or "has the FTC granted HSR early termination for this deal." Example: hsr_search({ party: "Blockbuster", limit: 25 })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional — your own api.data.gov key for higher limits; omit to use the shared Pipeworx key. |
| limit | number | – | Max notices to return, newest first. Default 25, max 100. |
| party | string | yes | Company or fund name to search for, e.g. "Blockbuster" or "Carl C. Icahn". Matches anywhere in the notice title (as-filed legal name, so include known fund suffixes like "L.P." if a plain name misses… |
| since | string | – | Optional — only return notices on or after this date, YYYY-MM-DD. |
No output schema declared.
No examples provided.
How do I install the Hsr Notices MCP server?
Hsr Notices runs locally as an npm package, launched with npx -y @pipeworx/mcp-hsr-notices. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-hsr-notices
claude mcp add pipeworx-io-hsr-notices -- npx -y @pipeworx/mcp-hsr-notices
What is the Hsr Notices MCP server?
Hsr Notices is an MCP server listed in the public MCP registry as io.github.pipeworx-io/hsr-notices. HSR Notices MCP, FTC Hart-Scott-Rodino early-termination notices (api.ftc.gov, brokered by… This page covers its npm package (@pipeworx/mcp-hsr-notices).
Is the Hsr Notices MCP server safe to use?
Hsr Notices scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Hsr Notices MCP server expose?
Hsr Notices exposes 4 tools: hsr_recent, hsr_search, hsr_party_history, hsr_coverage. Their descriptions and schemas cost roughly 742 tokens of context every time the server is loaded.
Is the Hsr Notices MCP server still maintained?
Hsr Notices is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Hsr Notices MCP server under?
Hsr Notices declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.