Drillr — The financial MCP for AI agents

Created By
Little-Grebe-Inc18 days ago
Drillr is the official financial MCP for AI agents. One hosted endpoint exposes **9 tools** spanning standardized financial data (90+ SQL tables: statements, ratios, earnings, insider, ownership), paragraph-level SEC filing semantic search across 10-K/10-Q/20-F/6-K/S-1/DEF 14A, live cross-asset signals across ~6,900 tickers, and 24 alt-data categories spanning the AI value chain (energy, chips, compute pricing, model adoption, app usage). Coverage: US + Japan equities plus ADRs of global companies; fundamentals back to the 1980s. Built and maintained by Little Grebe Inc.
Overview

What is Drillr?

Drillr is the financial MCP for AI agents. One hosted endpoint, 9 tools, full stack of equity research data — fundamentals, SEC filings, live signals, and 24 alt-data categories. Built and maintained by Little Grebe Inc.

Quick Start

  1. Sign up at drillr.ai
  2. Get an API key at drillr.ai/developer/keys
  3. Drop into your MCP host's config:
{
  "mcpServers": {
    "drillr": {
      "type": "http",
      "url": "https://gateway.drillr.ai/mcp/data",
      "headers": { "Authorization": "Bearer ${DRILLR_API_KEY}" }
    }
  }
}

Works in Claude Code, Cursor, Claude Desktop, Hermes, OpenClaw, and any other MCP-compatible host.

9 Tools

ToolPurpose
run_sqlStandardized financial data over 90+ tables — statements,
ratios, earnings, insider, ownership, prices, alt-data
sec_report_searchParagraph-level semantic search over 10-K / 10-Q /
20-F / 6-K / S-1 / DEF 14A filings
sec_report_listList filings by ticker, form type, and date range
company_searchOntology-based company search — find companies by
business model, supply-chain position, or theme (natural-language query)
ticker_resolveResolve company name / brand / nickname (multilingual)
to canonical ticker(s); call FIRST when user mentions a company by name
signal_listLive cross-asset signal feed
list_tablesDiscover available SQL tables behind run_sql
get_table_schemaInspect columns and types for any SQL table
fiscal_utilityFiscal-period helpers (FY/FQ resolution across companies
with non-calendar years)

关键变化:

  • 8 tools → 9 tools(粗体,跟 v1 SSOT 档 3 风格一致)
  • 8 Tools → ## 9 Tools

  • 新增 ticker_resolve 行(中英文 / 品牌名 → ticker)
  • 顺手把 company_search 的 Purpose 改成更准确的 "ontology-based search"(原来写的 "Resolve tickers" 其实是 ticker_resolve 该干的活,现在两条工具语义清楚分开)
  • list_tables 加一句 "behind run_sql" 让上下文更清楚

What's Covered

  • Global equities: US + Japan, plus ADRs of Chinese / Korean / European companies
  • Fundamentals: financial statements back to the 1980s, 90+ structured tables
  • SEC filings: 10-K / 10-Q / 20-F / 6-K / S-1 / DEF 14A with paragraph-level semantic search
  • Earnings: call transcripts with AI-structured summaries (guidance, risks, segments, Q&A)
  • Markets: equities, ETFs, indices (incl. Nikkei 225 / TOPIX), forex, crypto, commodities
  • Analyst coverage: 565K rating events from 519 firms
  • News & signals: continuously-updating feed across ~6,900 tickers
  • AI value chain alt-data: 24 categories spanning energy, chips, compute pricing, LLM token economics, model benchmarks, app usage, web traffic, patents, papers, government contracts, trade flows

Server Config

{
  "mcpServers": {
    "drillr": {
      "type": "http",
      "url": "https://gateway.drillr.ai/mcp/data",
      "headers": {
        "Authorization": "Bearer ${DRILLR_API_KEY}"
      }
    }
  }
}
Project Info
Created At
18 days ago
Updated At
a day ago
Author Name
Little-Grebe-Inc
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Meteomatics

a day ago
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

19 hours ago