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.

CLI

The Disclosery CLI reads the same HTTP API from your terminal. Use a local CLI build with this site endpoint:

disclosery --endpoint https://disclosery.com --accept-terms --json fund filings 1922318

This returns the filer's filings as JSON. The CLI also supports portfolios, timelines, stock holders, search and a filing by accession. Keyless use shares the same 20-call allowance. Set DISCLOSERY_API_KEY for your account's allowance. The key stays in the request header.

The first run asks you to acknowledge the personal-use notice. --accept-terms supplies that acknowledgement for a script. Use disclosery terms to read the notice. A device still needs network access to the configured endpoint.

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.