Fed Comms
NPM · @PIPEWORX/MCP-FED-COMMS · 2 COMPONENTS
Federal Reserve communications from federalreserve.gov: the FOMC meeting calendar, each policy…
Available components
Last scanned (5 hours ago)
Scores higher than 88% 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-fed-comms). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 970 tokens (~194/item across 5 items; 5 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 Management80
- Stability observed for 24 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 9 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Nov 2026 · Analysed npm/@pipeworx/mcp-fed-comms@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-fed-comms |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-fed-comms/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635940317 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ea2e9fad0a0fda3f3e5a7a3e8840a4eb20d202f89c4d70ef6cf6d019ad85a21e2d2b718d9be7e655ed02ddbae421abea86f9fdfec1c6d9c4e7cea2f32 |
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 →
beige_book ~191
Beige Book from the Federal Reserve — the eight-times-a-year summary of current economic conditions gathered by the 12 Federal Reserve Districts: the national summary or one district's report (Boston, New York, Philadelphia, Cleveland, Richmond, Atlanta, Chicago, St. Louis, Minneapolis, Kansas City, Dallas, San Francisco) split into its sections (Overall Economic Activity, Labor Markets, Prices, and the district's industry sections). Answers "what does the latest Beige Book say about the Dallas district", "Beige Book labor market conditions", "regional economic conditions per the Fed".
| Name | Type | Req | Description |
|---|---|---|---|
| district | string | – | District name, city, or number 1–12 (e.g. "Dallas", "Kansas City", "11"). Default: the national summary. |
| edition | string | – | Edition as YYYY-MM or YYYYMM (e.g. "2026-07"). Default: the latest published edition. |
No output schema declared.
No examples provided.
fed_speeches ~199
Recent speeches and congressional testimony by Federal Reserve Board governors and the Chair, from the Board's speeches and testimony feeds: title, speaker with official title, date, venue, URL and the opening paragraph. Filter by days back and speaker surname. Answers "what did Fed governors say this week", "latest speech by Waller", "Powell testimony".
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look back this many days (default 14). The feeds only carry the latest ~20 items each, so the window is capped by what the feed still holds — see feed_window in the response. |
| include_testimony | boolean | – | Also read the testimony feed (default true). |
| limit | integer | – | Max items to return and open for their first paragraph (default 10, max 25). |
| speaker | string | – | Surname to filter on, case-insensitive substring, e.g. "Cook", "Warsh", "Jefferson". |
No output schema declared.
No examples provided.
fomc_calendar ~143
FOMC meeting calendar from the Federal Reserve Board: every scheduled and unscheduled meeting of a year with dates, whether it carries a Summary of Economic Projections (SEP), statement, press-conference, implementation-note and minutes links (with the minutes release date), plus next_meeting and days_until from today. Answers "when is the next FOMC meeting", "what are the Fed meeting dates in 2026", "when do the minutes for the July meeting come out".
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | – | Calendar year, e.g. 2026. Default: the current year. The Fed page carries roughly the last 6 years plus next year. |
No output schema declared.
No examples provided.
fomc_minutes ~168
Minutes of an FOMC meeting from the Federal Reserve Board: full text split into its sections (Developments in Financial Markets, Staff Review of the Economic Situation, Participants' Views, Committee Policy Actions, votes, attendance) with an optional section filter. Answers "what did the FOMC minutes say about inflation", "summarize participants' views in the latest Fed minutes", "who attended the June FOMC meeting".
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Meeting date as YYYY-MM-DD or YYYY-MM (e.g. "2026-06"). Default: the most recently released minutes. |
| section | string | – | Case-insensitive substring of a section heading, e.g. "Participants' Views", "Policy Actions", "Staff Economic Outlook". Returns only that section's text. |
No output schema declared.
No examples provided.
fomc_statement ~215
FOMC post-meeting policy statement from the Federal Reserve with the rate decision parsed (target range, hold/cut/hike, basis points), the vote tally with named dissenters and what they preferred, the implementation-note URL, and diff_vs_prior — a sentence-level redline against the previous statement listing sentences added, removed and changed (date and roll-call lines excluded). Answers "what changed in the latest Fed statement", "did the FOMC cut rates", "who dissented at the Fed meeting".
| Name | Type | Req | Description |
|---|---|---|---|
| compare_to | string | – | Date of the statement to diff against (YYYY-MM-DD or YYYY-MM). Default: the statement immediately before the selected one. |
| date | string | – | Statement date as YYYY-MM-DD or YYYY-MM (e.g. "2026-06-17" or "2026-06"). Default: the most recent released statement. |
| include_text | boolean | – | Include the full statement text (default true). Set false for a compact rate-decision + diff answer. |
No output schema declared.
No examples provided.
How do I install the Fed Comms MCP server?
Fed Comms runs locally as an npm package, launched with npx -y @pipeworx/mcp-fed-comms. 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-fed-comms
claude mcp add pipeworx-io-fed-comms -- npx -y @pipeworx/mcp-fed-comms
What is the Fed Comms MCP server?
Fed Comms is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fed-comms. Federal Reserve communications from federalreserve.gov: the FOMC meeting calendar, each policy… This page covers its npm package (@pipeworx/mcp-fed-comms).
Is the Fed Comms MCP server safe to use?
Fed Comms scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 Fed Comms MCP server expose?
Fed Comms exposes 5 tools: fomc_calendar, fomc_statement, fomc_minutes, fed_speeches, beige_book. Their descriptions and schemas cost roughly 916 tokens of context every time the server is loaded.
Is the Fed Comms MCP server still maintained?
Fed Comms is still listed as active in the MCP registry. We last reached this channel on 22 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 Fed Comms MCP server under?
Fed Comms declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Fed Comms MCP server?
VerifyMCP ran 16 checks on Fed Comms, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.