Skip to content

API and MCP connections

Ask for a fund's holdings, a stock's institutional holders, or a position timeline that joins 13F, 13D/G and insider filings. Answers include links to the page and the SEC filing behind each reported fact.

Coverage depends on the filings currently imported. The examples below describe requests you can make, but their filings may not be loaded. A successful connection does not establish complete or current data. Check data coverage before using the results.

Endpoint and allowance

MCP endpoint: https://disclosery.com/mcp. Select Streamable HTTP. The server does not offer a legacy SSE endpoint or a local stdio command.

Keyless use allows 20 calls per day per IP. A free account key allows 100. Paid keys allow 2,000 when subscriptions are available. JSON and MCP calls share the allowance. It resets at midnight UTC. Keyless users behind the same network address share one allowance.

Create a key on your account's API keys page. Clients that support request headers can send Authorization: Bearer YOUR_API_KEY. A browser login cookie does not authenticate an API call. Keep keys out of shared configuration files.

Claude Code

Run this on a device that can reach the endpoint. It adds a keyless connection:

claude mcp add --transport http disclosery https://disclosery.com/mcp

For a keyed connection, use the same command with --header "Authorization: Bearer YOUR_API_KEY". You can also use a project configuration with a header that reads an environment variable. See the official Claude Code MCP guide.

Check claude mcp get disclosery and /mcp in Claude Code. Confirm the server lists nine tools, then ask, “Show Pale Fire Capital's LSPD position timeline, with source links.” Adding a configuration alone does not prove a connection.

Claude Desktop

For a publicly reachable server, open Customize, then Connectors. Choose Add custom connector, enter the MCP endpoint, and review the detected authentication. Choose No sign in for keyless use. Where Request headers is available, add Authorization with the value Bearer YOUR_API_KEY for keyed use. Team and Enterprise setup may require an organization owner.

Enable the connector in the conversation's connectors menu and check its tool list. Claude's remote-connector guide explains the steps and confirms that connections originate from Anthropic's cloud, including on Desktop. Desktop's local stdio configuration is a separate mechanism and this server provides no stdio transport.

Cursor

Put this in .cursor/mcp.json for the project, or ~/.cursor/mcp.json for all projects:

{
  "mcpServers": {
    "disclosery": {
      "url": "https://disclosery.com/mcp"
    }
  }
}

For keyed use, add "headers": {"Authorization": "Bearer ${env:DISCLOSERY_API_KEY}"} inside the Disclosery entry and set that variable before starting Cursor. Review the connection and enable its tools in Cursor's MCP settings. Ask for the LSPD timeline and check the source links. See Cursor's MCP documentation.

ChatGPT

For a publicly reachable endpoint, enable Developer mode under Settings, Security and login (availability depends on account and workspace policy). Open ChatGPT Plugins, select the plus button, enter a name and the MCP URL, then create the connection and inspect the discovered tools. Use the keyless connection. This version has no OAuth login, and this guide does not claim a supported keyed ChatGPT configuration.

Add the connection to a conversation and ask for a cited LSPD timeline. Refresh the connection after tool metadata changes. OpenAI's connection guide documents the current flow. OpenAI also offers a Secure MCP Tunnel for private servers. No tunnel is configured for this site.

JSON API

curl 'https://disclosery.com/api/v1/funds/1922318/timeline/LSPD'

For keyed use, add -H "Authorization: Bearer YOUR_API_KEY". Responses contain the result, tier and remaining daily allowance. See the frozen API v1 contract for routes, arguments, response fields and errors.

Install the Disclosery CLI

The CLI reads SEC ownership data from your terminal through the same JSON API. Download version 0.1.0; no account or Go installation is needed. Linux x64 is validated. Other platform builds are experimental until their native installation checks are complete.

Disclosery 0.1.0 downloads
PlatformDownloadStatus
Linux x64Linux x64 archiveValidated
Linux ARM64Linux ARM64 archiveExperimental
macOS Apple SiliconmacOS Apple Silicon archiveExperimental, unsigned
macOS IntelmacOS Intel archiveExperimental, unsigned
Windows x64Windows x64 ZIPExperimental, unsigned
Windows ARM64Windows ARM64 ZIPExperimental, unsigned

SHA-256 checksums · Release notes · MIT-licensed source and support

Install and verify

Choose the archive matching your operating system and processor. On Linux, uname -m reports x86_64 for x64 and aarch64 for ARM64. On macOS, About This Mac identifies Apple Silicon or Intel. Windows Settings, System, About shows your system type.

Download the archive and checksum file into the same folder. This example installs Linux x64 without administrator privileges:

curl -fLO https://github.com/disclosery/disclosery-cli/releases/download/v0.1.0/disclosery_0.1.0_linux_amd64.tar.gz
curl -fLO https://github.com/disclosery/disclosery-cli/releases/download/v0.1.0/checksums.txt
grep 'disclosery_0.1.0_linux_amd64.tar.gz$' checksums.txt | sha256sum -c -
tar -xzf disclosery_0.1.0_linux_amd64.tar.gz
mkdir -p "$HOME/.local/bin"
install -m 755 disclosery "$HOME/.local/bin/disclosery"
export PATH="$HOME/.local/bin:$PATH"
disclosery --version

Keep that directory in your shell's PATH for future sessions. On macOS, verify the selected archive with shasum -a 256, compare its digest with the matching line in checksums.txt, then extract and install it using the same user-directory steps. The macOS binaries are not signed or notarized; macOS may block them. Native installation acceptance is pending. No Homebrew installation is advertised for this release.

On Windows, compare Get-FileHash .\disclosery_0.1.0_windows_amd64.zip -Algorithm SHA256 with the matching checksum entry, extract the ZIP, and run .\disclosery.exe --version. For ARM64 use its corresponding ZIP. Add the extracted folder to your user PATH if you want to run it from any directory. Windows binaries are unsigned and native acceptance is pending.

Read your first filings

disclosery --accept-terms --json fund filings 1350694

This reads imported filings for Bridgewater Associates, LP from https://disclosery.com. It also supports search, portfolios, position timelines, stock holders, filing details and a cursor-based watch. On PowerShell use .\disclosery.exe while running from the extracted folder. Returned JSON includes the reporting organization, source links and remaining allowance; incomplete coverage is not an empty historical portfolio.

The first request asks you to acknowledge the personal-use notice. --accept-terms supplies that acknowledgement for scripts. Read it with disclosery terms. Use --endpoint, DISCLOSERY_ENDPOINT or your configuration to choose another trusted API origin.

Keyless use shares the 20-call daily allowance per IP. Set DISCLOSERY_API_KEY locally for your account's allowance; keys stay in request headers. Keep them out of URLs and shared files. CSV/CUSIP exports remain available when authorized by the server and require a paid key. Manage API keys.

Updates, removal and help

To upgrade, download a newer version from GitHub Releases, verify its checksum and replace the installed executable. To uninstall, remove the executable; remove ~/.config/disclosery and ~/.cache/disclosery only if you also want to delete your local settings and cached data.

If the command is not found, check PATH; if it cannot execute, check the selected processor and platform. For API errors, inspect the error and quota reset instead of assuming no filings exist. Read coverage and service terms. Report reproducible client problems through CLI issues, without keys or private output.

Check the answer

When the requested filings are loaded, compare the tool and JSON response with the fund's timeline and the linked SEC filings. An empty result does not establish that a filing or position does not exist. Estimates name their basis. A manager-wide aggregate may have no single SEC filing, so its EDGAR link is null.

Client guidance checked October 5, 2026. Data coverage describes what is loaded and when it updates.