Drillr — The financial MCP for AI agents
REMOTE · GATEWAY.DRILLR.AI · SCANNED SEP 21
Financial data and research MCP for US/CN/JP equities: filings, statements, ownership, signals.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2877 tokens (~287/item across 10 items; 10 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 Management65
- Stability check failed: schema churn in the 30 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Drillr — The financial MCP for AI agents server?
Drillr — The financial MCP for AI agents is a hosted endpoint at https://gateway.drillr.ai/mcp/data, 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 · gateway.drillr.ai
claude mcp add --transport http ai-drillr-drillr 'https://gateway.drillr.ai/mcp/data'
{
"mcpServers": {
"ai-drillr-drillr": {
"url": "https://gateway.drillr.ai/mcp/data"
}
}
} {
"servers": {
"ai-drillr-drillr": {
"type": "http",
"url": "https://gateway.drillr.ai/mcp/data"
}
}
} [mcp_servers.ai-drillr-drillr] url = "https://gateway.drillr.ai/mcp/data"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-drillr-drillr": {
"type": "remote",
"url": "https://gateway.drillr.ai/mcp/data",
"enabled": true
}
}
} openclaw mcp add ai-drillr-drillr --url 'https://gateway.drillr.ai/mcp/data' --transport streamable-http
mcp_servers:
ai-drillr-drillr:
url: "https://gateway.drillr.ai/mcp/data" {
"McpServers": {
"ai-drillr-drillr": {
"Transport": "http",
"Url": "https://gateway.drillr.ai/mcp/data"
}
}
} assistant mcp add ai-drillr-drillr -t streamable-http -u 'https://gateway.drillr.ai/mcp/data'
{
"mcpServers": {
"ai-drillr-drillr": {
"type": "http",
"url": "https://gateway.drillr.ai/mcp/data"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 16 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ai_adoption” rewrote its description, which is the text the model reads security
- Tool “filing_list” rewrote its description, which is the text the model reads security
- Tool “filing_search” rewrote its description, which is the text the model reads security
- Tool “get_table_schema” rewrote its description, which is the text the model reads security
- Tool “industry_inflections” rewrote its description, which is the text the model reads security
- Tool “news_search” rewrote its description, which is the text the model reads security
- Tool “run_sql” rewrote its description, which is the text the model reads security
- Tool “ticker_lookup” rewrote its description, which is the text the model reads security
- Schema quality: 324 → 287 ▲ functional
- “news_search” reworded the description of “ticker” cosmetic
- 5 Sept 26 −3
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “sec_report_search” was removed ▼ security
- Tool “sec_report_list” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “company_search” rewrote its description, which is the text the model reads security
- Tool “ticker_lookup” rewrote its description, which is the text the model reads security
- Tool coverage: 87% → 97% ▲ functional
- Schema quality: 369 → 324 ▲ functional
- New tool “ai_adoption” functional
- New tool “filing_list” functional
- New tool “filing_search” functional
- New tool “industry_inflections” functional
- “ticker_lookup” reworded the description of “market” cosmetic
- 27 Aug 26 −1
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “fiscal_utility” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 13 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “company_search” rewrote its description, which is the text the model reads security
- Tool “run_sql” rewrote its description, which is the text the model reads security
- Tool “sec_report_list” rewrote its description, which is the text the model reads security
- Tool “sec_report_search” rewrote its description, which is the text the model reads security
- Tool “ticker_lookup” rewrote its description, which is the text the model reads security
- “company_search” reworded the description of “market” cosmetic
- “ticker_lookup” reworded the description of “market” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Aug 26 0
- Tool “run_sql” rewrote its description, which is the text the model reads security
- Schema quality: good → excellent 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 Sept 2026 · Probed https://gateway.drillr.ai/mcp/data
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gateway.drillr.ai | CN=WR3,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | RSA 2048 | SHA256-RSA | 5135b910b58fc76091279ef2d1c5867 |
| SANs: gateway.drillr.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gateway.drillr.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| drillr.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://gateway.drillr.ai/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://gateway.drillr.ai/.well-known/oauth-protected-resource" Protected resource metadata
| Document | https://gateway.drillr.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://gateway.drillr.ai |
| Authorisation server | https://gateway.drillr.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gateway.drillr.ai/mcp/data | Verified | 200 | |
| http (plaintext) | http://gateway.drillr.ai/mcp/data | HTTPS enforced | 302 | https://gateway.drillr.ai/mcp/data |
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 →
ai_adoption ~303
Search concrete enterprise AI applications disclosed in US company earnings calls. Filter by ticker, partially match a company name, search for an application or workflow by name, or use since in YYYY-MM-DD format to include only observations updated on or after that date. Returns a data array ordered by update_date descending. Each result contains ticker, company_name, application_name, first_report_date, update_date, summary (an AI application summary), evolution_summary, business_position, deployment_stage, deployment_scope, value_type, metrics (application-related metrics), and evidence (supporting management quotes, with speaker and section when available). Use this tool to identify where and how a company applies AI, assess deployment maturity, scope, and disclosed value, and inspect the supporting evidence. Use no filters to browse the most recently updated observations. No matches return an empty data array.
| Name | Type | Req | Description |
|---|---|---|---|
| application_name | string | – | Case-insensitive partial application-name match. Empty means no filter. |
| company_name | string | – | Case-insensitive partial company-name match. Empty means no filter. |
| limit | integer | – | Results per page. Default 10, max 10. |
| page | integer | – | One-based page number. Default 1. |
| since | string | – | Only return observations with update_date on or after this date. Use YYYY-MM-DD. |
| ticker | – | – | Optional US ticker filter, up to 10 symbols. Accepts one symbol or a list. Company names are not resolved. |
No output schema declared.
No examples provided.
company_search ~242
Use for qualitative company discovery (industry, business model, supply chain, competitors, management background). For numerical screening (revenue, margins, ratios, growth rates) use run_sql on company_snapshot instead. Drillr's company knowledge graph — searchable across industry classification, product offerings, business model, segment structure, competitive landscape, supply chain, management background, and customer profile. Coverage: US, Japan, Hong Kong, China A-shares, and Korea. `market` accepts one lowercase value or a list from `us | jp | hk | cn | kr`; omit it or pass `[]` for all five. List order does not set priority. Pass a natural-language description (for example, "Hong Kong and China EV battery suppliers"). Returns a structured list of matching companies with context snippets. ONLY for finding a LIST of companies by description.
| Name | Type | Req | Description |
|---|---|---|---|
| market | – | – | Optional market filter. Pass one lowercase value or a list from 'us' | 'jp' | 'hk' | 'cn' | 'kr'. Omit or pass [] for all five; list order does not set priority. |
| query | string | yes | Natural-language company description |
No output schema declared.
No examples provided.
filing_list ~262
Use to discover which SEC filings exist for a ticker before searching content. For the actual content use filing_search instead. List indexed SEC filings for a given ticker with a summary header. Returns: summary (period coverage, per-type counts) + table of up to 50 filings (fiscal_year, fiscal_quarter, filing_type, filing_date, period_start, period_end). filing_types filter: omit for main reports only (US 10-K/10-Q/20-F/S-1/DEF 14A + /A amendments; JP 120/140/160; A-share annual_report / quarterly_report / q1_report; excludes ad-hoc 8-K/6-K); pass [] for all indexed types; pass explicit allowlist to override.
| Name | Type | Req | Description |
|---|---|---|---|
| filing_types | array | – | Filter by filing type. Omit for default (periodic reports + IPO/shelf registrations + amendments; excludes ad-hoc disclosures). Pass [] for all indexed types. Pass an explicit allowlist to override —… |
| ticker | string | yes | Stock ticker, e.g. NVDA, 6758.T, 00700.HK, 600519.SH |
No output schema declared.
No examples provided.
filing_search ~301
Search one company's SEC filings. Returns `## Facts` (exact as-reported and restated financial values) and `## Passages` (matching filing text) — both come back in one call. `ticker` is REQUIRED. When `## Facts` is empty, read `## Passages` — the figure is usually stated in the filing text. `period_start`/`period_end` match by interval overlap; `fiscal_period` sets granularity (Q1..Q4/H/9M/FY). Pass an explicit period window for the most recent figure.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | Publication cutoff date YYYY-MM-DD. Rows with missing published_at still appear; not a strict point-in-time snapshot |
| fiscal_period | – | – | Q1 | Q2 | Q3 | Q4 | H | 9M | FY, or a list of those |
| period_end | – | – | Calendar end date YYYY-MM-DD (calendar, not fiscal) |
| period_start | string | – | Calendar start date YYYY-MM-DD (calendar, not fiscal; resolve fiscal periods via financial_statements period_start/period_end) |
| period_type | string | – | instant or duration |
| query | string | yes | Natural-language financial metric query |
| ticker | string | yes | Required. Canonical or historical ticker; one only. Resolve company names with ticker_lookup first |
| top_k | integer | – | Max results; 1-30, default 10 |
No output schema declared.
No examples provided.
get_table_schema ~49
Column definitions (name, type, description) for a data table, plus its usage note where one exists: required filters, ticker format, and market coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| table_name | string | yes | – |
No output schema declared.
No examples provided.
industry_inflections ~346
Search industry inflections identified through structured research of earnings calls held by US-listed companies, including the change mechanism, impact scope, market attention and affected companies. All filters are optional and combine with AND. With no filters, returns the newest first page. Results are ordered by `quarter` descending. If nothing matches, returns the text `No relevant industry inflections found.` Returns JSON as `{ "data": [...] }`. Every result contains `quarter`, `name` (English title), `regime_type` (change mechanism), `impact_scope`, `impact_degree` (`limited` | `significant` | `structural`), `attention_verdict` (market-absorption judgment), `change_summary`, `first_seen` (`YYYY-MM-DD`), and `source_tickers` (companies whose calls are primary evidence). When `impact_companies` is true, `company_impacts` contains items with `ticker`, `relation`, `direction`, `magnitude`, `impact_stage`, `evidence_status`, `affected_business`, and `impact`.
| Name | Type | Req | Description |
|---|---|---|---|
| impact_companies | boolean | – | Include the per-company company_impacts list. Default false. |
| keyword | string | – | Optional case-insensitive text contained in the theme name or research summary, up to 200 characters. |
| limit | integer | – | Results per page. Default 10, max 10. |
| page | integer | – | One-based page number. Default 1. |
| ticker | – | – | Optional company filter, up to 10 US ticker symbols. Returns themes where any supplied ticker is a source company or an affected company. Use symbols such as AAPL, not company names. |
No output schema declared.
No examples provided.
list_tables ~276
List alternative-data tables under the given categories. Returns each table's name, one-line purpose, and column names (call get_table_schema if you need column types/comments). Batch up to 5 categories in one call; omit categories, or pass ["all"], to get the category index instead. Use this BEFORE run_sql when you want to explore alt-data — run_sql alone won't tell you which tables exist. Available categories: - Energy & Power — US power plants, electricity prices, regional hourly generation/demand - Data Centers — facilities, GPU clusters, cooling - Semiconductors — AI chip specs, sales, ownership, foundry revenue, customs trade - Compute Pricing — GPU rental, cloud VM spot/on-demand, instance specs - Model Development — model specs, benchmarks, AI companies, AI polling, LLM arena - Inference Economics — LLM API pricing across providers - Macro & Trade — UN Comtrade, US Census trade flows, FRED macro series - Prediction Markets — Polymarket and Kalshi events, markets, trades, daily aggregates - Critical Minerals — USGS mineral deposits, country supply, critical materials
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Altdata category names (see tool description for the list). Omit, or pass "all", for the category index. |
No output schema declared.
No examples provided.
news_search ~400
Use for any news, event, development, or statement question about a company, theme, or the market. The `ticker` filter takes exchange-suffixed symbols. Returns Markdown: a `## Stories` numbered list (each storyline once), then flat `## Events` and `## Claims` tables (claims = attributed statements: analyst actions, corporate guidance, central-bank remarks). The Events `story` column refers back to the Stories number. `sources` counts corroborating reports; `first_reported`/`last_reported` give the reporting span. Lowest-ranked stories are dropped to fit length; the meta line flags how many were omitted. At least one of query/theme/ticker/since/until is required. Per-parameter detail is on the input schema — search_type=claims needs query/ticker/a time window, not theme.
| Name | Type | Req | Description |
|---|---|---|---|
| order_by | string | – | Result ordering. relevance (default) | event_time (newest event time first) | create_time (most recently ingested first). |
| query | string | – | Semantic query (English). One of query/theme/ticker/since/until required. |
| search_type | string | – | all (default) | events | claims (opinions/statements only). |
| since | string | – | ISO8601; filter time_event >= since. |
| theme | string | – | Theme word, resolved to the nearest canonical theme. Not valid with search_type=claims. |
| ticker | – | – | Exact ticker symbol(s) — a single symbol, an array, or a comma-separated string; multiple tickers are an OR/overlap filter. Exchange-suffixed (AAPL, 7203.T, 600519.SH). Company names/brands are NOT r… |
| top_k | integer | – | Story count. Default 10, max 50. |
| until | string | – | ISO8601; filter time_event < until. |
No output schema declared.
No examples provided.
run_sql ~300
PostgreSQL SELECT over financial / market / alt-data tables — returns structured rows. Hard rules (query fails otherwise): - SELECT only, no CTE (`WITH ... AS`) — use subqueries. - Period columns are TEXT, not dates — `period_end` is 'YYYY-MM'. Compare as strings (`period_end >= '2024-01'`); a `::date` cast on it fails. - Filter structured tables by ticker (`WHERE ticker IN ('AAPL','MSFT')`; screening: add `ticker NOT LIKE '%-%'` to drop preferred stock). Tables by domain (get_table_schema gives columns + coverage note): - Market: price_volume_history (OHLCV history; MUST filter ticker + time_frame), index_price, equity_extended_rt (pre/after/overnight quotes) - Fundamentals: financial_statements (GAAP income/balance/cashflow), company_snapshot (ratios, per-share, growth) - Earnings: earning_call_summary, earning_call_calendar - Analyst: analyst_ratings, analyst_ratings_consensus - Ownership: insider_and_institution_activities - 8-K events: executive_change, company_deal_events, debt_issuance, securities_offering - Executives: executive_profile, executive_compensation - Alt-data: macro / industry / trade / AI-supply-chain — call list_tables(categories=[...])
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | PostgreSQL SELECT query |
No output schema declared.
No examples provided.
ticker_lookup ~150
Resolve a company name, brand, or ticker substring to canonical ticker(s). Input: - query (required): company name, brand, or ticker substring, e.g. "Apple", "AAPL", "OpenAI" - market (optional): "us" | "jp" | "cn" — omit to search all markets Returns up to 5 matches ranked by prefix-hit first, then name length; symbols carry their market suffix.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | – | Optional market filter: 'us' | 'jp' | 'cn'. Omit to search all markets. |
| query | string | yes | Company name or ticker substring (case-insensitive). Matches historical names + tickers too. |
No output schema declared.
No examples provided.
What is the Drillr — The financial MCP for AI agents server?
Drillr — The financial MCP for AI agents is listed in the public MCP registry as ai.drillr/drillr. Financial data and research MCP for US/CN/JP equities: filings, statements, ownership, signals. This page covers its hosted endpoint (https://gateway.drillr.ai/mcp/data).
Is the Drillr — The financial MCP for AI agents server safe to use?
Drillr — The financial MCP for AI agents scores 84 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 Drillr — The financial MCP for AI agents server expose?
Drillr — The financial MCP for AI agents exposes 10 tools: filing_list, filing_search, company_search, ticker_lookup, run_sql, and 5 more. Their descriptions and schemas cost roughly 2,629 tokens of context every time the server is loaded.
Does the Drillr — The financial MCP for AI agents server require authentication?
Yes. Drillr — The financial MCP for AI agents asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Drillr — The financial MCP for AI agents server still maintained?
Drillr — The financial MCP for AI agents is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.