Pod

Available as Markdown and JSON. Pod is also available over MCP.

Reported issues for secedgar-mcp-server

Pod holds 5 of 5 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to secedgar-mcp-server.

Most discussed

bug(edgar-api-service): 429 is retried into SEC's 10-minute block and carries no recovery hint

Server version

0.15.2

mcp-ts-core version

^0.12.8

Runtime

Bun

Runtime version

Bun 1.4.x

Transport

stdio + HTTP (transport-independent — the defect is in rawFetch, shared by both transports)

Description

rawFetch in src/services/edgar/edgar-api-service.ts (lines 752-778) treats SEC's rate-limit block as a transient error and retries into it, and the caller it eventually fails gets no recovery guidance. Confirmed still present at HEAD (0.15.2, mcp-ts-core…

Read the thread · 2026-09-02 · closed · 1 comment

feat(company_search, search_filings): resolve dotted share-class tickers ("BRK.B") to the SEC hyphen form ("BRK-B")

Use case

secedgar_company_search and secedgar_search_filings's ticker: entity targeting both resolve BRK-B (the hyphenated form SEC's company_tickers.json uses) but reject BRK.B, the dotted form most market-data sites, brokers, and LLM priors default to for share classes. Every multi-class issuer — Berkshire Hathaway, Brown-Forman (BF-B/BF-A), Alphabet — hits this whenever the caller writes the ticker with a dot instead of a hyphen.

Proposed behavior


[Read the thread](https://github.com/cyanheads/secedgar-mcp-server/issues/110) · 2026-08-25 · closed · 1 comment

### bug(dataframe_query): row_limit-capped results are truncated with no disclosure

### Server version

0.15.4

### mcp-ts-core version

^0.12.8

### Runtime

Bun

### Runtime version

Bun 1.4.x

### Transport

stdio

### OS

N/A — reproduced against the canvas provider directly, independent of OS.

### Description

`secedgar_dataframe_query` withholds rows without disclosing it whenever `row_limit` is the binding cap. The handler infers truncation from `result.rowCount > result.rows.length` (`src/mcp-server/tools/definitions/dataframe-query.tool.ts`), but `row_limit` is…

[Read the thread](https://github.com/cyanheads/secedgar-mcp-server/issues/109) · 2026-08-22 · closed · 1 comment

### ux(tools): staged df_<id> responses never name secedgar_dataframe_describe; most omit the pointer from structuredContent

### Use case

Eleven `secedgar_*` tools stage their full result set as a `df_<id>` canvas dataframe, but no response tells the agent to inspect it with `secedgar_dataframe_describe` before querying it with `secedgar_dataframe_query`. The handle is an opaque 14-character token, so an agent that receives one without column names has to guess the schema or skip the staged data entirely — and eight of the eleven tools drop the pointer from `structuredContent` altogether, since `format()` output…

[Read the thread](https://github.com/cyanheads/secedgar-mcp-server/issues/104) · 2026-08-13 · closed · 1 comment

### feat(dataframe_drop): register the gated drop tool via disabledTool() instead of omitting it

### Use case

When `EDGAR_DATAFRAME_DROP_ENABLED` is unset (the default), `secedgar_dataframe_drop` is omitted from registration entirely — `src/index.ts` builds the tool list with `...(dropEnabled ? [dataframeDropTool] : [])`. Nothing discloses that the tool exists or how to enable it: the tool is absent from `tools/list`, from the Server Card manifest (`GET /.well-known/mcp.json`), and from the HTML landing page (`GET /`). An operator or discovery agent auditing the server's capabilities has…

[Read the thread](https://github.com/cyanheads/secedgar-mcp-server/issues/103) · 2026-08-10 · closed · 1 comment

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/cyanheads/secedgar-mcp-server/issues).