Oxford Ledge
v3.8.3Ask your assistant; it reads the public record: SEC filings, 13F, insider trades, BDC loans.
Endpoint health
online- Last checked
- 11/20/2026, 7:17:04 AM
- Latency
- 118 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.oxfordledge%2Foxford-ledge
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.oxfordledge/oxford-ledge": {
"url": "https://www.oxfordledge.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
13F Holdings of a Fund
get_13f_holdings
What one institutional filer owns: the largest positions in its latest SEC 13F-HR, plus QoQ changes (keyless: from stored quarters). Accepts a numeric CIK (preferred), a ticker (BRK-B or BRK.B for Berkshire), or a filer NAME (3-80 characters): ONE name-prefix match in the curated 13F filer universe resolves to its CIK (`resolved_from` says so); an ambiguous name is refused with candidates, never guessed. Returns {cik, fundName, filingDate, periodOfReport, totalHoldings, totalValue, holdings}; rows carry name, title_of_class, value (whole USD), shares, type, position_type, lots. There is NO ticker field and `cusip` is stripped on every channel (no plan carries a CUSIP Global Services licence today); `title_of_class` is the share-class discriminator. `position_type` is COM|PRN|PUT|CALL: do NOT sum across types. Source: SEC EDGAR 13F-HR, ~45-day quarterly delay. Heavy operation, max 2 concurrent.
Schema valid · SHA-256 7cf0d6ddf13a…
View input schema
{ "type": "object", "properties": { "fund": { "type": "string", "description": "Fund CIK number (e.g. 1067983 for Berkshire Hathaway) -- preferred. A ticker is resolved via SEC's company map: letters with at most one class suffix (e.g. BLK, or BRK-B / BRK.B -- SEC lists Berkshire as BRK-A / BRK-B, so bare 'BRK' does not resolve). A filer NAME (3-80 chars) resolves when exactly one curated filer name starts with it; otherwise the error names ol_13f_filer_search. Any other shape is rejected as INVALID_PARAMS." }, "max_holdings": { "type": "integer", "description": "Maximum number of holdings to return (default 50)", "minimum": 1, "maximum": 500 } }, "required": [ "fund" ] }Access Status
get_access_status
Who this server resolved the caller as (caller.kind api_key / bearer / cookie / anonymous, key_presented, key_accepted), the plan, the hourly data-tool budget left (anonymous calls share one budget per network address), and data_through for the 13F and BDC stores. Asking does not spend that budget. A rejected key is refused 401 invalid_api_key before any tool runs. No personal data. Source: Oxford Ledge account and store metadata.
Connections
streamable-http
https://www.oxfordledge.com/mcp