EDGAR 13F point-in-time
PYPI · EDGAR13F-MCP
SEC Form 13F holdings as they could have been known on a given date (stdio).
Available components
Last scanned (16 hours ago)
Scores higher than 87% of PyPI servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Serios16/edgar13f-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 790 tokens (~197/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Analysed pypi/edgar13f-mcp@1.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Serios16/edgar13f-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Serios16/edgar13f-mcp/.github/workflows/publish.yml@refs/tags/v1.2.2 |
| Rekor log index | 3394868530 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:53447a901b0736c13e1e6153e0509a517649bb6d7738b2a1b6e0e68b703ed705 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
diff_holdings ~248
Position-level changes between period_a and period_b, each computed with get_holdings_as_of rules on the same as_of and consolidated by (cusip, put_call, sh_prn). Large managers file tens of thousands of rows: narrow with issuer, cusip or max_positions. as_of means what was publicly filed by that date.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | ISO-8601 knowledge date: the answer uses only what was publicly filed on EDGAR by this date. |
| cik | string | yes | SEC Central Index Key; leading zeros optional. Resolve a manager's name to its CIK with find_manager. |
| cusip | array | – | – |
| issuer | string | – | Keep only rows whose name_of_issuer contains this text (case-insensitive, whitespace collapsed); combined with cusip as AND. The response lists matched_cusips. |
| max_positions | integer | – | Return only the largest positions (by value); the response adds total_positions, truncated and order. |
| period_a | string | yes | Form 13F report period: a calendar quarter-end date. |
| period_b | string | yes | Form 13F report period: a calendar quarter-end date. |
No output schema declared.
No examples provided.
find_manager ~136
Find a manager's CIK from its name (a case-insensitive substring of current or former EDGAR entity names). Candidates that have filed Form 13F come first. Use it before the other tools when you only know the name. entity_name is EDGAR's current name (not point-in-time); with as_of, has_13f_filings counts only 13F filings dated on or before as_of.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | ISO-8601 knowledge date: the answer uses only what was publicly filed on EDGAR by this date. |
| limit | integer | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
get_holdings_as_of ~252
Effective 13F holdings of the manager for one report period as knowable on as_of (point-in-time and amendment rules), with the accession number(s) they come from. Large managers file tens of thousands of rows: narrow with issuer, cusip or max_positions. as_of means what was publicly filed by that date.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | ISO-8601 knowledge date: the answer uses only what was publicly filed on EDGAR by this date. |
| cik | string | yes | SEC Central Index Key; leading zeros optional. Resolve a manager's name to its CIK with find_manager. |
| cusip | array | – | – |
| issuer | string | – | Keep only rows whose name_of_issuer contains this text (case-insensitive, whitespace collapsed); combined with cusip as AND. The response lists matched_cusips. |
| max_positions | integer | – | Return only the largest positions (by value); the response adds total_positions, truncated and order. |
| period | string | yes | Form 13F report period: a calendar quarter-end date. |
| position_type | string | – | Form 13F contains long positions only; any other value is declined with unsupported_request. |
No output schema declared.
No examples provided.
list_13f_filings ~154
Every Form 13F submission (13F-HR, 13F-HR/A, 13F-NT, 13F-NT/A) by the manager whose EDGAR filing date is on or before as_of (what was publicly filed by then). Pass period to list only the filings for one report period.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | ISO-8601 knowledge date: the answer uses only what was publicly filed on EDGAR by this date. |
| cik | string | yes | SEC Central Index Key; leading zeros optional. Resolve a manager's name to its CIK with find_manager. |
| period | string | – | Form 13F report period: a calendar quarter-end date. |
No output schema declared.
No examples provided.
How do I install the EDGAR 13F point-in-time MCP server?
EDGAR 13F point-in-time runs locally as a PyPI package, launched with uvx edgar13f-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · edgar13f-mcp
claude mcp add serios16-edgar13f-mcp -- uvx edgar13f-mcp
What is the EDGAR 13F point-in-time MCP server?
EDGAR 13F point-in-time is an MCP server listed in the public MCP registry as io.github.Serios16/edgar13f-mcp. SEC Form 13F holdings as they could have been known on a given date (stdio). This page covers its PyPI package (edgar13f-mcp).
Is the EDGAR 13F point-in-time MCP server safe to use?
EDGAR 13F point-in-time scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 November 2026. 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 EDGAR 13F point-in-time MCP server expose?
EDGAR 13F point-in-time exposes 4 tools: find_manager, list_13f_filings, get_holdings_as_of, diff_holdings. Their descriptions and schemas cost roughly 790 tokens of context every time the server is loaded.
Is the EDGAR 13F point-in-time MCP server still maintained?
EDGAR 13F point-in-time is still listed as active in the MCP registry. We last reached this channel on 7 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 EDGAR 13F point-in-time MCP server under?
EDGAR 13F point-in-time 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 EDGAR 13F point-in-time MCP server?
VerifyMCP ran 16 checks on EDGAR 13F point-in-time, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.