the13f-mcp
mcp-name: com.the13f/mcp
Model Context Protocol server for the13f. Brings institutional 13F intelligence into Claude Desktop, Cursor, VS Code + Continue, and any MCP-compatible host — no HTTP code required on your side.
Important limitations
Research data only. Sourced from publicly disclosed SEC Form 13F filings,
which lag quarter-end by up to 45 days. Past institutional positioning does
not predict future performance. Nothing here constitutes investment advice.
Every tool's response includes a disclaimer field; the host LLM should
surface it alongside any analysis it produces.
Install
uvx the13f-mcp
Or pip install the13f-mcp if you prefer to manage Python environments
yourself. Python 3.11+ required.
Get a free API key
Free, no payment, no credit card:
- Visit https://the13f.com/integrations/
- Enter your email and solve the Cloudflare Turnstile challenge
- Copy your
pf13f_key — shown once - Paste it into your MCP host's config as
THE13F_API_KEY(see below) - Restart the host
Free tier: 100 read calls per day; quota rolls at UTC midnight. Signal and report tools arrive in later minor versions when paid tiers launch.
Configure your MCP host
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json
(macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows):
{
"mcpServers": {
"the13f": {
"command": "uvx",
"args": ["the13f-mcp"],
"env": {
"THE13F_API_KEY": "pf13f_..."
}
}
}
}
Restart Claude Desktop. The13f tools should appear in the MCP tool list.
Cursor
Settings → MCP → Add Server. Paste the same JSON block into the "Custom" field.
VS Code with Continue
Settings → experimental.modelContextProtocolServers → add a stdio
transport running uvx the13f-mcp with THE13F_API_KEY in env. The key
reveal page at https://the13f.com/integrations/signup-success shows a
copy-paste-ready snippet with the key already filled in.
Available tools — v0.2.0 (Read tier, free)
| Tool | What it does |
|---|---|
list_quarters |
All quarters with holdings data + the latest quarter |
search_managers |
Autocomplete 13F filers by name |
get_manager_holdings |
Full positions for a CIK + quarter |
get_manager_holdings_bulk |
Up to 25 (cik, quarter) pairs in one call |
list_all_managers |
Universe of 8,600+ filers with per-manager summary stats |
find_similar_managers |
Match a portfolio against the universe |
get_consensus_portfolio |
Most-widely-held securities per quarter |
get_market_regime |
Institutional regime snapshot (IIOI composite, state, transition) |
get_sector_flows |
Per-sector capital flows and risk posture |
get_manager_changes |
What a filer bought, sold, added and trimmed vs. the prior quarter |
get_security_ownership |
Which managers hold a stock, plus new buyers and exits |
get_manager_profile |
A filer's AUM + position-count history and a latest-quarter snapshot |
compare_managers |
Two managers head to head: shared positions, weight gaps, what's unique |
Planned tools — later paid releases
| Tools | Requires |
|---|---|
get_security_signals, get_security_signals_bulk, get_portfolio_signals |
Paid tier subscription |
generate_manager_report, generate_security_report, generate_sector_report, check_report_status, wait_and_download_report |
Paid tier + stored card; two-step confirm |
The free-tier Read tools are enough to explore the data and build prompts against it. Signal and report tools deliberately wait on the paid-tier billing plumbing.
Example prompts
"Pull Berkshire Hathaway's top 20 positions as of Q4 2025 and summarize what grew the most quarter-over-quarter."
"I own AAPL, MSFT, and NVDA equal-weight. Find the 5 institutional managers whose portfolios most closely resemble mine."
"What sector did 13F filers most aggressively reduce last quarter? Show me the top three managers leading the reduction."
"Which institutional managers hold NVDA this quarter, and who newly bought or exited it versus last quarter?"
"What did Renaissance buy, sell, add, and trim last quarter, and where does its book overlap most with Two Sigma's?"
The MCP host's LLM picks the right tool, fills in arguments, surfaces the
disclaimer, and returns the result as structured JSON.
Environment variables
| Var | Default | What it controls |
|---|---|---|
THE13F_API_KEY |
(none) | Your pf13f_ key. Without it, tools return a structured "free signup required" response with a link to the signup page. |
THE13F_API_BASE_URL |
https://api.the13f.com |
Override for local development against a running copy of the13f's gui_server. |
THE13F_MCP_TIMEOUT |
30 |
Per-request HTTP timeout in seconds. Minimum 5. |
THE13F_MCP_REPORTS |
on |
off stops the server telling The 13F when it fails on your computer. A report carries the versions, your operating system, where it failed and the error message (see below). |
When it fails on your computer
If the server fails to start, stops with an error or meets a bug of ours in a
tool, it sends The 13F one short report so we can fix it: this package's
version, the mcp library's and Python's versions, your operating system and
processor type, where in the package it failed and the error message with every
file path cut to its last part. It never sends your API key, your questions,
the data or a file path, and nothing leaves while it works. Set
THE13F_MCP_REPORTS=off to stop it.
Source
Public source: https://github.com/pickelfintech/the13f-mcp. This is the
snapshot that PyPI, Glama.ai, and the MCP community list point at. The
GitHub repo is a push-mirror of the GitLab one at
gitlab.com/pickel-fintech/the13f-mcp; GitLab remains the primary and
also carries the release CI. Bug reports and PRs are accepted on either
side.
License
MIT — see LICENSE. The hosted api.the13f.com API that this
client calls is a separate service. A free API key (100 calls/day) is
required; sign up at https://the13f.com/integrations/.
Support
tom@pickelfintech.com — quote the request_id field returned by any failing
tool call for fastest triage.
License
MIT. See LICENSE. The MCP server source is MIT-licensed; use of the the13f API itself is governed by the Terms of Service at https://the13f.com/terms.html.
Metadata
Release files for the13f-mcp 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| the13f_mcp-0.4.1.tar.gz | 41.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| the13f_mcp-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 71.7 kB
Release files / the13f_mcp-0.4.1.tar.gz
| Download URL | the13f_mcp-0.4.1.tar.gz |
|---|---|
| Size | 41.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11486fd47bde70fa270274cc42361ec6763fe06e05462b771d7a8b00b78dd671
|
|
BLAKE2b-256 checksum How to use checksums |
8c0d1a78d04d2525220ea018b58add2df3d337a08041d2b40baa563a3aee8d43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / the13f_mcp-0.4.1-py3-none-any.whl
| Download URL | the13f_mcp-0.4.1-py3-none-any.whl |
|---|---|
| Size | 30.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7ccabd3be7d2e3bb670b43ceb228ce31aceca8b10ac2ce60814291196d8f6e70
|
|
BLAKE2b-256 checksum How to use checksums |
2adfff0461e734e5e441cc32798bb56cbbb76c898e7de4f536fb3f65831cec8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for the13f-mcp 0.4.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.