Drillr — The financial MCP for AI agents
REMOTE · GATEWAY.DRILLR.AI · SCANNED AUG 3
The financial MCP for AI agents - 90+ financial tables, SEC filings, signals, alt-data.
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 →
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 Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3013 tokens (~334/item across 9 items; 9 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · gateway.drillr.ai
claude mcp add --transport http ai-drillr-drillr 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": {
"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.
- 3 Aug 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.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Jul 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_tables” rewrote its description, which is the text the model reads security
- “list_tables” reworded the description of “categories” cosmetic
- “list_tables” made “categories” optional cosmetic
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 65
First indexed and scored.
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 3 Aug 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 | 11 Jul 2026 | 9 Oct 2026 | RSA 2048 | SHA256-RSA | ad685bb9d3af92f909661838c9982f9d |
| 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 |
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 |
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.
company_search ~234
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 base — searchable across industry classification, product offerings, business model, segment structure, competitive landscape, supply chain, management background, and customer profile. Coverage: US, Japan, Hong Kong, and China A-shares. `market` accepts one lowercase value or a list from `us | jp | hk | cn`; omit it or pass `[]` for all four. 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'. Omit or pass [] for all four; list order does not set priority. |
| query | string | yes | Natural-language company description |
No output schema declared.
No examples provided.
fiscal_utility ~187
Use to convert between fiscal year/quarter and calendar months for a ticker before filtering period_end columns. Coverage warning: fiscal-year configuration is primarily US, with sparse JP/HK entries and no China A-share coverage in the verified dataset. Do not assume this tool supports a ticker merely because the core equity tables do. Forward: ticker + fiscal_year + fiscal_quarter → period_start/period_end. Reverse: ticker + yyyy_mm → fiscal_year/fiscal_quarter.
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_quarter | integer | — | Quarter 1-4, or 0 for full fiscal year (required for forward conversion) |
| fiscal_year | integer | — | Fiscal year (required for forward conversion) |
| ticker | string | yes | Stock ticker. Coverage is primarily US; sparse JP/HK; no China A-share configuration. |
| yyyy_mm | string | — | Calendar month yyyy-mm (required for reverse conversion) |
No output schema declared.
No examples provided.
get_table_schema ~46
Use BEFORE run_sql when you're unsure which columns a table has. Look up column definitions (name, type, description) for a data table.
| Name | Type | Req | Description |
|---|---|---|---|
| table_name | string | yes | — |
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 ~478
Use for any news, event, development, or statement question about a company, theme, or the market. Covers US, Japan, Hong Kong and A-share markets; The `ticker` filter takes exchange-suffixed symbols: US bare (AAPL), Japan `.T` (7203.T), Hong Kong `.HK` (00700.HK), A-share `.SH`/`.SZ` (600519.SH). 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. US symbols bare (AAPL); other markets carry their exchange suffix — 7203.T,… |
| 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 ~405
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). Core equity coverage: US, Japan, Hong Kong, and China A-shares. Tickers are US bare (AAPL), Japan `.T` (6758.T), Hong Kong `.HK` (00700.HK), and A-shares `.SH`/`.SZ` (600519.SH, 300750.SZ). financial_statements, company_snapshot, and price_volume_history span all four. Specialized tables may be US-only or US+Japan — call get_table_schema before treating an empty result as a finding. Tables by domain (call get_table_schema for detail): - 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.
sec_report_list ~265
Use to discover which SEC filings exist for a ticker before searching content. For the actual content use sec_report_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; HK/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.
sec_report_search ~558
Use when you need narrative content from company filings — risk factors, MD&A, guidance language, deal terms, accounting policies, share structure. For consolidated financial numbers use run_sql on financial_statements instead. Semantic search over the full text of company-filed reports; returns matching passages. Coverage: US + Japan + Hong Kong + China A-shares. US = SEC EDGAR (including foreign issuers' 20-F/6-K). Japan = EDINET, `.T` ticker (6758.T). Hong Kong = HKEX filings, 5-digit `.HK` ticker (00700.HK). A-shares = `.SH`/`.SZ` (600519.SH, 300750.SZ). Parameters: - query (required): natural-language search; phrase it as the concept or section name you want, e.g. "share repurchase authorization", "Risk Factors". Run a few phrasings rather than one broad query. - ticker (required): US bare (NVDA), Japan `.T`, HK `.HK`, A-share `.SH`/`.SZ`, ADRs as their US symbol (SONY). - filing_types (optional): US = SEC form names (10-K, 10-Q, 8-K, 20-F, 6-K, DEF 14A, S-1/F-1, + amendments). Japan = EDINET NUMERIC codes: 120 (annual), 140 (quarterly), 160 (semi-annual). HK/A-share = plain names — annual_report; A-share quarters per-quarter (q1_report, ...); HK quarterly results all quarterly_report. OMIT to search all types. - period_start / period_end (optional): yyyy-mm window; omit to search all history. - top_k (optional): max passages to return (default 10). Scope: indexes ONLY company-filed reports — NOT institutional filings (13F-HR/13D/13G; for those use insider_and_institution_activities with source='institution'). Section targets: non-GAAP reconciliations → earnings 8-K (Ex 99.1); dilution / SBC / buyback → "Shareholders' Equity"; segment breakdown → "Segment Information"; guidance → "Outlook" in MD&A; exec comp → DEF 14A.
| Name | Type | Req | Description |
|---|---|---|---|
| filing_types | array | — | — |
| period_end | string | — | End period YYYY-MM |
| period_start | string | — | Start period YYYY-MM |
| query | string | yes | Search query |
| ticker | string | yes | Stock ticker, e.g. NVDA, 6758.T, 00700.HK, 600519.SH |
| top_k | integer | — | — |
No output schema declared.
No examples provided.
ticker_lookup ~225
Resolve a company name, brand, or ticker substring to canonical ticker(s). Use this FIRST when the user mentions a company by name/brand/nickname before running any ticker-keyed tool. Input: - query (required): company name, brand, or ticker substring, e.g. "Apple", "苹果", "AAPL", "OpenAI" - market (optional): "us" | "jp" | "hk" | "cn" — omit to search all markets Returns up to 5 matches ranked by prefix-hit first, then name length. Returned symbols carry their market suffix: US bare (AAPL), Japan `.T`, Hong Kong 5-digit `.HK` (00700.HK), A-share `.SH`/`.SZ` (600519.SH).
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | — | Optional market filter: 'us' | 'jp' | 'hk' | '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.