# Fed Comms (npm · @pipeworx/mcp-fed-comms)

Federal Reserve communications from federalreserve.gov: the FOMC meeting calendar, each policy…

- Trust score: 91/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `gateway.pipeworx.io`: 88/100, [markdown](https://verifymcp.io/servers/pipeworx-io-fed-comms/fed-comms-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-fed-comms/fed-comms-mcp)
- npm · `@pipeworx/mcp-fed-comms`: 91/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-fed-comms/pipeworx-mcp-fed-comms.md), [page](https://verifymcp.io/servers/pipeworx-io-fed-comms/pipeworx-mcp-fed-comms)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-fed-comms`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-fed-comms).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-fed-comms -- npx -y @pipeworx/mcp-fed-comms
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-fed-comms": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fed-comms"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-fed-comms": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fed-comms"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-fed-comms -- npx -y @pipeworx/mcp-fed-comms
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-fed-comms": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-fed-comms"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-fed-comms --command npx --arg -y --arg @pipeworx/mcp-fed-comms
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-fed-comms:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-fed-comms"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-fed-comms": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-fed-comms"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-fed-comms -t stdio -c npx -a -y @pipeworx/mcp-fed-comms
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-fed-comms": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fed-comms"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 91, +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.

### 2026-11-19 (score 90, +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.

### 2026-11-17 (score 89, +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.

### 2026-11-15 (score 88, +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.

### 2026-11-12 (score 87, +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.

### 2026-11-10 (score 86, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-09 (score 85, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-08 (score 85, +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.

## MCP tools (5)

### `fomc_calendar` (~143 tokens)

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".

Input parameters:

- `year` (integer): Calendar year, e.g. 2026. Default: the current year. The Fed page carries roughly the last 6 years plus next year.

### `fomc_statement` (~215 tokens)

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".

Input parameters:

- `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.

### `fomc_minutes` (~168 tokens)

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".

Input parameters:

- `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.

### `fed_speeches` (~199 tokens)

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".

Input parameters:

- `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".

### `beige_book` (~191 tokens)

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".

Input parameters:

- `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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-fed-comms/pipeworx-mcp-fed-comms#diagnostics

## Score history

- 2026-11-22: 91
- 2026-11-21: 91
- 2026-11-20: 90
- 2026-11-19: 90
- 2026-11-18: 89
- 2026-11-17: 89
- 2026-11-16: 88
- 2026-11-15: 88
- 2026-11-14: 87
- 2026-11-13: 87
- 2026-11-12: 87
- 2026-11-11: 86
- 2026-11-10: 86
- 2026-11-09: 85
- 2026-11-08: 85
- 2026-11-07: 84
- 2026-11-06: 84
- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-fed-comms
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-fed-comms
- Repository: https://github.com/pipeworx-io/mcp-fed-comms
- Website: https://pipeworx.io/packs/fed-comms
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-fed-comms/pipeworx-mcp-fed-comms.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-fed-comms/pipeworx-mcp-fed-comms/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-fed-comms/pipeworx-mcp-fed-comms.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-fed-comms/pipeworx-mcp-fed-comms
