Back to MCP servers

Fed Comms

https://gateway.pipeworx.io/fed-comms/mcp

● healthy

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

Transport

streamable-http

Auth

—

Cost

—

Protocol revision

2026-07-28

negotiated, not declared

MCP readiness

B · 88/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 94.2/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (430 ms).
Protocol revision	10/10	Speaks the current MCP revision 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 49 tool(s) with descriptions.
Verified identity	7/10	Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags	2/5	seen within 30 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (430 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 95% of peers; This listing 88 · peer median 81
Latency: Faster than 95% of peers; This listing 75 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
Verified identity −3 — Claim the listing and prove control of its domain.
Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags −3 — Keep the listing current in the registry or source it comes from.
Now: seen within 30 days.

How many agent tools actually work · All statistics

Adoption signals

Public signals from outside this directory, shown for context. They do not change search order or grades.

GitHub: ★ 0 · 0 forks; last push 2026-11-09

Listed in

Directories this entry was found in.

mcp-registry since 2026-09-15 wellknown since 2026-09-23 ↗

How to connect

MCP endpoint (streamable-http)

https://gateway.pipeworx.io/fed-comms/mcp

JSON-RPC initialize probe

curl -X POST https://gateway.pipeworx.io/fed-comms/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://pipeworx.io/packs/fed-comms

Source code

https://github.com/pipeworx-io/mcp-fed-comms