Analytical engine for US-listed equities: screens, rankings, and event studies in plain English.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 9 tools
Each tool has a clearly distinct purpose: describe_data for catalog, query_data for analysis, fetch_page for pagination, get_symbols for symbol lookup, get_account_status for account info, getting_started for onboarding, list_tickets/report_issue for support, recent_queries for history. No overlap.
Most tools follow a verb_noun pattern (describe_data, fetch_page, get_account_status, get_symbols, list_tickets, report_issue), but 'getting_started' uses a gerund and 'recent_queries' is adjective_noun, breaking the pattern. 'query_data' could be interpreted as a noun phrase. Minor inconsistency.
With 9 tools covering data catalog, query, pagination, symbol lookup, account status, onboarding, support, and query history, the count is well-scoped for the server's purpose. Each tool earns its place without redundancy.
The tool surface covers the full lifecycle from discovery (describe_data), analysis (query_data, fetch_page), identification (get_symbols), account management (get_account_status), onboarding (getting_started), to support (list_tickets, report_issue, recent_queries). No obvious gaps for the intended use case.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
list_tickets2 fields changedInput schema / properties / limit / exclusiveMinimumRemoved value: -0Input schema / properties / limit / minimumAdded value: +1recent_queries2 fields changedInput schema / properties / limit / exclusiveMinimumRemoved value: -0Input schema / properties / limit / minimumAdded value: +1query_data1 field changedInput schema / properties / visualizeAdded value: +{
+ "description": "Opt-in charting for the shareable view_url. Default false returns a plain table link (cheapest). Set true when the user wants a chart or stat card: the link is then rendered with the chart type the engine picks from the data shape — a single-row result becomes a \"stat\" card, a multi-period series a line chart, etc. Does not change the JSON rows you receive, only how the view_url renders.",
+ "type": "boolean"
+}list_ticketsquery_data5 fields changedInput schema / properties / clarification_modeAdded value: +{
+ "description": "\"auto\" (default): ambiguous questions are resolved via elicitation or sensible server defaults in one call. \"return\": the server returns status \"clarification_needed\" with the questions + recommended defaults and does NOT proceed (and does not charge); answer by re-calling query_data with `clarifications`. Use \"return\" when silent defaults are not acceptable for your user.",
+ "enum": [
+ "auto",
+ "return"
+ ],
+ "type": "string"
+}Input schema / properties / clarificationsAdded value: +{
+ "description": "Answers to a prior clarification_needed response (pass each question verbatim with your chosen answer). Use together with clarification_mode: \"return\" for a two-step round-trip.",
+ "items": {
+ "properties": {
+ "answer": {
+ "type": "string"
+ },
+ "question": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "question",
+ "answer"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+}Input schema / properties / question / descriptionPrevious value: -"Full natural-language financial question. Not SQL. For complex multi-step workflows (backtests, Monte Carlo, multi-factor scoring), decompose into multiple calls — see mrmarket://capabilities resource."New value: +"ONE natural-language financial question, max 100 words (hard limit — longer is rejected as QUESTION_TOO_LONG, free of charge). Not SQL. Be precise, not redundant: metric(s) + universe/filters + time range is enough; the server picks columns and thresholds. Put ticker lists in `symbols`, never in this text. If 100 words feels tight, you are bundling multiple questions — split them into separate calls (see mrmarket://capabilities for the split test)."Input schema / properties / question / maxLengthAdded value: +4000Input schema / properties / symbolsAdded value: +{
+ "description": "Explicit ticker universe for this question (e.g., a screening batch). STRONGLY preferred over pasting long ticker lists into `question`: the list is applied mechanically as a symbol filter (exact, order-independent), keeps the question readable, and is cheaper. Phrase the question generically (\"Find every golden cross event…\") and put the tickers here.",
+ "items": {
+ "type": "string"
+ },
+ "maxItems": 2000,
+ "type": "array"
+}describe_datafetch_pageget_account_statusget_symbolsgetting_startedquery_datarecent_queriesreport_issueExplainable model signals, drivers, news sentiment, SEC filings and macro data for US stocks.
9,900+ US equities, 64 years of prices, financials, technicals, and earnings. Ask in plain English.
Daily ML stock signals for 4,000+ US stocks, screening, company data and a portfolio optimizer.
Primary-source equity research: scores, screens, filings, insider trades and 13F holdings.
Add one secure layer between your agents and this server.