MCP.Market

Ferc Eqr MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/ferc-eqr·v0.2.1

FERC Electric Quarterly Reports (EQR) — wholesale power sales: who sells to whom, under what…

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Ferc Eqr yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Ferc Eqr tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Ferc Eqr compares

Against every graded Sales and outbound MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 876 Sales and outbound servers
Uptime
100%
of our recent checks; the typical remote Sales and outbound server answers 100%
Response time
234 ms
faster than 63% of 671 Sales and outbound servers

Release history: 6 versions in the registry since 2026-09-25, latest 2026-11-01, typically one every 4 days.

Install Ferc Eqr in Claude Code, Cursor or VS Code

claude mcp add --transport http ferc-eqr https://gateway.pipeworx.io/ferc-eqr/mcp
Add to Cursor

What the publisher says

From the Ferc Eqr repository's README, as published. We do not edit it. Read it on GitHub

ferc-eqr

Who sells wholesale power to whom: FERC Electric Quarterly Report (EQR) filers, and the contracts between sellers and their counterparties.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Not the same thing as ferc-elibrary: that pack is FERC's docket/document search (filings, orders, opinions). This pack is the underlying filer and contract data — a different question entirely ("who sells to whom" vs. "what did FERC file").

Tools

Auth

None. No key, no account.

No personal data

The upstream source also carries filer CONTACT fields per company — a named individual's name, title, address, phone and email. None of that is loaded or returned by any tool. Only company-level identity (companyidferc, fileruniqueid, company_name) is kept.

Coverage is not automatically "everything since 2013"

The upstream data spans 2013q3 through the present, but this pack's coverage is loaded incrementally rather than all at once. Call eqrcoverage for the quarter range actually covered before treating an empty result as "no such contract"** — a result outside the covered range is a coverage gap, not a negative answer. Every tool's response says this too.

Data source, licence, attribution

FERC itself publishes Electric Quarterly Reports only as quarterly nested ZIP files, with no query interface of its own. Catalyst Cooperative's PUDL project — a widely-used open energy-data project — normalizes EQR into structured per-quarter tables and republishes them publicly.

Licence: "Copyright 2016-2026, Catalyst Cooperative, CC-BY-4.0" () — explicit on the DATA (their processing code carries a separate MIT licence, which is a different thing and does not govern the data). CC-BY-4.0 permits redistribution with attribution. Every tool response carries an attribution field; do not remove it if you touch this pack.

Refreshing

node scripts/ingest-ferc-eqr.mjs --since <yyyyqN>

Re-runnable and safe: rows upsert on a content hash of every loaded column, so loading an already-covered quarter again is a no-op rather than a duplicate. node scripts/ingest-ferc-eqr.mjs --dry-run [--since | --all] parses without writing anything, useful for checking a new quarter's row counts before committing to a load. listQuarters() discovers what's published live each run, so a newly published quarter needs no code change — just a wider --since.

Phase 1 vs Phase 2

Phase 1 (this pack): filer identity, index-price-publisher reporting, and contract terms — one row per contract RATE-PERIOD line item, not one row per contract (a single contract can carry several rows for different rate periods over its life). A quantity or rate returned here comes from the CONTRACT's stated terms, not from a settled trade.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Ferc Eqr: common questions

Is Ferc Eqr MCP server safe?
Mostly: it is graded B (77/100). Read the Ferc Eqr safety report
How do I install Ferc Eqr?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Ferc Eqr need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Ferc Eqr maintained?
The last commit was 40 days ago (2026-09-25). The latest release is v0.2.1.
Is Ferc Eqr up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Ferc Eqr?
Servers from other publishers that do the same job: Adwarp MCP server, Luca MCP server and MisarReach MCP Server.
How does Ferc Eqr compare with other Sales and outbound MCP servers?
safety score 77/100 (higher than 50% of 876 Sales and outbound servers); uptime 100% (of our recent checks; the typical remote Sales and outbound server answers 100%); response time 234 ms (faster than 63% of 671 Sales and outbound servers). Full comparison.

Alternatives to Ferc Eqr

Same job from other publishers: the closest match first, then the best rated.

  • Adwarp
    Open-source ad agent for LinkedIn Ads and Google Ads. Drafts campaigns, audiences and reports.
    A
  • Luca
    SetLuca DM sales from any MCP client: 208 API tools and 15 task tools for leads, replies, calls.
    A
  • MisarReach MCP Server
    Find leads, enrich and score them, run multi-channel outreach, and manage the sales pipeline — from…
    A
  • Conduyt CRM
    Conduyt CRM tools for AI agents: contacts, deals, pipelines, tasks, automations, messaging, reports
    B
  • Outreach
    Outreach sales engagement MCP server: prospects, sequences, accounts, tasks, and mailings
    A

More from pipeworx-io →