EDGAR 13F point-in-time MCP server
io.github.Serios16/edgar13f-mcp·v1.2.2SEC Form 13F holdings as they could have been known on a given date (stdio).
0 stars126 downloads/wk
Reviews
Write oneNobody has reviewed EDGAR 13F point-in-time yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
EDGAR 13F point-in-time tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it
- Code scan14 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How EDGAR 13F point-in-time compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 80% of 48,255 servers
- Downloads a week
- 126
- more than 68% of 12,191 servers with a package
Install EDGAR 13F point-in-time in Claude Code, Cursor or VS Code
claude mcp add edgar13f-mcp -- uvx edgar13f-mcp
What the publisher says
From the EDGAR 13F point-in-time repository's README, as published. We do not edit it. Read it on GitHub
edgar13f-mcp
<!-- mcp-name: io.github.Serios16/edgar13f-mcp -->
An MCP server that answers questions about SEC Form 13F holdings as they could have been known on a given date. It comes with an evaluation that was frozen before the server was written.
What it does, and why point-in-time matters
Institutional managers with US$100m or more in 13F securities file Form 13F every quarter, up to 45 days after the quarter ends. Many of them later amend the report. A restatement replaces the whole report. A new-holdings amendment adds rows to it. So "what did manager X hold at 2024-12-31?" has different correct answers on different days: nothing before the filing date, then the original report, and later the amended one.
A tool that always returns the latest version leaks the future into backtests, research notes and agent answers. This server takes an as_of date with every call and follows two rules (full text in contracts/CONTRACTS.md):
before as_of. Nothing filed later affects the answer: not the rows, the citations, the filing list, or which filing counts as "latest".
- Visibility (§3): a filing is visible on as_of only if its EDGAR filing date is on or
last original or restatement. Every later new-holdings amendment is added to it. Each row cites the filing it came from.
- Amendments (§4): the visible filings for the period are put in order. The base is the
Install and run
Python 3.11, with the official MCP Python SDK 2.x. The server speaks MCP over stdio only.
One command (needs uv). The package is edgar13f-mcp on PyPI, uploaded by this repository's release workflow with trusted publishing, and listed in the official MCP Registry as io.github.Serios16/edgar13f-mcp:
export SEC_USER_AGENT="Your Name your.email@example.com" # required by SEC fair access
uvx --python 3.11 edgar13f-mcp # pin a release: edgar13f-mcp@1.2.2For an MCP client such as Claude Desktop:
{"mcpServers": {"edgar13f": {
"command": "uvx",
"args": ["--python", "3.11", "edgar13f-mcp"],
"env": {"SEC_USER_AGENT": "Your Name your.email@example.com"}}}}Any commit or tag also runs straight from GitHub: uvx --python 3.11 --from git+https://github.com/Serios16/edgar13f-mcp@v1.2.2 edgar13f-mcp. The older command name edgar13f-server still works. Both names are tested on the built wheel by tests/tools/installsmoke.sh (empty uv cache, MCP handshake; output in reports/artifacts/installsmoke_stage6.txt). From a clone instead:
python3.11 -m venv .venv && . .venv/bin/activate
pip install -e .
export SEC_USER_AGENT="Your Name your.email@example.com" # required by SEC fair access
python -m edgar13f.server # or: edgar13f-serverEnvironment variables:
does not contact sec.gov.
- SECUSERAGENT: the User-Agent sent to sec.gov. It is required; without it the server
~/.cache/edgar13f), then a private per-user temp dir. The server writes nowhere else.
- EDGAR13FCACHEDIR: the on-disk cache. The default is $XDGCACHEHOME/edgar13f (or
Limits). Any other value, or none, keeps redaction on.
- EDGAR13F_REDACT: set to exactly off to return the rows that are redacted by default (see
50 largest positions (see Agent use). Unset, every v1 call answers byte for byte as in v1.1.0.
- EDGAR13FAGENTMODE: set to exactly on to cap unnarrowed holdings and diff answers at the
together with EDGAR13F_REDACT=off).
- EDGAR13FFIXTUREDIR: serve recorded fixtures instead of EDGAR (used by the tests; refused
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
EDGAR 13F point-in-time: common questions
- Is EDGAR 13F point-in-time MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the EDGAR 13F point-in-time safety report
- How do I install EDGAR 13F point-in-time?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does EDGAR 13F point-in-time need an API key?
- No secret keys are declared. It reads 3 settings from the environment.
- Is EDGAR 13F point-in-time maintained?
- The last commit was 12 days ago (2026-10-23). The latest release is v1.2.2.
- What can I use instead of EDGAR 13F point-in-time?
- Servers from other publishers that do the same job: EdgarTools MCP server.
- How does EDGAR 13F point-in-time compare with other MCP servers?
- safety score 89/100 (higher than 80% of 48,255 servers); downloads a week 126 (more than 68% of 12,191 servers with a package). Full comparison.
Alternatives to EDGAR 13F point-in-time
Same job from other publishers: the closest match first, then the best rated.
- EdgarToolsOpen-source SEC EDGAR toolkit — 13 tools, 7 prompts, every filing type. No API key required.not reviewedWidely usedA