Oxford Ledge
REMOTE · WWW.OXFORDLEDGE.COM · 2 COMPONENTS
Ask your assistant; it reads the public record: SEC filings, 13F, insider trades, BDC loans.
Available components
Last scanned (23 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 16690 tokens (~256/item across 65 items; 65 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 65 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 66 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 0
- Tool “search_company” rewrote its description, which is the text the model reads security
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_corporate_events” rewrote its description, which is the text the model reads security
- Tool “search_bdc_borrower” rewrote its description, which is the text the model reads security
- Tool “ol_ownership_changes” rewrote its description, which is the text the model reads security
- Tool “ol_institutional_confluence” rewrote its description, which is the text the model reads security
- Tool “ol_insider_recent_buys” rewrote its description, which is the text the model reads security
- Tool “ol_insider_cluster_scan” rewrote its description, which is the text the model reads security
- Tool “ol_borrower_profile” rewrote its description, which is the text the model reads security
- Tool “ol_bdc_borrower_dispersion” rewrote its description, which is the text the model reads security
- Tool “get_institutional_holders” rewrote its description, which is the text the model reads security
- Tool “get_institutional_consensus” rewrote its description, which is the text the model reads security
- Tool “get_insider_activity” rewrote its description, which is the text the model reads security
- “get_fundamentals” added an optional parameter “years” cosmetic
- “get_corporate_events” added an optional parameter “limit” cosmetic
- “ol_ownership_changes” reworded the description of “limit” cosmetic
- 14 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_13f_holdings” rewrote its description, which is the text the model reads security
- Tool “get_institutional_consensus” rewrote its description, which is the text the model reads security
- Tool “ol_ownership_changes” rewrote its description, which is the text the model reads security
- Tool “ol_bdc_top_borrowers” rewrote its description, which is the text the model reads security
- New tool “get_bdc_holdings” functional
- New tool “get_access_status” functional
- “ol_ownership_changes” added an optional parameter “sort_by” cosmetic
- “get_institutional_consensus” added an optional parameter “funds_per_ticker” cosmetic
- “ol_bdc_top_borrowers” reworded the description of “limit” cosmetic
- “get_institutional_consensus” reworded the description of “top_n” cosmetic
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 +28
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
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 21 Nov 2026 · Probed https://www.oxfordledge.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.oxfordledge.com | CN=WE1,O=Google Trust Services,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | be32319f758cae34131df86c4d5372bb |
| SANs: www.oxfordledge.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.oxfordledge.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| oxfordledge.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.oxfordledge.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.oxfordledge.com/mcp | HTTPS enforced | 301 | https://www.oxfordledge.com/mcp |
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 →
ol_learn_find Find a Lesson ~268
Find an Oxford Ledge LEARN lesson to teach: 40 learning paths and 433 modules written for lifelong students and investors. No arguments lists the paths plus a start_here module; `path` lists one path's modules in teaching order; `query` searches module titles, section headings and glossary terms ('P/E ratio', 'free cash flow'). Each module row carries module_id, title, level, est_minutes, prereqs, check counts and lesson_url. `completed` (module ids the learner has finished; advisory, never stored) picks start_here and next_up by path order and prerequisites. Teach the module with ol_learn_lesson. Educational content, never a recommendation to buy or sell a security. Source: Oxford Ledge LEARN (authored); FREE for every caller, no key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| completed | array | – | Module ids the learner has finished. Advisory; never stored. |
| level | string | – | Only paths at this level. |
| limit | integer | – | Most modules a `query` returns (1..50, default 10). |
| path | string | – | A path id such as 'valuation-101': list its modules in order. |
| query | string | – | Words to search for, e.g. 'P/E ratio'. |
No output schema declared.
No examples provided.
ol_learn_lesson Lesson Step ~264
Teach one Oxford Ledge LEARN module a step at a time. Call with module_id and no step for the outline, then step=0, 1, 2 and so on. A step is one lesson section as body_markdown, plus where the lesson has them: a formula, a table, live filing figures each with its as-of date (market prices are withheld and named in `withheld`), and suggested_calls naming Oxford Ledge tools the learner can try the idea on. A check step carries the question and options, NEVER the answer: ask it exactly as written, wait for the learner, then submit their choice with ol_learn_check. hint: true adds the hint to a check step. The last step is the module check. The teaching protocol rides tool_notes. Source: Oxford Ledge LEARN (authored); FREE for every caller, no key needed; nothing is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| hint | boolean | – | On a check step, include the hint. Only when the learner asks. |
| module_id | string | yes | Module id such as 'val-1', or its slug ('pe-ratio'), or '<path>/<slug>'. |
| step | integer | – | 0-based step; omit it for the outline. |
No output schema declared.
No examples provided.
ol_maturity_wall Debt Maturity Wall ~213
The corporate DEBT MATURITY WALL: scheduled bond/loan maturities aggregated by year -- total_by_year, by_rating, top_issuers_by_year, peak_year, concentration. Amounts are USD MILLIONS (see `units`). `by_rating` splits IG vs HY by an Oxford Ledge LEVERAGE HEURISTIC, NOT agency ratings. Market-wide when `tickers` is omitted, or scoped to up to 50 tickers. Coverage is companies with PARSED maturity schedules only; an issuer with debt and no parsed schedule is NAMED under `unscheduled`, never estimated. LATENCY: a scoped call can fetch each issuer's annual report LIVE from SEC EDGAR -- seconds per issuer, minutes for a cold list. Source: SEC filing debt schedules + balance sheets (Oxford Ledge parse); FREE.
| Name | Type | Req | Description |
|---|---|---|---|
| by_sector | boolean | – | Include the by-sector split (default false). |
| tickers | array | – | Optional issuer symbols (max 50); omit for market-wide. |
No output schema declared.
No examples provided.
ol_operating_kpis Operating KPIs ~241
Industry OPERATING KPIs for ONE issuer -- the operational numbers the income statement hides (same-store sales, RevPAR, load factor, medical-loss ratio, net interest margin, TEU, rig count ...) extracted from SEC filings across 26 configured industries, each switched on by a deployment flag, so live coverage is a subset. Returns the issuer's panel {ticker, industry, metrics, available, partial, total_metrics, period, as_of, provenance, caveat, ...}. Anonymous callers get at most 3 rows (partial, total_metrics says how many); keyed callers get the full panel. Values are AS-REPORTED and confidence-gated. available=false cannot tell an uncovered industry from a covered issuer with no rows or an outage: do not retry with variations. Per-issuer by design. Source: SEC 10-K/10-Q/8-K exhibits (Oxford Ledge parse); FREE.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Issuer symbol, e.g. DAL, MAR, HCA, JPM, DAC (single issuer, mandatory). There is deliberately no cross-issuer KPI screen: panels are per-issuer by design. |
No output schema declared.
No examples provided.
ol_ownership_changes Ownership Changes ~256
Use for 'are institutions buying or selling X?': each fund's position in one ticker classified new / increased / decreased / exited over the last ~4 quarters. For one strict-quarter verdict use ol_institutional_confluence. Returns {summary, ticker, quarters_analyzed, counts, new_positions, increased, decreased, exited, split_suspect, ...}. `counts` is always the COMPLETE tally; `limit` bounds EACH row list (default 10, hard cap 250), ranked by `sort_by` (default shares_change: largest buyer first). Pairs whose delta looks like an unconfirmed corporate action are withheld into `split_suspect` with their as-filed counts. Share classes are never summed or netted. Share figures are close approximations. Source: SEC EDGAR 13F-HR (public domain; OL derived).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows per bucket (default 10, hard cap 250); counts are complete regardless. |
| sort_by | string | – | Bucket ranking: shares_change (default, largest buyer / seller first), pct_change, or value (biggest positions). |
| ticker | string | yes | Stock ticker (e.g. AAPL). |
No output schema declared.
No examples provided.
ol_paper_portfolio Paper Portfolio ~227
YOUR paper (practice) portfolio on Oxford Ledge -- the same snapshot the web sandbox at /practice/ renders: {portfolio, positions, totals, position_theses, summary, has_portfolio}. include_history: true adds recent_trades (history_limit 1..50, default 20). A user with NO portfolio gets {has_portfolio: false, how_to_start} -- an honest empty, not an error. Positions are marked to the platform's DELAYED quote at read time. Requires an authenticated Oxford Ledge caller (API key or linked OAuth token) and serves the caller's own portfolio only; the local stdio server gets AUTH_REQUIRED. Never cached. Practice money: _meta.disclaimer says so on every response. Source: Oxford Ledge paper sandbox; FREE. Needs a free Oxford Ledge API key that the client's operator configures.
| Name | Type | Req | Description |
|---|---|---|---|
| history_limit | integer | – | How many recent fills to include when include_history is true (1..50). |
| include_history | boolean | – | Add recent_trades (the last history_limit fills). |
No output schema declared.
No examples provided.
ol_paper_trade Paper Trade ~434
WRITE (opt-in): place a market order in YOUR paper (practice) portfolio -- the same engine, quote, fills and rejections as the web sandbox; no real money, no real account. One of TWO mutating tools here (the other is reading_list_annotate). DEFAULTS TO A DRY RUN: with _dry_run omitted or true nothing is placed and you get {dry_run: true, tool, args, idempotency_key, preview, message}. Re-call with _dry_run: false AND that same _idempotency_key to execute; a rejection is a normal (non-error) response you must read and relay, and a repeat of the same key returns {replay: true, ...} without placing twice. shares is whole shares, 1..1,000,000; side is buy or sell; thesis (optional, max 250 chars) is the USER's own reason. Requires an API KEY or a linked OAuth token (a browser session cookie is refused). Capped at 20 executed fills per user per UTC day. Practice money: _meta.disclaimer says so on every response. Needs a free Oxford Ledge API key that the client's operator configures.
| Name | Type | Req | Description |
|---|---|---|---|
| _dry_run | boolean | – | Default true: preview the fill (quote, cost, cash after) without placing it. Re-call with false and the returned _idempotency_key to execute. |
| _idempotency_key | string | – | Optional replay-safety key; auto-derived if omitted. A repeat of the same key returns the first result and places nothing. |
| shares | integer | yes | Whole shares, 1..1,000,000 per order (the engine's per-order cap). |
| side | string | yes | buy or sell (market order at the platform's delayed quote). |
| thesis | string | – | Optional: why (max 250 chars). Stored on the fill and shown back to the user beside the position; write it as the USER's reason. |
| ticker | string | yes | Symbol to trade in YOUR paper portfolio (e.g. DAC). |
No output schema declared.
No examples provided.
ol_patents Patent Filings ~220
Recent USPTO patent filings for a ticker (innovation-intensity diligence). Returns {summary, ticker, count, filings}, NEWEST FIRST; `limit` default 50, hard cap 200, so this is a recent slice, never a full portfolio, and `count` is the number RETURNED. TRAP: a non-empty patent_number marks a continuation of an already-granted PARENT, NOT a grant of this application -- read the status field. Filings reflect Oxford Ledge's last on-demand USPTO ingest for the ticker, not a schedule; an unreachable store is REFUSED (DATA_UNAVAILABLE), never served as count 0. Source: USPTO (public domain); FREE. ATTRIBUTION: every filing field is USPTO ODP verbatim EXCEPT `ticker`, which is an Oxford Ledge applicant-name resolution, not a USPTO field.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max filings (default 50, hard cap 200). |
| ticker | string | yes | Stock ticker (e.g. GOOGL). |
No output schema declared.
No examples provided.
ol_peer_fundamentals Peer Fundamentals ~222
Side-by-side latest-fiscal-year fundamentals for a peer set (the FIRST 6 unique tickers; the rest are named in `dropped`). Returns {summary, count, peers, dropped, as_of}; a peer is {ticker, available, fiscal_year, revenue, net_income, eps_diluted, free_cash_flow, gross_margin_pct, ebit_margin_pct, debt_to_assets_pct, current_ratio, stockholders_equity}. Dollar figures are whole USD; *_pct are percentage numbers. ONE YEAR ONLY -- no history (use get_fundamentals). Fiscal years are each filer's own, so peers are NOT calendar-aligned. A ticker without XBRL coverage returns {ticker, available: false} (no metric keys), never dropped. No price leg, so no P/E or EV multiples. Source: SEC EDGAR company-facts XBRL; one cold EDGAR fetch per ticker.
| Name | Type | Req | Description |
|---|---|---|---|
| tickers | array | yes | 2-6 ticker symbols to compare (hard-capped at 6). |
No output schema declared.
No examples provided.
ol_short_interest_trend Short Interest Trend ~187
FINRA short-interest trend for one ticker: the biweekly settlement-date short-percent series, OLDEST-FIRST. Returns {summary, ticker, count, as_of, trend}; each point is EXACTLY {date (settlement date), shortPct (a PERCENTAGE number)} -- no share counts and no days-to-cover. `points` default 6, max 26 (about one year). A fortnightly SNAPSHOT with a reporting lag, not a live short-float figure; `as_of` is the settlement date, not today. Honest-empty for a ticker FINRA does not publish; an unreachable store is REFUSED (DATA_UNAVAILABLE). Source: FINRA (public); FREE.
| Name | Type | Req | Description |
|---|---|---|---|
| points | integer | – | Readings to return (default 6, max 26). |
| ticker | string | yes | Stock ticker (e.g. GME). |
No output schema declared.
No examples provided.
ol_treasury_debt Treasury Debt Composition ~225
US Treasury debt composition from the Monthly Statement of the Public Debt. Omit BOTH args for the newest month's full class breakdown; pass security_type AND security_class together for that one class's monthly history (only one of them is refused). Returns {summary, rows}. AMOUNTS ARE IN MILLIONS OF USD -- a 28,000,000 value means $28 trillion. The breakdown holds component AND Total rows, so summing a column double-counts. `limit` (series only) default 120 months, hard cap 360. An unreachable store is REFUSED (DATA_UNAVAILABLE). Sibling of get_yield_curve. Source: Treasury.gov MSPD (public domain); FREE.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Monthly points for a series (default 120, hard cap 360). |
| security_class | string | – | Class within the type; '_' for Total rows. Sent only together with security_type. |
| security_type | string | – | e.g. 'Total Public Debt Outstanding'. Sent only together with security_class, for a series. |
No output schema declared.
No examples provided.
reading_list_annotate Reading List Note ~288
WRITE (opt-in): save or update YOUR private note on an Oxford Ledge reading-list entry. One of TWO mutating tools here (the other is ol_paper_trade). DEFAULTS TO A DRY RUN: with _dry_run omitted or true you get a proposal {dry_run: true, tool, args, idempotency_key, message}, not a save. Re-call with _dry_run: false AND that same _idempotency_key to execute; a repeat of the same key returns {replay: true, ...} without writing twice. Requires Researcher tier AND an authenticated Oxford Ledge caller -- the local stdio server has no account context and raises AUTH_REQUIRED. `slug` must already exist on /reading-list; `body` is capped at 500 chars. Notes stay PRIVATE; this tool can never publish one. Needs a free Oxford Ledge API key that the client's operator configures.
| Name | Type | Req | Description |
|---|---|---|---|
| _dry_run | boolean | – | Default true: propose without persisting. Re-call with false to execute. |
| _idempotency_key | string | – | Optional replay-safety key; auto-derived if omitted. |
| body | string | yes | The note text (max 500 chars). Notes are PRIVATE; publishing requires the dashboard flow (age attestation). |
| slug | string | yes | Reading-list entry slug (as on /reading-list). |
No output schema declared.
No examples provided.
search_bdc_borrower BDC Borrower Search ~325
Use first with a borrower's NAME: which BDCs lend to one private-credit borrower, matched fuzzily -- Oxford Ledge's parse of SEC EDGAR BDC schedules of investments (ol-derived), not filer-published data. Returns borrowerName, borrowerNorm (the key ol_bdc_borrower_dispersion and ol_borrower_profile take), description, descriptionSource, industry, aggregates over CURRENT holders (totalHolders, totalParAmount, totalFairValue, avgMarkedPrice) and `holders`, one row per TRANCHE. ABOVE-PAR TRAP: a mark above 100 is not a credit premium until fairValue is checked against cost. `description` is a compiled company profile from public sources, NOT filing text. A miss is {found: false} -- a search miss, not a finding of no BDC exposure. `query` needs 3+ characters; `limit` / `offset` page `holders` only. Source: SEC EDGAR BDC schedules of investments (~45-60 day lag).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max `holders` rows to return (default 5000 = every row; hard cap 5000, refused above). Pages the tranche rows only. |
| offset | integer | – | Rows to skip before the page (default 0; max 5000). Past the end returns an empty page with `page.total` intact. |
| query | string | yes | Borrower/company name to search (e.g. Finastra, Medline); at least 3 characters. |
No output schema declared.
No examples provided.
search_company Company Search ~185
Resolve a company name, ticker or CIK to its SEC identity. Returns {results, count}, up to 20 matches (hard cap); each result carries SEC-EDGAR-derivable identity fields only: ticker, companyName, cik, sicCode, exchange, fiscalYearEnd, tickerStatus (check it before treating a match as a live listing). A null field is OMITTED from the row, so never assume `cik` is present. Matching is a literal substring on ticker / companyName (plus the other class-share punctuation, and a digit-only CIK); former names NOT yet (tool_notes); typos NOT. Once resolved, call get_fundamentals or get_business_summary. Source: Oxford Ledge company profiles, limited to SEC-submission identity fields.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query (company name, ticker, or industry) |
No output schema declared.
No examples provided.
search_news_archive News Archive Search ~184
TF-IDF full-text search over the archived news headlines + the pulse-fact corpus (a lexical index, not embeddings). Returns {query, count, results, index}; each result is {type ('news' | 'fact'), text, score (0-1 cosine), metadata}. `limit` default 20, hard cap 50. The first call after a restart pays the index build (seconds); later calls are fast. RESTRICTED posture: a keyed tool (refuses anonymous callers). For per-ticker archive reads use get_news; for semantic retrieval over SEC filings use ol_filing_search. Needs a free Oxford Ledge API key that the client's operator configures.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return (default 20) |
| query | string | yes | Search query (e.g. 'oil prices', 'Fed rate cut') |
No output schema declared.
No examples provided.
How do I install the Oxford Ledge MCP server?
Oxford Ledge is a hosted endpoint at https://www.oxfordledge.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.oxfordledge.com
claude mcp add --transport http com-oxfordledge-oxford-ledge 'https://www.oxfordledge.com/mcp'
What is the Oxford Ledge MCP server?
Oxford Ledge is an MCP server listed in the public MCP registry as com.oxfordledge/oxford-ledge. Ask your assistant; it reads the public record: SEC filings, 13F, insider trades, BDC loans. This page covers its hosted endpoint (https://www.oxfordledge.com/mcp).
Is the Oxford Ledge MCP server safe to use?
Oxford Ledge scores 68 out of 100 on VerifyMCP. 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 Oxford Ledge MCP server expose?
Oxford Ledge exposes 65 tools: get_13f_holdings, get_access_status, get_activist_stakes, get_anomaly_flags, get_bdc_holdings, and 60 more. Their descriptions and schemas cost roughly 16,179 tokens of context every time the server is loaded.
Does the Oxford Ledge MCP server require authentication?
No. We connected to Oxford Ledge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Oxford Ledge MCP server still maintained?
Oxford Ledge is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Oxford Ledge MCP server?
VerifyMCP ran 12 checks on Oxford Ledge, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Oxford Ledge: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.