# DeltaSignal ATLAS-7 (remote · api.aitrailblazer.net) SEC/XBRL issuer intelligence for crypto public companies via MCP, OpenAPI, x402, and MPP. - Trust score: 66/100 (medium) - Change this week: +7 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-03 ## Components - remote · `api.aitrailblazer.net`: 66/100 (this document), [markdown](https://verifymcp.io/servers/aitrailblazer-deltasignal-atlas-7/api.md), [page](https://verifymcp.io/servers/aitrailblazer-deltasignal-atlas-7/api) ## Channel facts - Endpoint: `https://api.aitrailblazer.net/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.1.4` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-03. - **Endpoint Security**: 74/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 51/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 17193 tokens (~212/item across 81 items; 81 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Capabilities**: 40/100 - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http aitrailblazer-deltasignal-atlas-7 https://api.aitrailblazer.net/mcp ``` ### Codex ```toml [mcp_servers.aitrailblazer-deltasignal-atlas-7] url = "https://api.aitrailblazer.net/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "aitrailblazer-deltasignal-atlas-7": { "type": "remote", "url": "https://api.aitrailblazer.net/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add aitrailblazer-deltasignal-atlas-7 --url https://api.aitrailblazer.net/mcp --transport streamable-http ``` ### Hermes ```yaml mcp_servers: aitrailblazer-deltasignal-atlas-7: url: "https://api.aitrailblazer.net/mcp" ``` ### Other ```json { "mcpServers": { "aitrailblazer-deltasignal-atlas-7": { "type": "http", "url": "https://api.aitrailblazer.net/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-03 (score 66, +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. ### 2026-08-01 (score 65, +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. ### 2026-07-31 (score 64, +3) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-29 (score 61, +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. ### 2026-07-28 (score 60, +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. ### 2026-07-27 (score 59, 0) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-26 (score 59) First indexed and scored. ## MCP tools (81) ### `deltasignal_help` (~294 tokens) DeltaSignal help Use this free read-only discovery-tier tool when the user asks for help, available commands, MCP tools, core concepts, pricing, parser-stable fields, grants, x402, Morning Brief, Company Report, MSTR treasury review, perp adapters, SPECTRA, or examples. Parameters: optional topic, detail, include_examples, question, or query fields; callers may omit all arguments for overview help. Behavior: local and idempotent with no destructive side effects; it does not run paid analysis routes or expose internal-only tools. It translates natural-language orientation requests into the live DeltaSignal MCP/OpenAPI discovery contract and points users to tools/list, /v1/pricing, /v1/contract/fields, and /v1/readiness. It is not a trading, execution, or investment-advice tool and must not expose internal-only tools unless the live public contract lists them. Input parameters: - `detail` (string): Optional detail level. short returns a compact guide; full includes more examples and boundary notes. - `include_examples` (boolean): Include example MCP tool-call payloads and safe next commands. Defaults to true when omitted. - `query` (string): Alias for question for clients that pass a generic query field. - `question` (string): Optional natural-language help question, such as 'what can I ask Delta Signal?' or 'help pricing'. - `topic` (string): Optional help topic. Output parameters: - `data` (object): Free DeltaSignal MCP discovery and orientation response. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_morning_brief` (~206 tokens) DeltaSignal morning brief Use this read-only composite workflow tool as the default first-pass DeltaSignal ATLAS-7 daily scan. It server-enforces the complete morning brief call plan: readiness, daily_changes, risk_distribution, top_stressed with limit 10, alpha_opportunities with limit 10, and alpha_opportunities_audit with limit 10. Parameters: optional output_mode=compact only; do not pass limit, offset, ticker, source_date, or issuer filters because this preset owns exact arguments internally. Behavior: read-only and idempotent; it performs a bounded internal fan-out, has no destructive side effects, and preserves partial results if one required internal call fails. Use it for morning brief, daily brief, daily scan, current risk board, and newsroom first-pass requests; sell company-report or deep-brief issuer reports separately when the user wants drilldown explanation. Input parameters: - `output_mode` (string): Optional response mode. Only compact is accepted in Phase 1. Output parameters: - `data` (object): Server-enforced DeltaSignal morning brief composite response. The data object preserves successful subtool payloads plus a deterministic internal call ledger. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_public_daily_brief` (~213 tokens) DeltaSignal public daily brief Use this read-only composite renderer for customer-facing DeltaSignal Daily Brief artifacts. It server-enforces the morning brief evidence plan, then renders a public-safe HTML brief and copy-ready text with plain-English explanations of risk tiers, top-stressed issuers, alpha screens, deltas, and evidence boundaries. Parameters: optional output_mode=compact only; do not pass ticker, limit, offset, source_date, period, or issuer filters because this preset owns exact arguments internally. Behavior: read-only and idempotent; it calls the bounded morning brief composite, has no destructive side effects, removes internal-only identifiers from the public copy, preserves non-advice language, and returns deterministic HTML plus copy_text for publishing workflows. Use it when the user asks for a public daily brief, customer-facing daily brief, investor-ready risk and opportunity scan, or copy-ready DeltaSignal article based on the current daily evidence. Input parameters: - `output_mode` (string): Optional response mode. Only compact is accepted in Phase 1. Output parameters: - `data` (object): Customer-facing DeltaSignal daily brief response. The data object includes rendered HTML, copy_text, public summary fields, term explanations, and a compact evidence boundary. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_company_report` (~349 tokens) DeltaSignal company report Use this read-only composite workflow tool for the default full single-issuer DeltaSignal ATLAS-7 company report add-on. It server-enforces the complete company report call plan: readiness, company_fundamentals, alpha_signals, peer_ranking, covenant_stress, and SPECTRA field-map support for one normalized ticker. Parameters: ticker is required and normalized to uppercase; period, include_segments, include_related_party, and output_mode=compact are optional. SPECTRA is included when a field-map contract is available for the issuer. Behavior: read-only and idempotent; it performs six internal HTTPS reads, has no destructive side effects, rejects invalid tickers before fan-out, and preserves partial results if a required issuer leg fails. Use it when the user asks for a report, deep dive, issuer brief, or diligence package on one crypto public-company ticker, or when a Morning Brief top-stressed or alpha-screen row needs a separately sold explanation report; use low-level tools only for custom drilldowns. Input parameters: - `include_related_party` (boolean): Request related-party containers from company_fundamentals when available. - `include_segments` (boolean): Request segment containers from company_fundamentals when available. - `output_mode` (string): Optional response mode. Only compact is accepted in Phase 1. - `period` (string): Optional YYYY-MM-DD reporting period to pass to fundamentals, peer ranking, and covenant stress when reproducing a known filing date. - `ticker` (string, required): Required crypto public company ticker. The server trims whitespace and normalizes to uppercase before all internal calls. Examples: RIOT, MARA, COIN, MSTR. Output parameters: - `data` (object): Server-enforced DeltaSignal company report composite response. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_issuer_deep_report` (~422 tokens) DeltaSignal issuer deep report Use this read-only composite workflow tool for a paid filing-backed issuer drilldown when a daily brief pressure or opportunity row needs causality, not just a headline score. It server-enforces a broad issuer evidence plan: readiness, company_fundamentals, covenant_stress, peer_ranking, alpha_signals, SPECTRA field-map, ATLAS history, ATLAS-7 calculation history, CompanyFacts history, point-in-time history, daily_changes, risk_distribution, and top_stressed rank context. Parameters: ticker is required and normalized to uppercase; source_date, source_date_from, source_date_to, as_of_date_from, as_of_date_to, and output_mode=compact are optional reproduction controls. Behavior: read-only and idempotent; it has no destructive side effects, performs bounded internal fan-out, preserves partial failures, and explicitly reports missing evidence instead of inventing filing, liquidity, covenant, crypto-exposure, market-structure, or scenario facts. Use it for GME-style paid reports that must explain why a CRITICAL stress row exists, what filing evidence supports it, what changed, what peer context says, what historical stress path is available, and which sections still require external or future data. Input parameters: - `as_of_date_from` (string): Optional YYYY-MM-DD lower bound for point-in-time CompanyFacts history. - `as_of_date_to` (string): Optional YYYY-MM-DD upper bound for point-in-time CompanyFacts history. - `output_mode` (string): Optional response mode. Only compact is accepted in Phase 1. - `source_date` (string): Optional YYYY-MM-DD source date to reproduce one filing/evidence slice where supported. - `source_date_from` (string): Optional YYYY-MM-DD lower bound for ATLAS history and calculation history. - `source_date_to` (string): Optional YYYY-MM-DD upper bound for ATLAS history and calculation history. - `ticker` (string, required): Required crypto public company ticker. Examples: GME, MSTR, RIOT, MARA, COIN. Output parameters: - `data` (object): Server-enforced DeltaSignal issuer deep report evidence bundle with report-readiness contract and missing-evidence matrix. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_pressure_board` (~166 tokens) DeltaSignal pressure board Use this read-only composite workflow tool for risk and stress monitoring across the current DeltaSignal issuer universe. It server-enforces the pressure-board call plan: readiness, top_stressed with limit 15, and risk_distribution. Parameters: optional output_mode=compact only; do not pass limit, offset, ticker, source_date, or issuer filters because this preset owns exact arguments internally. Behavior: read-only and idempotent; it performs three internal HTTPS reads, has no destructive side effects, never calls issuer-level tools, and preserves partial results if one internal call fails. Use it when the user asks for risk monitoring, pressure board, stress board, top stressed overview, or current risk mix. Input parameters: - `output_mode` (string): Optional response mode. Only compact is accepted. Output parameters: - `data` (object): Server-enforced DeltaSignal pressure board composite response. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_alpha_sweep` (~188 tokens) DeltaSignal alpha sweep Use this read-only composite workflow tool for opportunity and alpha screening across the current DeltaSignal issuer universe. It server-enforces the alpha-sweep call plan: readiness, alpha_opportunities with limit 15, and daily_changes; alpha_opportunities defaults to operating-company issuers. Parameters: optional output_mode=compact only; do not pass limit, offset, ticker, source_date, or issuer filters because this preset owns exact arguments internally. Behavior: read-only and idempotent; it performs three internal HTTPS reads, has no destructive side effects, never calls issuer-level tools, and preserves partial results if one internal call fails. Use it when the user asks for alpha opportunities, opportunity sweep, clean alpha board, or names worth follow-up research; treat the result as a screen requiring issuer drilldown. Input parameters: - `output_mode` (string): Optional response mode. Only compact is accepted. Output parameters: - `data` (object): Server-enforced DeltaSignal alpha sweep composite response. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_quick_ticker_check` (~195 tokens) DeltaSignal quick ticker check Use this read-only composite workflow tool for a fast single-ticker sanity check without the full company-report payload. It server-enforces the quick-check call plan: readiness, covenant_stress, and alpha_signals for one normalized ticker. Parameters: ticker is required and normalized to uppercase; output_mode=compact is optional. Fundamentals, peer ranking, and SPECTRA are intentionally excluded. Behavior: read-only and idempotent; it performs three internal HTTPS reads, has no destructive side effects, rejects invalid tickers before fan-out, and preserves partial results if a required issuer leg fails. Use it when the user asks whether one ticker is clean, stressed, actionable, or needs deeper diligence. Input parameters: - `output_mode` (string): Optional response mode. Only compact is accepted. - `ticker` (string, required): Required crypto public company ticker. The server trims whitespace and normalizes to uppercase before all internal calls. Output parameters: - `data` (object): Server-enforced DeltaSignal quick ticker check composite response. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_readiness` (~169 tokens) DeltaSignal readiness Use this read-only tool before analysis to verify that the DeltaSignal ATLAS-7 data plane is live, fresh, and safe to query. It returns service readiness, active source dates, issuer coverage, quality coverage, debt coverage, live-price status, market regime, and tower-coherence diagnostics. Parameters: none; call it exactly as-is when the user asks if DeltaSignal is ready or whether data freshness is acceptable. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, does not write external systems, and does not handle secrets or payments itself. Use it at the start of an agent workflow, after a deploy, or whenever results should be gated on freshness; use daily_changes for what changed and issuer tools for company-specific analysis. Output parameters: - `data` (object): Readiness and data-freshness diagnostics for the live DeltaSignal ATLAS-7 data plane. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_top_stressed` (~213 tokens) DeltaSignal top stressed issuers Use this read-only screening tool to rank the most stressed crypto public companies in the active DeltaSignal slice. It returns issuer rows sorted by stress, including ticker, period, risk tier, stress values, debt-coverage status, quality flags, linkbase provenance, live-price indicators, and pagination metadata. Parameters: limit is 1-100 and should usually be 5-20 for summaries; offset is only for pagination after a previous screen. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and never writes orders, files, accounts, or wallet state. Use it for portfolio triage, issuer watchlists, and deciding which companies deserve deeper covenant or alpha analysis; use covenant_stress with ticker for detail on one issuer. Input parameters: - `limit` (integer): Maximum issuers to return. Use 5-20 for agent summaries and up to 100 for full screening. - `offset` (integer): Pagination offset for continuing a previous ranked screen. Output parameters: - `data` (object): Ranked stressed issuer screen. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_top_stressed_natural` (~228 tokens) DeltaSignal top stressed Natural Language brief Use this premium read-only Natural Language tool when the user wants the Top Stressed screen explained in human-readable Markdown. It renders compact ATLAS-7 Top Stressed evidence into an audit-grade brief while preserving returned ranks, stress values, quality flags, nulls, source dates, and caveats. Parameters: limit is 1-100, offset paginates, and style is professional, concise, trader, or detailed. Style changes tone and density only, not facts. Behavior: read-only and idempotent; it performs one HTTPS read against the Natural Language route, has no destructive side effects, and never executes trades, wallets, settlements, or writes. Use raw deltasignal_top_stressed for cheap structured JSON and this tool for premium human-facing summaries. Input parameters: - `limit` (integer): Maximum issuers to include in the brief. Use 5-10 for concise human summaries. - `offset` (integer): Pagination offset for continuing a previous ranked screen. - `style` (string): Rendering style. Style changes tone and density only, not facts. Output parameters: - `data` (object): Natural Language Top Stressed response. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_covenant_stress` (~460 tokens) DeltaSignal covenant stress Use this read-only tool for ATLAS-7 covenant stress analysis on crypto public companies. Pass ticker for a single-issuer detail view, or omit ticker to screen the active issuer universe with risk, quality, debt-coverage, linkbase, minimum-stress, limit, and offset filters. It returns filing-backed stress, headroom, risk tier, debt coverage, quality, linkbase provenance, live-price deltas, and metadata needed for covenant-risk research. Parameters: ticker selects detail mode; without ticker, limit/offset paginate list mode, min_stress is 0-100, and risk_tier, quality_flag, debt_coverage_status, and linkbase_only narrow the screen. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not change filings, portfolios, wallets, or account state. Use top_stressed for the default ranked universe, peer_ranking for relative peer context, and alpha_signals when the user asks for opportunity or edge rather than covenant stress. Input parameters: - `debt_coverage_status` (string): Optional debt coverage status filter, such as resolved_nonzero, legitimate_zero_debt, or low_confidence_missing_debt. - `limit` (integer): Maximum rows for list mode. Use 10-25 for concise screens. - `linkbase_only` (boolean): Restrict list mode to issuers backed by SEC XBRL linkbase/rooted facts. - `min_stress` (integer): Optional minimum stress score for list mode. - `offset` (integer): Pagination offset for list mode. - `period` (string): Optional YYYY-MM-DD filing period for ticker detail mode. - `quality_flag` (string): Optional data quality filter for list mode, such as High, Medium, or Low. - `risk_tier` (string): Optional risk tier filter for list mode, such as HIGH, MODERATE, LOW, or UNCLASSIFIED. - `source_date` (string): Optional YYYY-MM-DD DeltaSignal source date for list mode. - `ticker` (string): Optional crypto public company ticker. When set, returns detail for that issuer. Examples: MARA, RIOT, COIN, MSTR. Output parameters: - `data` (object): Covenant stress detail when ticker is supplied, or list-mode response with data and meta when ticker is omitted. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_covenant_stress_natural` (~224 tokens) DeltaSignal covenant stress Natural Language brief Use this premium read-only Natural Language tool when the user wants ticker-specific covenant stress evidence explained in human-readable Markdown. It renders compact ATLAS-7 covenant, leverage, liquidity, filing, and stress evidence into an audit-grade brief while preserving returned ticker, issuer, values, source dates, nulls, quality flags, and caveats. Parameters: ticker is required; date is optional and maps to the evidence period when supported; style is professional, concise, trader, or detailed. Behavior: read-only and idempotent; it performs one HTTPS read against the Natural Language route, has no destructive side effects, and never infers covenant breach, default risk, insolvency, liquidity crisis, or trade direction unless returned by evidence. Input parameters: - `period` (string): Optional YYYY-MM-DD source/evidence period selector. - `style` (string): Rendering style. Style changes tone and density only, not facts. - `ticker` (string, required): Required crypto public company ticker. Examples: RIOT, MARA, COIN, MSTR. Output parameters: - `data` (object): Natural Language Covenant Stress response. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_morning_brief_natural` (~196 tokens) DeltaSignal Morning Brief Natural Language brief Use this premium read-only Natural Language tool when the user wants the server-composed Morning Brief rendered as audit-grade Markdown. It compiles backend-composed compact evidence across readiness, daily changes, risk distribution, top stressed issuers, and alpha opportunities. The renderer never fans out into tools and never generates social drafts or trade recommendations. Parameters: style is professional, concise, trader, or detailed. Date and limit are accepted only where the backend composite supports them. Behavior: read-only and idempotent; it performs the server-enforced Morning Brief workflow, has no destructive side effects, then renders the returned compact evidence as a bounded Natural Language response. Input parameters: - `limit` (integer): Optional compact record limit where supported. - `period` (string): Optional YYYY-MM-DD date selector when supported by the backend composite. - `style` (string): Rendering style. Style changes tone and density only, not facts. Output parameters: - `data` (object): Natural Language Morning Brief response rendered from backend-composed compact evidence. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_peer_ranking` (~233 tokens) DeltaSignal peer ranking Use this read-only tool to compare one crypto public company against its current peer group. It returns peer rank, peer percentile, peer score, stressed leverage, risk tier, debt coverage, quality flags, linkbase provenance, and period/source-date context. Parameters: ticker is required and must be one public-company symbol such as COIN, MSTR, MARA, RIOT, HUT, or CLSK; period is optional and only for reproducing a known filing date. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write external systems or access user accounts. Use it when the user asks whether one issuer is better or worse than peers; use covenant_stress for absolute stress, top_stressed for universe-wide ranking, and alpha_signals for opportunity signals. Input parameters: - `period` (string): Optional YYYY-MM-DD filing period. Omit for the latest peer ranking. - `ticker` (string, required): Required crypto public company ticker. Examples: COIN, MSTR, MARA, RIOT, HUT, CLSK. Output parameters: - `data` (object): Peer ranking and percentile context for one crypto public company. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_alpha_signals` (~331 tokens) DeltaSignal alpha signals Use this read-only tool to retrieve DeltaSignal ATLAS-7 alpha signals for one crypto public company ticker. It returns issuer-level signal evidence such as resilience, treasury pressure, regime fit, phase-one opportunity indicators, and the active source date used by the DeltaSignal data plane. Use it for research triage on supported public-company tickers such as COIN, MSTR, MARA, RIOT, HUT, and CLSK; do not pass crypto asset symbols unless they are listed public-company tickers. Parameters: ticker is required and normalized to uppercase; source_date is optional YYYY-MM-DD and should be used only to replay a known historical DeltaSignal slice. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, does not trade, does not store user data, and does not handle wallet secrets. Usage guidelines: call readiness first if you need service freshness, use covenant_stress for covenant-only questions, use company_fundamentals for raw SEC XBRL facts, and treat the result as issuer intelligence rather than investment advice. Input parameters: - `source_date` (string): Optional DeltaSignal source slice date in YYYY-MM-DD format. Omit this for the latest active slice; set it only when reproducing a prior dated run. - `ticker` (string, required): Required crypto public company ticker symbol. The server normalizes it to uppercase. Good examples: COIN, MSTR, MARA, RIOT, HUT, CLSK. Do not use asset symbols like BTC or ETH unless they are also pu… Output parameters: - `data` (object): Alpha-signal research result for one crypto public company. Scores are issuer-level DeltaSignal values from 0 to 100 when present. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_alpha_opportunities` (~396 tokens) DeltaSignal alpha opportunities Use this read-only screening tool to rank the active DeltaSignal issuer universe by deterministic Phase 1 alpha score. It returns opportunity rows with ticker, CIK/entity metadata when available, issuer type, raw alpha score, board rank score, risk tier, debt coverage, quality, treasury, regime, and provenance fields. Parameters: limit is 1-100; source_date replays a known YYYY-MM-DD slice; risk_tier, quality_flag, issuer_type, include_funds, and debt_coverage_status narrow the screen. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not handle wallets, payments, orders, or account state. Default behavior returns operating-company issuers. Use include_funds=true or issuer_type=etf_trust|fund_vehicle|all only when the user asks for ETF, trust, fund, or product-vehicle screens. High scores are drilldown candidates, not standalone conclusions. Input parameters: - `debt_coverage_status` (string): Optional debt coverage filter such as resolved_nonzero, legitimate_zero_debt, or low_confidence_missing_debt. - `include_funds` (boolean): Set true to include ETF, trust, fund, and product-vehicle rows in the screen. - `issuer_type` (string): Optional issuer-type filter: operating_company, etf_trust, fund_vehicle, foreign_issuer, unresolved_identifier, or all. - `limit` (integer): Maximum rows to return. Use 10-25 for agent summaries and up to 100 for full screening. - `quality_flag` (string): Optional normalized quality filter such as high, medium, low, or unknown. - `risk_tier` (string): Optional risk tier filter such as HIGH, MODERATE, LOW, or UNCLASSIFIED. - `source_date` (string): Optional DeltaSignal source slice date in YYYY-MM-DD format. Output parameters: - `data` (object): Ranked Phase 1 alpha-opportunity screen for the active DeltaSignal issuer universe. The default screen focuses on operating-company issuers and requires issuer drilldown; ETF/trust/fund/product vehic… - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_alpha_opportunities_audit` (~344 tokens) DeltaSignal alpha opportunities audit Use this read-only diagnostic tool to explain why the alpha-opportunity board includes, excludes, or demotes rows. It returns issuer-type, identity, quality-gate, and raw-alpha-versus-board-rank summaries from the same scoring universe used by deltasignal_alpha_opportunities. Parameters: limit is 1-100 for bounded samples; source_date replays a known YYYY-MM-DD slice; issuer_type narrows the audit to operating_company, etf_trust, fund_vehicle, foreign_issuer, unresolved_identifier, or all; include_rows=true attaches full publishable audit rows and should be used only for explicit debugging. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not change board scoring, payments, wallets, files, or account state. Use it after deltasignal_alpha_opportunities or deltasignal_alpha_sweep when the user asks why a high raw alpha row is missing, why ETF/trust/fund rows are excluded by default, why a row was demoted, or whether a screen is safe to summarize. Input parameters: - `include_rows` (boolean): Set true only when the user explicitly asks for the full publishable audit rows. - `issuer_type` (string): Optional issuer-type audit filter: operating_company, etf_trust, fund_vehicle, foreign_issuer, unresolved_identifier, or all. - `limit` (integer): Maximum sample rows to return in each audit sample. Use 10-25 for agent summaries and up to 100 for broad debugging. - `source_date` (string): Optional DeltaSignal source slice date in YYYY-MM-DD format. Output parameters: - `data` (object): Alpha-opportunity board audit explaining issuer-type filters, identity quality, quality gates, and raw-alpha versus board-rank demotions. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_company_fundamentals` (~278 tokens) DeltaSignal company fundamentals Use this read-only tool to retrieve SEC XBRL-backed fundamentals for one crypto public company ticker. It returns filing period, entity identifiers, filing form, core financial values, provenance, and optional segment or related-party containers when requested. Parameters: ticker is required; period is optional YYYY-MM-DD; include_segments and include_related_party request additional containers when available and otherwise return availability metadata. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not modify SEC data, accounts, files, or wallets. Use it when the user asks for revenue, net income, assets, cash, liabilities, equity, SEC filing context, or fact provenance; use alpha_signals or covenant_stress for modeled signal interpretation. Input parameters: - `include_related_party` (boolean): Request related-party transaction container when available. Current runtime returns availability metadata even when related-party facts are not populated. - `include_segments` (boolean): Request segment fact container when available. Current runtime returns availability metadata even when segment facts are not populated. - `period` (string): Optional YYYY-MM-DD reporting period. Omit for the latest available filing period. - `ticker` (string, required): Required crypto public company ticker. Examples: COIN, MSTR, MARA, RIOT, HUT, CLSK. Output parameters: - `data` (object): SEC XBRL-backed fundamentals for one crypto public company ticker. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_atlas_history` (~300 tokens) DeltaSignal ATLAS history Use this read-only tool to retrieve a historical ATLAS-7 covenant and stress series for one crypto public company ticker. It returns one compact row per ATLAS source_date, including debt, crypto fair value, BTC holdings, stress, risk tier, live-price fields, quality flags, and provenance needed for mNAV and Mirror Pulse joins. Parameters: ticker is required; source_date_from and source_date_to bound the inclusive ATLAS source-date range; limit defaults to 500 and is capped at 2000; offset paginates the dated series. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not apply the latest ATLAS snapshot retroactively across history. Use this when the user needs historical ATLAS data, MSTR/Strategy time series, mNAV backtests, Mirror Pulse joins, or dated stress/risk snapshots. Input parameters: - `limit` (integer): Maximum dated rows to return. Defaults to 500 and is capped at 2000. - `offset` (integer): Pagination offset over dated ATLAS rows. - `source_date_from` (string): Optional inclusive ATLAS source-date lower bound in YYYY-MM-DD format. - `source_date_to` (string): Optional inclusive ATLAS source-date upper bound in YYYY-MM-DD format. - `ticker` (string, required): Required crypto public company ticker. Examples: MSTR, COIN, MARA, RIOT. Output parameters: - `data` (object): Historical ATLAS-7 issuer time series keyed by source_date. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_atlas7_calculation_history` (~351 tokens) DeltaSignal ATLAS-7 complete calculation history Use this read-only tool when agents need the complete ATLAS-7 calculation bundle for an issuer and source_date. It assembles one calculation-history row from the existing ATLAS-7 precomputed surfaces: covenant stress, company fundamentals, peer ranking, alpha signals, alpha score breakdown, market regime context, SPECTRA inputs, quality flags, provenance, source fields, and hashes. Parameters: source_date replays one YYYY-MM-DD ATLAS-7 slice; source_date_from/source_date_to can page recent slices; ticker or CIK narrows to one issuer; mode=compact by default and full includes source_fields_json. Behavior: read-only and idempotent; it has no destructive side effects and performs no wallet, settlement, or trading actions. Use this before historical report rendering so agents do not mix latest-only fields into a historical answer. Input parameters: - `cik` (string): Optional CIK filter. Bare digits or CIK-prefixed digits are accepted. - `limit` (integer): Maximum calculation rows to return. Defaults to 25 and is capped at 100 through MCP. - `mode` (string): Optional response mode: compact or full. Compact omits source_fields_json. - `offset` (integer): Pagination offset over calculation rows. - `source_date` (string): Optional exact ATLAS-7 source date in YYYY-MM-DD format. Defaults to latest when no range is supplied. - `source_date_from` (string): Optional inclusive source-date lower bound in YYYY-MM-DD format. - `source_date_to` (string): Optional inclusive source-date upper bound in YYYY-MM-DD format. - `ticker` (string): Optional issuer ticker, for example MSTR. Output parameters: - `data` (object): Complete ATLAS-7 calculation-history rows keyed by source_date and issuer. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_atlas7_companyfacts_history` (~360 tokens) DeltaSignal ATLAS-7 CompanyFacts history Use this read-only tool to retrieve compact SEC CompanyFacts/XBRL materialization rows for the crypto public-company universe or a specific ticker/CIK. It returns one compact row per issuer for a materialized companyfacts source_date, including tag counts, crypto/digital-asset flags, top tags, taxonomies, evidence hashes, and fact source pointers. Parameters: source_date replays a known YYYY-MM-DD materialization slice; ticker or cik optionally narrows to one issuer; limit defaults to 25 and is capped at 250; offset paginates the universe. Behavior: read-only and idempotent; it performs no writes, has no destructive side effects, and never returns the raw facts_payload, so use fact_source_pointer plus evidence_hash for drilldown/audit. Use this for Mirror Pulse or ATLAS-7 historical joins when you need the compact issuer-level CompanyFacts inventory for all 215 crypto companies. Input parameters: - `cik` (string): Optional SEC CIK. Accepts bare digits or CIK-prefixed form and normalizes to 10 digits. - `include_summary` (boolean): Include the compact summary JSON object in each row. - `limit` (integer): Maximum issuer rows to return. Defaults to 25 and is capped at 250. - `mode` (string): Optional response mode. Use compact by default; summary includes the compact summary object. - `offset` (integer): Pagination offset over compact issuer rows. - `source_date` (string): Optional materialized CompanyFacts source date in YYYY-MM-DD format. Defaults to the latest materialized source date. - `ticker` (string): Optional public-company ticker. Omit with cik to page the full materialized crypto issuer universe. Output parameters: - `data` (object): Compact materialized SEC CompanyFacts rows keyed by source_date and issuer. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_atlas7_point_in_time_history` (~342 tokens) DeltaSignal ATLAS-7 point-in-time factor history Use this read-only structured history tool when Mirror Pulse, backtests, or agents need daily ATLAS-7 CompanyFacts-derived factor rows keyed by as_of_date. It returns point-in-time-safe rows derived from the latest CompanyFacts archive by applying only facts with filed <= as_of_date; rows are retrospective recomputations and include lookahead safety flags. Parameters: optional ticker or CIK, source_date, as_of_date_from, as_of_date_to, mode=compact|full, limit, and offset. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, does not generate Natural Language, and never executes trades, wallets, or settlement flows. Use compact mode by default for Mirror Pulse joins; use full mode only for selected audit pages because factor_payload can be larger. Input parameters: - `as_of_date_from` (string): Optional inclusive as-of date lower bound in YYYY-MM-DD format. - `as_of_date_to` (string): Optional inclusive as-of date upper bound in YYYY-MM-DD format. - `cik` (string): Optional CIK filter. Bare digits or CIK-prefixed digits are accepted. - `limit` (integer): Maximum daily factor rows to return. Defaults to 250 on REST and is capped lower on MCP. - `mode` (string): Optional response mode. Use compact by default; full includes factor_payload. - `offset` (integer): Pagination offset for daily factor rows. - `source_date` (string): Optional CompanyFacts archive source date in YYYY-MM-DD format. - `ticker` (string): Optional issuer ticker filter, for example MSTR. Output parameters: - `data` (object): CompanyFacts-derived point-in-time ATLAS-7 factor rows keyed by as_of_date and issuer. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_atlas7_audit_status` (~141 tokens) DeltaSignal ATLAS-7 audit status Use this read-only tool to check whether the Azure-native ATLAS-7 full-universe regression audit is healthy. It reads the latest audit summary artifact from Azure Blob and reports last successful run time, issuer count, operation count, failure counts, historical route status, composite route status, and artifact prefix. Parameters: none. Behavior: read-only and idempotent; it has no destructive side effects, does not run the audit, mutate data, or access raw issuer evidence. Use this before trusting historical ATLAS-7 surfaces in an agent workflow or when an operator asks whether the nightly 215-issuer audit is current. Output parameters: - `data` (object): Latest Azure ATLAS-7 regression audit health summary. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_atlas7_four_level_applicability` (~256 tokens) DeltaSignal ATLAS-7 four-level applicability Use this read-only tool to determine which ATLAS-7 four-level layers are evidence-backed for one issuer or a paginated issuer universe. It reports Level 1 issuer truth, Level 2 market behavior, Level 3 point-in-time basket pressure, and Level 4 capability-gated depth/reference dislocation without promoting legacy compatibility scores or venue context into canonical truth. Parameters: optional ticker, CIK, source_date, mode=compact|full, limit, and offset. Behavior: read-only and idempotent with no destructive side effects; it does not fetch live market data, run ATLAS calculations, place trades, or mutate recorder state. Input parameters: - `cik` (string): Optional issuer CIK filter. Digits only. - `limit` (integer): Maximum issuer rows to return. Defaults to 25 and is capped at 100 through MCP. - `mode` (string): Optional response mode: compact or full. - `offset` (integer): Pagination offset over issuer rows. - `source_date` (string): Optional exact ATLAS issuer-truth source date in YYYY-MM-DD format. - `ticker` (string): Optional issuer ticker filter, for example NVDA or MSTR. Output parameters: - `data` (object): ATLAS-7 four-level applicability/readiness rows for issuer, market, basket, and capability-gated depth/reference evidence. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_risk_distribution` (~147 tokens) DeltaSignal risk distribution Use this read-only tool to summarize the active crypto public company universe by ATLAS-7 risk tier. It returns risk-tier buckets such as HIGH, MODERATE, LOW, and UNCLASSIFIED with issuer counts and percentages. Parameters: none; call it exactly as-is when the user asks for market-wide risk mix or high-level distribution. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write external systems or access user accounts. Use it for market-wide context before issuer drilldown; use top_stressed to name the issuers in the high-risk bucket and use issuer tools for company-level analysis. Output parameters: - `data` (object): Risk-tier distribution for the active DeltaSignal issuer universe. Tier names are object keys such as HIGH, MODERATE, LOW, and UNCLASSIFIED. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_daily_changes` (~139 tokens) DeltaSignal daily changes Use this read-only monitoring tool to retrieve the latest meaningful DeltaSignal daily change snapshot. It highlights tracked crypto filing deltas, newly discovered crypto issuers, source dates, computed timestamps, classification summary, and change statistics. Parameters: none; call it exactly as-is when the user asks what changed today or needs a monitoring summary. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write notifications, files, accounts, or wallet state. Use it for daily monitoring and freshness narratives; use readiness for service health and issuer-specific tools for detailed research on any ticker it mentions. Output parameters: - `data` (object): Latest promoted DeltaSignal daily change snapshot for monitoring workflows, with separate compute and CompanyFacts artifact freshness fields. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_daily_change_evidence` (~240 tokens) DeltaSignal daily change evidence Use this read-only drilldown tool only when the user asks why one issuer or CIK was flagged in daily changes. It returns paginated raw CompanyFacts tag evidence for a specific ticker or CIK, plus page metadata and issuer identity. Parameters: ticker or cik is required; source_date is optional; limit defaults to 100 and is capped at 250; offset paginates the raw tag page. Behavior: read-only and idempotent; it performs one internal daily-changes read, filters evidence for one issuer/change, and has no destructive side effects. Do not use it for routine monitoring, Morning Brief, or Alpha Sweep unless the user explicitly asks for proof. Input parameters: - `cik` (string): Optional SEC CIK. Required when ticker is absent. - `limit` (integer): Maximum raw tag evidence rows to return. Default 100, maximum 250. - `offset` (integer): Pagination offset for raw tag evidence rows. - `source_date` (string): Optional CompanyFacts activity source date. Omit for latest activity date. - `ticker` (string): Optional public-company ticker. Required when cik is absent. Output parameters: - `data` (object): Issuer-specific paginated daily-change evidence. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_spectra_field_map` (~187 tokens) DeltaSignal SPECTRA field map Use this read-only tool to retrieve the SPECTRA historical field-map contract for one crypto public company ticker. It returns issuer-specific filing choreography and pressure-map context used by DeltaSignal report and visualization workflows. Parameters: ticker is required and must be one public-company symbol such as RIOT, MARA, COIN, MSTR, HUT, or CLSK. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write files, wallets, orders, or account state. Use it when the user asks for SPECTRA, field-map, historical pressure, filing choreography, or report-visualization context for a named issuer. Input parameters: - `ticker` (string, required): Required crypto public company ticker symbol. Examples: RIOT, MARA, COIN, MSTR, HUT, CLSK. Output parameters: - `data` (object): SPECTRA historical field-map contract for one issuer. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_coinbase_perp_constituents` (~281 tokens) DeltaSignal Coinbase perp constituents Use this read-only tool to retrieve persisted constituent registries for one Coinbase thematic or index perp product such as COIN50-PERP-INTX or AI-PERP-INTX. It returns additive curated constituent overlays grouped by source date, preserving the evidence boundary that these are persisted registry rows rather than live exchange-native constituent APIs. Parameters: product is required; optional source_date or source_date_from/source_date_to, mode=compact|full, limit, and offset. Behavior: read-only and idempotent with no destructive side effects; it does not fetch live exchange data, place trades, or mutate recorder state. Input parameters: - `limit` (integer): Maximum grouped constituent registries to return. Defaults to 25 and is capped at 100 through MCP. - `mode` (string): Optional response mode: compact or full. - `offset` (integer): Pagination offset over grouped constituent registries. - `product` (string, required): Required Coinbase thematic or index perp product_id or contract_symbol, for example COIN50-PERP-INTX. - `source_date` (string): Optional exact source date in YYYY-MM-DD format. - `source_date_from` (string): Optional inclusive source-date lower bound in YYYY-MM-DD format. - `source_date_to` (string): Optional inclusive source-date upper bound in YYYY-MM-DD format. Output parameters: - `data` (object): Coinbase thematic/index perp constituent registries read from persisted additive overlay rows. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_coinbase_perp_calculation_history` (~288 tokens) DeltaSignal Coinbase perp calculation history Use this read-only tool to retrieve Coinbase INTX perp market-factor history assembled from persisted recorder evidence. It returns venue-pure calculation-history rows with contract identity, ATLAS-shaped factor fields, deltas, quality state, and optional full market inputs or lineage. Parameters: optional product or underlying_ticker filters, source_date or source_date_from/source_date_to, mode=compact|full, limit, and offset. Behavior: read-only and idempotent with no destructive side effects; it does not fetch live exchange data on demand, place trades, or mutate recorder state. Input parameters: - `limit` (integer): Maximum calculation-history rows to return. Defaults to 25 and is capped at 100 through MCP. - `mode` (string): Optional response mode: compact or full. - `offset` (integer): Pagination offset over calculation-history rows. - `product` (string): Optional Coinbase INTX product_id or contract_symbol filter, for example AI-PERP-INTX. - `source_date` (string): Optional exact source date in YYYY-MM-DD format. - `source_date_from` (string): Optional inclusive source-date lower bound in YYYY-MM-DD format. - `source_date_to` (string): Optional inclusive source-date upper bound in YYYY-MM-DD format. - `underlying_ticker` (string): Optional underlying ticker filter, for example AI or COIN50. Output parameters: - `data` (object): Coinbase INTX perp market-factor history assembled from persisted venue-pure recorder evidence. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_coinbase_perp_factors` (~278 tokens) DeltaSignal Coinbase perp factor history Use this read-only tool when the user wants persisted Coinbase INTX market-factor history for one perp product. It returns one product's venue-pure factor history, including factor rows, deltas, quality state, and optional full market inputs or lineage. Parameters: product is required; optional source_date or source_date_from/source_date_to, underlying_ticker, mode=compact|full, limit, and offset. Behavior: read-only and idempotent with no destructive side effects; it does not fetch live exchange state or write recorder artifacts on demand. Input parameters: - `limit` (integer): Maximum factor-history rows to return. Defaults to 25 and is capped at 100 through MCP. - `mode` (string): Optional response mode: compact or full. - `offset` (integer): Pagination offset over factor-history rows. - `product` (string, required): Required Coinbase INTX product_id or contract_symbol, for example AI-PERP-INTX. - `source_date` (string): Optional exact source date in YYYY-MM-DD format. - `source_date_from` (string): Optional inclusive source-date lower bound in YYYY-MM-DD format. - `source_date_to` (string): Optional inclusive source-date upper bound in YYYY-MM-DD format. - `underlying_ticker` (string): Optional underlying ticker filter to keep product routing explicit. Output parameters: - `data` (object): Coinbase INTX perp market-factor history assembled from persisted venue-pure recorder evidence. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_coinbase_perp_rankings` (~268 tokens) DeltaSignal Coinbase perp rankings Use this read-only tool to rank Coinbase INTX perp products by the latest persisted market_alpha row per product within the requested scope. It returns one latest factor row per product, ordered into a board with rank, percentile, ranking_score, ranking_band, and preserved factor provenance. Parameters: optional product or underlying_ticker filters, source_date or source_date_from/source_date_to, mode=compact|full, limit, and offset. Behavior: read-only and idempotent with no destructive side effects; it performs no live exchange fetches, order placement, or settlement flows. Input parameters: - `limit` (integer): Maximum ranked products to return. Defaults to 25 and is capped at 100 through MCP. - `mode` (string): Optional response mode: compact or full. - `offset` (integer): Pagination offset over ranked products. - `product` (string): Optional Coinbase INTX product_id or contract_symbol filter. - `source_date` (string): Optional exact source date in YYYY-MM-DD format. - `source_date_from` (string): Optional inclusive source-date lower bound in YYYY-MM-DD format. - `source_date_to` (string): Optional inclusive source-date upper bound in YYYY-MM-DD format. - `underlying_ticker` (string): Optional underlying ticker filter. Output parameters: - `data` (object): Coinbase INTX perp rankings built from the latest persisted factor row per product within scope. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_coinbase_perp_market_spectra` (~253 tokens) DeltaSignal Coinbase perp market SPECTRA Use this read-only tool to retrieve the market SPECTRA field map for one Coinbase INTX perp product. It converts persisted market-factor history into field pressure, stored energy, compression, release, and current_read labels while preserving the underlying numeric factor evidence. Parameters: product is required; optional source_date or source_date_from/source_date_to, limit, and offset. Behavior: read-only and idempotent with no destructive side effects; it does not create factors, reconstruct missing depth, or override the underlying factor rows. Input parameters: - `limit` (integer): Maximum factor-history points to include before SPECTRA assembly. Defaults to 25 and is capped at 100 through MCP. - `offset` (integer): Pagination offset over the factor-history points used for the field map. - `product` (string, required): Required Coinbase INTX product_id or contract_symbol, for example AI-PERP-INTX. - `source_date` (string): Optional exact source date in YYYY-MM-DD format. - `source_date_from` (string): Optional inclusive source-date lower bound in YYYY-MM-DD format. - `source_date_to` (string): Optional inclusive source-date upper bound in YYYY-MM-DD format. Output parameters: - `data` (object): Coinbase INTX perp market SPECTRA field map derived from persisted factor history. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_synthetic_etf_pressure_state` (~294 tokens) DeltaSignal Synthetic ETF pressure state Use this read-only composite tool when the user asks for the current pressure state of the Delta Signal Synthetic AI 10 ETF or Synthetic Tech100 ETF. It returns one user-facing pressure-state envelope assembled from persisted constituent registry evidence and persisted market-factor/SPECTRA history. Parameters: product is required and accepts AI10, Synthetic AI10 ETF, AI-PERP-INTX, Tech100, or TEK-19DEC30-CDE; optional source date filters, limit, and offset constrain the factor-history window. Behavior: read-only and idempotent with no destructive side effects; it does not fetch live exchange state, expose provider branding outside bounded identity lineage, place trades, or mutate recorder state. Input parameters: - `limit` (integer): Maximum factor-history points to inspect before building the pressure state. Defaults to 10 and is capped at 100 through MCP. - `offset` (integer): Pagination offset over factor-history points used for the pressure state. - `product` (string, required): Required Synthetic ETF or linked product identifier, for example AI10, Synthetic AI10 ETF, or AI-PERP-INTX. - `source_date` (string): Optional exact source date in YYYY-MM-DD format. - `source_date_from` (string): Optional inclusive source-date lower bound in YYYY-MM-DD format. - `source_date_to` (string): Optional inclusive source-date upper bound in YYYY-MM-DD format. Output parameters: - `data` (object): Composite DeltaSignal Synthetic ETF pressure-state envelope. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_synthetic_etf_audit` (~419 tokens) DeltaSignal Synthetic ETF audit payload Use this read-only audit tool when the user asks what factors drive the Delta Signal Synthetic AI 10 ETF state, asks for raw audit evidence, or asks whether the current pressure state is a full four-level ATLAS-7 verdict. It returns current and previous buckets, bucket comparison, factor-history rows, audit-window z-scores including basis_pressure_z, a threshold contract, threshold flags, canonical event status/reasons/blockers, event classification, four-level coverage, bounded constituent contribution rows, presentation-parity status, TRIDENT/liquidation-gradient availability, per-question readiness, provenance, caveats, and quality flags. Parameters: product is required and accepts AI10, Synthetic AI10 ETF, AI-PERP-INTX, Tech100, or TEK-19DEC30-CDE; optional source-date filters override window_days; optional limit and offset paginate factor-history rows. Behavior: read-only and idempotent with no destructive side effects; it must label partial coverage explicitly and must not convert a linked-market read into issuer truth, exchange-native microstructure truth, a trade signal, or investment advice. Input parameters: - `include_export` (boolean): Whether to include export availability metadata. Defaults true. - `limit` (integer): Maximum factor-history rows to return. Defaults to 100 and is capped at 100 through MCP. - `offset` (integer): Pagination offset over factor-history rows used for audit. - `product` (string, required): Required Synthetic ETF or linked product identifier, for example AI10, Synthetic AI10 ETF, or AI-PERP-INTX. - `source_date` (string): Optional exact source date in YYYY-MM-DD format. Overrides window_days. - `source_date_from` (string): Optional inclusive source-date lower bound in YYYY-MM-DD format. - `source_date_to` (string): Optional inclusive source-date upper bound in YYYY-MM-DD format. - `window_days` (integer): Default audit lookback when no source-date filters are supplied. Defaults to 7 and is capped at 30. Output parameters: - `data` (object): Audit-grade DeltaSignal Synthetic ETF payload. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_thesis_readiness` (~344 tokens) DeltaSignal thesis readiness Use this read-only tool before paid ATLAS evidence evaluation to determine whether a user-written issuer thesis is monitorable. It scores issuer specificity, thesis clarity, evidence alignment, watch-condition quality, falsifiability, weakening criteria, materiality, provenance requirements, non-execution boundary, and monitoring readiness. Parameters: ticker and thesis_text are required; watch_conditions, evidence_surfaces, cadence, lookback_days, output_mode, and provenance_required are optional. Behavior: read-only and idempotent; it performs deterministic local validation only, has no destructive side effects, does not call DeltaSignal evidence routes, does not execute wallets or x402 settlement, and never returns buy, sell, hold, target-price, allocation, or order instructions. Use it as the free or low-cost thesis-structuring layer; use paid thesis baseline or evaluation only after readiness is monitor_ready or needs_cleanup. Input parameters: - `cadence` (string): Optional monitoring cadence. - `evidence_surfaces` (array): Optional ATLAS evidence surfaces expected to evaluate the thesis. - `lookback_days` (integer): Optional monitoring lookback window in days. - `output_mode` (string): Optional response mode. - `provenance_required` (boolean): Whether source dates, route status, and evidence provenance are required before evidence-backed evaluation. - `thesis_text` (string, required): Required user-authored thesis text. It should state what must remain true, what weakens it, and what falsifies it. - `ticker` (string, required): Required issuer ticker. Examples: MSTR, RIOT, MARA, COIN. - `watch_conditions` (array): Optional structured watch conditions extracted from the thesis. Output parameters: - `data` (object): Deterministic thesis readiness score. This response uses no ATLAS evidence and only decides whether the thesis is suitable for monitoring. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_thesis_create` (~302 tokens) DeltaSignal accountless thesis create Use this MCP beta write tool to create an accountless Thesis Monitor object protected by a one-time capability token. It stores the user-authored thesis and watch conditions in backend memory for the current runtime and returns thesis_id plus access_token once; persistent Postgres storage and x402 paid evaluation are the next implementation phase. Parameters: ticker and thesis_text are required; watch_conditions, cadence, lookback_days, output_mode, and provenance_required are optional. Behavior: non-trading write operation; it creates one in-memory thesis record with a fresh capability token, has no destructive side effects outside that requested object, does not call DeltaSignal evidence routes, does not execute wallet settlement, and refuses buy, sell, hold, target-price, allocation, or order instructions. Use it after thesis readiness when the user wants to start a lightweight MCP/x402 thesis-monitor flow without traditional accounts. Input parameters: - `cadence` (string): Optional monitoring cadence. - `lookback_days` (integer): Optional monitoring lookback window in days. - `output_mode` (string): Optional response mode. - `provenance_required` (boolean): Whether source dates, route status, and evidence provenance are required before evidence-backed evaluation. - `thesis_text` (string, required): Required user-authored thesis text. - `ticker` (string, required): Required issuer ticker. Examples: MSTR, RIOT, MARA, COIN. - `watch_conditions` (array): Optional structured watch conditions extracted from the thesis. Output parameters: - `data` (object): Accountless thesis creation response. The access_token is returned once and must be kept by the client; the server stores only its hash. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_generate_article_tripcode` (~573 tokens) DeltaSignal article TripCode generate Use this read-only identity tool to generate a deterministic TF-SUB resolver object for a DeltaSignal-owned article or narrative research node. Parameters: primary issuer/ticker, title, research_slug, research_date, and optional research_version define the stable DeltaSignal identity. Substack post_id, canonical_url, slug, and published_at are publication metadata only and must not change the TripCode. Behavior: idempotent and local with no destructive side effects; it does not write Azure Blob, does not mutate Substack, and does not call wallets or x402 settlement. Use the returned TripCode in the article subtitle and the returned canonical blob paths in the authoring/sync pipeline. Input parameters: - `article_body` (string): Optional article body used only for content hash/provenance, not canonical TripCode identity. - `author` (string): Article author or publication author. - `canonical_url` (string): Optional public canonical URL. Secondary publication metadata only. - `claim_summary` (array): Optional claim summary bullets. - `invalidation_checklist` (array): Optional invalidation checklist. - `issuer` (string): Primary issuer symbol when ticker is not supplied. - `linked_ds_tripcodes` (array): Optional linked TF-DS signal TripCodes. - `linked_xbrl_tripcodes` (array): Optional linked TF-XBRL evidence TripCodes. - `monitoring_checklist` (array): Optional monitoring checklist. - `platform` (string): Publication platform. Defaults to Substack. - `post_id` (string): Optional Substack post ID. Secondary publication metadata only. - `prior_article_tripcodes` (array): Optional prior TF-SUB TripCodes in this River. - `publication` (string): Publication name. Defaults to DeltaSignal. - `publication_state` (string): Optional article state such as draft or published_or_linked. - `published_at` (string): Optional publication timestamp. Secondary publication metadata only. - `research_date` (string, required): Stable DeltaSignal research date in YYYY-MM-DD form. - `research_id` (string): Optional explicit DeltaSignal research ID. If omitted, issuer + research_slug + research_date + version form the canonical identity. - `research_slug` (string, required): Stable DeltaSignal research slug, for example hut-8-re-rating-deadline. - `research_version` (string): Optional research version. Defaults to 1. - `river_tripcodes` (array): Optional linked TF-RIVER TripCodes. - `subtitle` (string): Article subtitle before TripCode writeback. - `thesis_line` (string): Optional concise thesis line. Defaults to title. - `ticker` (string): Primary issuer ticker. Alias for issuer/primary_issuer. - `title` (string, required): Article title. Required for the article payload, but not hashed when research_slug is supplied. Output parameters: - `data` (object): Generated TF-SUB article/narrative research resolver object. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_list_article_tripcodes` (~337 tokens) DeltaSignal article TripCode discovery Use this read-only resolver to discover TF-SUB article nodes from a current article TripCode, an issuer TF-RIVER root, or an issuer lookup index. Parameters: pass current_tripcode, article_tripcode, tripcode, river, river_tripcodes, issuer, or ticker. object_type defaults to TF-SUB. include_unpublished defaults to false. limit defaults to 25. Behavior: read-only and River-root-first with no destructive side effects. It treats TF-RIVER as the canonical issuer thesis graph and by_issuer as a lookup surface only. Missing nodes are returned in missing_or_unresolved instead of inferred. Use this before article_thesis_map so subscribers do not need to manually paste old River TripCodes. Input parameters: - `article_tripcode` (string): Optional current TF-SUB article TripCode alias. - `current_tripcode` (string): Optional current TF-SUB article TripCode from the article subtitle. - `include_unpublished` (boolean): When true, include draft or unpublished article nodes. - `issuer` (string): Optional issuer ticker such as HUT. - `limit` (integer): Optional maximum article nodes to return. Defaults to 25. - `object_type` (string): Optional object type. Defaults to TF-SUB. - `river` (string): Optional issuer shorthand such as HUT or full TF-RIVER root TripCode. - `river_tripcodes` (array): Optional TF-RIVER root TripCodes. - `ticker` (string): Optional issuer ticker alias. - `tripcode` (string): Optional TF-SUB current article TripCode or TF-RIVER root TripCode. Output parameters: - `data` (object): Discovered TF-SUB article nodes from TF-RIVER continuity. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_resolve_article_tripcode` (~158 tokens) DeltaSignal article TripCode resolve Use this read-only resolver tool to load a TF-SUB article/narrative research object from the TrendForge Azure Blob resolver lake. Parameters: tripcode is required and must be a proprietary DeltaSignal article resolver key such as TF-SUB-DA79A58372. Behavior: idempotent and read-only with no destructive side effects; it does not mutate Azure Blob, Substack, filings, wallets, or account state. Use this when a subscriber gives Codex or Claude Code a TripCode from an article subtitle and asks for the machine-readable research object behind the article. Input parameters: - `tripcode` (string, required): Required TF-SUB article TripCode, for example TF-SUB-DA79A58372. Output parameters: - `data` (object): Resolved TF-SUB article/narrative research object from Azure Blob. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_resolve_tripcode_research_packet` (~424 tokens) DeltaSignal TripCode research packet Use this read-only composite resolver as the default subscriber-facing TripCode tool. Parameters: tripcode is required and must be a public TF-SUB article TripCode. issuer, river_tripcode, limit, payload_mode, and include flags are optional. Behavior: read-only and idempotent with no destructive side effects; it resolves the current article object, discovers prior TF-SUB River nodes, runs the article thesis map, and returns one research_packet with article memory, River continuity, evidence refs, boundaries, missing evidence, and suggested follow-ups. It does not call Grok, does not mutate Azure Blob or Substack, does not invent missing evidence, and does not treat TripCodes as SEC identifiers or investment advice. Input parameters: - `include_article_body` (boolean): When true with available content, include article body fields. Compact mode returns metadata and hashes only. - `include_filing_evidence` (boolean): When true, include filing evidence refs from the thesis map. The MVP keeps missing filing evidence explicit. - `include_prior_articles` (boolean): When true, include discovered prior River nodes. The MVP defaults to including compact River nodes. - `include_thesis_map` (boolean): When true, include the thesis-map sections. The MVP defaults to running the thesis map. - `include_unpublished` (boolean): When true, include draft or unpublished article nodes when the caller is authorized. - `issuer` (string): Optional issuer hint, such as HUT. - `limit` (integer): Optional maximum prior article nodes to return. Defaults to 25. - `payload_mode` (string): Optional payload mode: compact or full. Compact is the default. - `river_tripcode` (string): Optional TF-RIVER root hint. - `river_tripcodes` (array): Optional TF-RIVER root hints. - `ticker` (string): Optional issuer hint alias. - `tripcode` (string, required): Required TF-SUB article TripCode from a DeltaSignal article subtitle, for example TF-SUB-9DA70A7F98. Output parameters: - `data` (object): One TripCode-centered subscriber research packet across TF-SUB, TF-RIVER, TF-XBRL, and TF-DS continuity. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_resolve_river_tripcode` (~301 tokens) DeltaSignal River TripCode resolve Use this read-only resolver to load a TF-RIVER issuer thesis graph from the TrendForge Azure Blob resolver lake. Parameters: pass river_tripcode, tripcode, river, current article TripCode, or issuer. Issuer lookup uses by_issuer only to find the active River root. Behavior: idempotent and fail-closed with no destructive side effects. Missing River roots, article seeds, or issuer indexes are reported as missing_or_unresolved and are never inferred as evidence. Input parameters: - `article_tripcode` (string): Optional current TF-SUB article TripCode alias. - `current_tripcode` (string): Optional current TF-SUB article TripCode. - `include_unpublished` (boolean): When true, include draft or unpublished article nodes. - `issuer` (string): Optional issuer ticker. - `limit` (integer): Optional maximum result rows. Defaults to 25. - `river` (string): Optional TF-RIVER TripCode or issuer shorthand. - `river_tripcode` (string): Optional TF-RIVER TripCode. - `river_tripcodes` (array): Optional known TF-RIVER TripCodes. - `seed_tripcode` (string): Optional seed TF-SUB, TF-XBRL, TF-DS, or TF-RIVER TripCode. - `ticker` (string): Optional ticker alias for issuer. - `tripcode` (string): Optional TF-RIVER TripCode or TF-SUB seed TripCode. Output parameters: - `data` (object): Resolved TF-RIVER issuer thesis graph. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_reverse_search_river` (~470 tokens) DeltaSignal River reverse search Use this read-only thesis-lineage tool to start from a TripCode, issuer, claim, filing, or current object and reconstruct what the River already covered. Parameters: pass river_tripcode, issuer, seed_tripcode, query, claim_text, claim_hash, mode, include_xbrl, or include_ds. Output preserves the subscriber eight-section thesis-map shape: changed across River, confirmed signals, weakened assumptions, bridge risks, milestones, scenarios, invalidation, and next monitors. Behavior: deterministic graph synthesis with no destructive side effects, not an LLM or trading layer. Missing evidence remains missing. Input parameters: - `article_tripcode` (string): Optional current TF-SUB article TripCode alias. - `claim_hash` (string): Optional normalized claim hash for by_claim_hash lookup. - `claim_text` (string): Optional claim text to compare against the River. - `current_tripcode` (string): Optional current TF-SUB article TripCode. - `include_ds` (boolean): When true, include TF-DS computed signal refs from the River object. - `include_unpublished` (boolean): When true, include draft or unpublished article nodes. - `include_xbrl` (boolean): When true, include TF-XBRL evidence refs from the River object. - `issuer` (string): Optional issuer ticker. - `limit` (integer): Optional maximum result rows. Defaults to 25. - `mode` (string): Reverse-search mode: resolve, thesis_delta, claim_lineage, evidence_backtrace, invalidation_search, confirmation_search, monitoring_search, or scenario_rebuild. - `query` (string): Optional reverse-search question or claim. - `river` (string): Optional TF-RIVER TripCode or issuer shorthand. - `river_tripcode` (string): Optional TF-RIVER TripCode. - `river_tripcodes` (array): Optional known TF-RIVER TripCodes. - `seed_tripcode` (string): Optional seed TF-SUB, TF-XBRL, TF-DS, or TF-RIVER TripCode. - `ticker` (string): Optional ticker alias for issuer. - `time_window` (string): Optional time window label for caller-side filtering. - `tripcode` (string): Optional TF-RIVER TripCode or TF-SUB seed TripCode. Output parameters: - `data` (object): Reverse search across one issuer River. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_search_by_claim` (~301 tokens) DeltaSignal River claim search Use this read-only tool to search one River or claim index for matching thesis claims. Parameters: pass query, claim_text, claim_hash, river_tripcode, or issuer. Behavior: read-only with no destructive side effects; missing claim indexes are returned as unresolved, not fabricated. Input parameters: - `article_tripcode` (string): Optional current TF-SUB article TripCode alias. - `claim_hash` (string): Optional precomputed normalized claim hash. - `claim_text` (string): Claim text alias for query. - `current_tripcode` (string): Optional current TF-SUB article TripCode. - `include_unpublished` (boolean): When true, include draft or unpublished article nodes. - `issuer` (string): Optional issuer ticker. - `limit` (integer): Optional maximum result rows. Defaults to 25. - `query` (string): Claim text to search for when claim_hash is absent. - `river` (string): Optional TF-RIVER TripCode or issuer shorthand. - `river_tripcode` (string): Optional TF-RIVER TripCode. - `river_tripcodes` (array): Optional known TF-RIVER TripCodes. - `seed_tripcode` (string): Optional seed TF-SUB, TF-XBRL, TF-DS, or TF-RIVER TripCode. - `ticker` (string): Optional ticker alias for issuer. - `tripcode` (string): Optional TF-RIVER TripCode or TF-SUB seed TripCode. Output parameters: - `data` (object): Claim search result. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_search_by_issuer` (~133 tokens) DeltaSignal River issuer search Use this read-only tool to resolve the issuer index, active TF-RIVER root, and published TF-SUB article nodes for an issuer. Parameters: pass issuer or ticker, optional include_unpublished, and limit. Behavior: read-only with no destructive side effects; this is a discovery helper, not a thesis generator. Input parameters: - `include_unpublished` (boolean): When true, include draft or unpublished article nodes. - `issuer` (string): Issuer ticker such as HUT. - `limit` (integer): Maximum article nodes to return. - `ticker` (string): Ticker alias for issuer. Output parameters: - `data` (object): Issuer River discovery result. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_compare_claim_to_evidence` (~307 tokens) DeltaSignal claim evidence compare Use this read-only tool to compare a claim to River claim records and evidence refs. Parameters: pass claim_text or query plus river_tripcode or issuer. Behavior: read-only with no destructive side effects; returns confirmed, weakened, unresolved, or new_claim without inventing evidence. Input parameters: - `article_tripcode` (string): Optional current TF-SUB article TripCode alias. - `claim_hash` (string): Optional precomputed normalized claim hash. - `claim_text` (string): Claim text to compare against River claims and evidence refs. - `current_tripcode` (string): Optional current TF-SUB article TripCode. - `include_unpublished` (boolean): When true, include draft or unpublished article nodes. - `issuer` (string): Optional issuer ticker. - `limit` (integer): Optional maximum result rows. Defaults to 25. - `query` (string): Claim text to compare when claim_text is absent. - `river` (string): Optional TF-RIVER TripCode or issuer shorthand. - `river_tripcode` (string): Optional TF-RIVER TripCode. - `river_tripcodes` (array): Optional known TF-RIVER TripCodes. - `seed_tripcode` (string): Optional seed TF-SUB, TF-XBRL, TF-DS, or TF-RIVER TripCode. - `ticker` (string): Optional ticker alias for issuer. - `tripcode` (string): Optional TF-RIVER TripCode or TF-SUB seed TripCode. Output parameters: - `data` (object): Claim-to-evidence comparison. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_generate_filing_tripcode` (~427 tokens) DeltaSignal SEC/XBRL TripCode generate Use this read-only SEC/XBRL identity tool to generate a deterministic TF-XBRL resolver object for a DeltaSignal evidence object. Parameters: pass ticker=HUT with no filing overrides for the HUT 2026-Q1 10-Q seed object, or provide cik, issuer, filing_type, filing_period, and source document fields for explicit generation. Behavior: idempotent and local for the MVP; it has no destructive side effects, does not modify SEC filings, does not call wallets or x402 settlement, and never replaces SEC accession numbers, CIKs, form types, reporting periods, or XBRL concept identities. Use the returned TripCode as a subscriber-facing join key from article nodes, research rivers, SEC evidence, and DeltaSignal outputs. Input parameters: - `accession_number` (string): SEC accession number when the object is filing-specific. - `cik` (string): SEC CIK, with or without CIK prefix. - `company` (string): SEC registrant company name. - `companyfacts_snapshot` (string): CompanyFacts snapshot reference when available. - `deltasignal_method_version` (string): Optional method version override for deterministic regeneration tests. - `filing_date` (string): SEC filing date. - `filing_period` (string): Normalized filing period such as 2026-Q1. - `filing_type` (string): SEC form type such as 10-Q or 8-K. - `issuer` (string): Issuer ticker or short symbol. Prefer ticker for public companies. - `latest_article_node` (string): Optional latest TF-SUB article node linked to this filing evidence object. - `primary_filing` (string): Primary SEC filing document reference. - `report_date` (string): SEC report date or period end. - `research_river` (array): Optional prior TF-SUB article TripCodes linked to this filing object. - `ticker` (string): Issuer ticker. HUT is the seeded MVP ticker. - `xbrl_instance` (string): XBRL instance document reference when available. Output parameters: - `data` (object): Generated SEC/XBRL TripCode resolver object. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_resolve_filing_tripcode` (~176 tokens) DeltaSignal SEC/XBRL TripCode resolve Use this read-only resolver tool to load a TF-XBRL TripCode as a SEC/XBRL evidence object. Parameters: tripcode is required and must be a proprietary DeltaSignal SEC/XBRL resolver key such as TF-XBRL-HUT-2026Q1-... Behavior: idempotent and local for the MVP; it has no destructive side effects, does not mutate SEC filings, does not call wallets or x402 settlement, and returns HUT seed objects when the TripCode is known. Use this before article comparison whenever a Substack article names a TF-XBRL evidence object. Input parameters: - `tripcode` (string, required): Required SEC/XBRL TripCode, for example TF-XBRL-HUT-2026Q1-A8F31C2D9B. Output parameters: - `data` (object): Resolved SEC/XBRL TripCode object. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_compare_article_to_filing_evidence` (~496 tokens) DeltaSignal article-to-filing evidence compare Use this read-only comparison tool to compare a TF-SUB article node against resolved TF-XBRL filing evidence objects. Parameters: article_tripcode is optional, filing_tripcodes may list one or more TF-XBRL objects, and ticker=HUT with no filing_tripcodes loads the default HUT filing pack. Behavior: idempotent and local for the MVP; it has no destructive side effects, does not mint official SEC identity, does not infer filing evidence from prose, and does not call wallets or x402 settlement. The HUT MVP returns a structured article-readiness packet with filing changes, confirmed thesis points, weakened assumptions, stress points, XBRL drivers, invalidation checks, and next-filing monitors. Input parameters: - `accession_number` (string): SEC accession number when the object is filing-specific. - `article_tripcode` (string): Optional TF-SUB article node TripCode to compare against filing evidence. - `cik` (string): SEC CIK, with or without CIK prefix. - `company` (string): SEC registrant company name. - `companyfacts_snapshot` (string): CompanyFacts snapshot reference when available. - `comparison_focus` (string): Optional comparison focus, such as HUT article readiness or thesis verification. - `deltasignal_method_version` (string): Optional method version override for deterministic regeneration tests. - `filing_date` (string): SEC filing date. - `filing_period` (string): Normalized filing period such as 2026-Q1. - `filing_tripcodes` (array): Optional TF-XBRL filing evidence TripCodes. If omitted for HUT, the default HUT filing pack is used. - `filing_type` (string): SEC form type such as 10-Q or 8-K. - `issuer` (string): Issuer ticker or short symbol. Prefer ticker for public companies. - `latest_article_node` (string): Optional latest TF-SUB article node linked to this filing evidence object. - `primary_filing` (string): Primary SEC filing document reference. - `report_date` (string): SEC report date or period end. - `research_river` (array): Optional prior TF-SUB article TripCodes linked to this filing object. - `ticker` (string): Issuer ticker. HUT is the seeded MVP ticker. - `xbrl_instance` (string): XBRL instance document reference when available. Output parameters: - `data` (object): Article-to-filing thesis verification packet backed by TF-XBRL resolver objects. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `deltasignal_article_thesis_map` (~637 tokens) DeltaSignal article thesis map Use this read-only synthesis tool when a subscriber gives Codex or Claude Code a DeltaSignal article TripCode and asks for the thesis map behind the article. Parameters: pass article_tripcode or tripcode, optional prior_article_tripcodes, linked_xbrl_tripcodes, filing_tripcodes, and ticker. For HUT, the MVP can use the seeded HUT filing pack when no filing_tripcodes are supplied. Behavior: idempotent and evidence-scoped with no destructive side effects. It resolves the TF-SUB article object when Azure Blob is configured, compares linked TF-XBRL filing evidence, marks missing live ATLAS evidence explicitly, and returns the eight required thesis-map sections. It does not call Grok, does not invent evidence, does not mutate Substack or Azure Blob, and does not treat TripCodes as official SEC identities. Input parameters: - `accession_number` (string): SEC accession number when the object is filing-specific. - `article_tripcode` (string): Optional TF-SUB article node TripCode from the article subtitle. - `cik` (string): SEC CIK, with or without CIK prefix. - `company` (string): SEC registrant company name. - `companyfacts_snapshot` (string): CompanyFacts snapshot reference when available. - `comparison_focus` (string): Optional thesis-map focus. - `deltasignal_method_version` (string): Optional method version override for deterministic regeneration tests. - `filing_date` (string): SEC filing date. - `filing_period` (string): Normalized filing period such as 2026-Q1. - `filing_tripcodes` (array): Optional TF-XBRL filing evidence TripCodes. HUT with no filing_tripcodes loads the seeded HUT filing pack. - `filing_type` (string): SEC form type such as 10-Q or 8-K. - `issuer` (string): Issuer ticker or short symbol. Prefer ticker for public companies. - `latest_article_node` (string): Optional latest TF-SUB article node linked to this filing evidence object. - `linked_ds_tripcodes` (array): Optional linked TF-DS signal TripCodes from the current article object. - `linked_xbrl_tripcodes` (array): Optional linked TF-XBRL evidence TripCodes from the current article object. - `primary_filing` (string): Primary SEC filing document reference. - `prior_article_tripcodes` (array): Optional prior TF-SUB TripCodes in the issuer River. - `report_date` (string): SEC report date or period end. - `research_river` (array): Optional prior TF-SUB article TripCodes linked to this filing object. - `river_tripcodes` (array): Optional linked TF-RIVER TripCodes. - `thesis_line` (string): Optional current article thesis line. - `ticker` (string): Issuer ticker. HUT is the seeded MVP ticker. - `title` (string): Optional current article title. - `tripcode` (string): Optional TF-SUB article TripCode alias. Prefer article_tripcode. - `xbrl_instance` (string): XBRL instance document reference when available. Output parameters: - `data` (object): Article-centered thesis map across TF-SUB, TF-XBRL, TF-DS, and TF-RIVER continuity. - `mcp_summary` (string): Concise high-signal summary of the tool response. Maximum 140 characters. - `provenance` (object): Traceability information for the MCP tool response. - `suggested_follow_ups` (array): Concrete next MCP calls an agent can run to continue the workflow. - `usage_metadata` (object): Performance and estimated cost metadata for this MCP tool call. ### `strategix_diagram_validate` (~98 tokens) StrategiX diagram contract validation Validate a canonical StrategiX visual-spec contract before rendering. Infrastructure-first: validates nodes, edges, owners, viewport policy, accessibility, source references, and receipt-binding metadata. Does not draw or mutate a canvas. Input parameters: - `contract` (object, required): Minimum viable StrategiX visual-spec contract. This is the source of truth; D2, Mermaid, Graphviz DOT, SVG, and draw.io XML are input or intermediate formats only. ### `strategix_diagram_render` (~149 tokens) StrategiX deterministic diagram render Render a validated StrategiX visual-spec contract into deterministic Go-native SVG with fit report, hashes, compact search metadata, and human-readable receipt fields. This MVP does not use external D2/Graphviz yet. Input parameters: - `contract` (object, required): Minimum viable StrategiX visual-spec contract. This is the source of truth; D2, Mermaid, Graphviz DOT, SVG, and draw.io XML are input or intermediate formats only. - `payment_reference` (string): Optional x402 payment reference supplied by the caller or payment middleware. - `project_id` (string): Optional project namespace for compact search metadata. - `source_digest` (array): Optional source digest ids or short source notes. ### `strategix_visual_spec_package` (~163 tokens) StrategiX visual-spec HTML package Package a canonical contract and rendered SVG into self-contained HTML with embedded JSON contract, source digest, fit report, compact metadata, and a human-readable x402 receipt block. Input parameters: - `contract` (object, required): Minimum viable StrategiX visual-spec contract. This is the source of truth; D2, Mermaid, Graphviz DOT, SVG, and draw.io XML are input or intermediate formats only. - `payment_reference` (string): Optional x402 payment reference supplied by the caller or payment middleware. - `project_id` (string): Optional project namespace for compact search metadata. - `rendered_svg` (string): Optional pre-rendered SVG. If omitted, the service renders the contract first. - `source_digest` (array): Optional source digest ids or short source notes. ### `strategix_visual_spec_search` (~102 tokens) StrategiX visual-spec compact search Search compact visual-spec metadata by topic, source digest, embedded contract hash, receipt hash, project, diagram family, and tags. Returns compact metadata only; full HTML/SVG/XML is a drilldown concern. Input parameters: - `artifacts` (array): Optional caller-supplied compact metadata records to search. - `limit` (integer): Maximum results. Defaults to 10. - `query` (string, required): Search query across compact metadata and built-in MVP fixture records. ### `atlas7_model_catalog` (~29 tokens) ATLAS-7 model catalog Subscription-gated catalog of governed semantic models, supported intents, evidence requirements, and freshness policies. ### `atlas7_field_catalog` (~43 tokens) ATLAS-7 field catalog Subscription-gated field, metric, filter, sort, and evidence contract for one governed semantic model. Input parameters: - `model_key` (string, required): Required governed semantic model key. ### `atlas7_issuer_identity` (~66 tokens) ATLAS-7 issuer identity Subscription-gated canonical issuer identity lookup by ticker or CIK. Input parameters: - `cik` (string): Issuer CIK when ticker is not supplied. - `limit` (integer): Maximum rows to return. - `ticker` (string): Issuer ticker, for example IREN. ### `atlas7_metadata_health` (~38 tokens) ATLAS-7 metadata health Subscription-gated semantic metadata, source freshness, row-count, and evidence-contract health surface. Input parameters: - `limit` (integer): Maximum health rows. ### `atlas7_compile_query` (~105 tokens) ATLAS-7 compile query Subscription-gated validation of a governed semantic query. Returns the public plan and SQL fingerprint without exposing raw SQL. Input parameters: - `fields` (array): Optional allowlisted fields. Evidence fields are appended automatically. - `filters` (array): Optional validated filters. - `intent` (string): Allowlisted semantic intent. - `limit` (integer): Maximum rows to return. - `model_key` (string): Allowlisted semantic model key. - `sort` (array): Optional validated sort fields. ### `atlas7_readiness` (~46 tokens) ATLAS-7 semantic readiness Subscription-gated semantic readiness and entitlement status. Existing DeltaSignal readiness remains available through x402; this semantic surface requires Marketplace subscription. Input parameters: - `limit` (integer): Maximum readiness rows. ### `atlas7_signal_board` (~58 tokens) ATLAS-7 signal board Subscription-gated latest issuer signal board. Input parameters: - `limit` (integer): Maximum rows to return. - `signal_filter` (string): Optional alpha signal text filter. - `stress_field` (string): Optional stress field override for stress-ranked tools. ### `atlas7_issuer_signal` (~64 tokens) ATLAS-7 issuer signal Subscription-gated issuer signal by ticker or CIK. Input parameters: - `cik` (string): Issuer CIK when ticker is not supplied. - `limit` (integer): Maximum rows to return. - `ticker` (string): Issuer ticker, for example IREN. ### `atlas7_pressure_board` (~57 tokens) ATLAS-7 pressure board Subscription-gated semantic pressure board. Input parameters: - `limit` (integer): Maximum rows to return. - `signal_filter` (string): Optional alpha signal text filter. - `stress_field` (string): Optional stress field override for stress-ranked tools. ### `atlas7_top_stress` (~60 tokens) ATLAS-7 top stress Subscription-gated semantic top-stress ranking. Input parameters: - `limit` (integer): Maximum rows to return. - `signal_filter` (string): Optional alpha signal text filter. - `stress_field` (string): Optional stress field override for stress-ranked tools. ### `atlas7_alpha_candidates` (~59 tokens) ATLAS-7 alpha candidates Subscription-gated semantic alpha-candidate screen. Input parameters: - `limit` (integer): Maximum rows to return. - `signal_filter` (string): Optional alpha signal text filter. - `stress_field` (string): Optional stress field override for stress-ranked tools. ### `atlas7_quick_ticker_check` (~63 tokens) ATLAS-7 quick ticker check Subscription-gated semantic ticker triage. Input parameters: - `cik` (string): Issuer CIK when ticker is not supplied. - `limit` (integer): Maximum rows to return. - `ticker` (string): Issuer ticker, for example IREN. ### `atlas7_peer_comparison` (~62 tokens) ATLAS-7 peer comparison Subscription-gated peer ranking and relative pressure. Input parameters: - `cik` (string): Issuer CIK when ticker is not supplied. - `limit` (integer): Maximum rows to return. - `ticker` (string): Issuer ticker, for example IREN. ### `atlas7_covenant_stress` (~65 tokens) ATLAS-7 covenant stress Subscription-gated covenant, debt, and liquidity stress view. Input parameters: - `limit` (integer): Maximum rows to return. - `signal_filter` (string): Optional alpha signal text filter. - `stress_field` (string): Optional stress field override for stress-ranked tools. ### `atlas7_company_fundamentals` (~63 tokens) ATLAS-7 company fundamentals Subscription-gated filing-backed fundamentals surface. Input parameters: - `cik` (string): Issuer CIK when ticker is not supplied. - `limit` (integer): Maximum rows to return. - `ticker` (string): Issuer ticker, for example IREN. ### `atlas7_recent_history` (~62 tokens) ATLAS-7 recent history Subscription-gated recent point-in-time issuer trajectory. Input parameters: - `cik` (string): Issuer CIK when ticker is not supplied. - `limit` (integer): Maximum rows to return. - `ticker` (string): Issuer ticker, for example IREN. ### `atlas7_market_context` (~38 tokens) ATLAS-7 market context Subscription-gated market and instrument overlay context. Input parameters: - `instrument` (string): Optional market instrument. - `limit` (integer): Maximum rows. ### `atlas7_explain_signal` (~101 tokens) ATLAS-7 explain signal Subscription-gated explanation of fields, evidence requirements, and SQL fingerprint without raw SQL. Input parameters: - `fields` (array): Optional allowlisted fields. Evidence fields are appended automatically. - `filters` (array): Optional validated filters. - `intent` (string): Allowlisted semantic intent. - `limit` (integer): Maximum rows to return. - `model_key` (string): Allowlisted semantic model key. - `sort` (array): Optional validated sort fields. ### `atlas7_company_report_inputs` (~62 tokens) ATLAS-7 company report inputs Subscription-gated structured Company Report input bundle. Input parameters: - `cik` (string): Issuer CIK when ticker is not supplied. - `limit` (integer): Maximum rows to return. - `ticker` (string): Issuer ticker, for example IREN. ### `atlas7_morning_brief_inputs` (~62 tokens) ATLAS-7 morning brief inputs Subscription-gated structured Morning Brief input bundle. Input parameters: - `limit` (integer): Maximum rows to return. - `signal_filter` (string): Optional alpha signal text filter. - `stress_field` (string): Optional stress field override for stress-ranked tools. ### `atlas7_theme_discovery` (~60 tokens) ATLAS-7 theme discovery Subscription-gated theme, concept, and taxonomy discovery. Input parameters: - `cik` (string): Optional CIK. - `limit` (integer): Maximum rows. - `theme` (string): Optional theme filter. - `ticker` (string): Optional ticker. ### `atlas7_evidence_lineage` (~73 tokens) ATLAS-7 evidence lineage Subscription-gated evidence and provenance lineage drilldown. Input parameters: - `accession` (string): Optional SEC accession. - `cik` (string): Optional CIK. - `fact_name` (string): Optional fact or concept name. - `limit` (integer): Maximum rows. - `ticker` (string): Optional ticker. ### `atlas7_lineage_audit` (~70 tokens) ATLAS-7 lineage audit Subscription-gated calculation lineage audit. Input parameters: - `accession` (string): Optional SEC accession. - `cik` (string): Optional CIK. - `fact_name` (string): Optional fact or concept name. - `limit` (integer): Maximum rows. - `ticker` (string): Optional ticker. ### `atlas7_semantic_query` (~104 tokens) ATLAS-7 semantic query Subscription-gated governed semantic query. Returns ATLAS evidence envelopes only; raw SQL is never returned. Input parameters: - `fields` (array): Optional allowlisted fields. Evidence fields are appended automatically. - `filters` (array): Optional validated filters. - `intent` (string): Allowlisted semantic intent. - `limit` (integer): Maximum rows to return. - `model_key` (string): Allowlisted semantic model key. - `sort` (array): Optional validated sort fields. ### `atlas7_archive_search` (~60 tokens) ATLAS-7 archive search Subscription-gated archive and history search. Input parameters: - `cik` (string): Issuer CIK when ticker is not supplied. - `limit` (integer): Maximum rows to return. - `ticker` (string): Issuer ticker, for example IREN. ### `atlas7_portfolio_watchlist` (~76 tokens) ATLAS-7 portfolio watchlist Subscription-gated saved watchlist analysis. MVP accepts ticker or CIK filters until watchlist persistence is enabled. Input parameters: - `cik` (string): Issuer CIK when ticker is not supplied. - `limit` (integer): Maximum rows to return. - `ticker` (string): Issuer ticker, for example IREN. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/aitrailblazer-deltasignal-atlas-7/api#diagnostics ## Score history - 2026-08-03: 66 - 2026-08-02: 65 - 2026-08-01: 65 - 2026-07-31: 64 - 2026-07-30: 61 - 2026-07-29: 61 - 2026-07-28: 60 - 2026-07-27: 59 - 2026-07-26: 59 ## Links - Remote endpoint: https://api.aitrailblazer.net/mcp - Repository: https://github.com/aitrailblazer/deltasignal-atlas-codex-plugin - Website: https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin - Changelog RSS feed: https://verifymcp.io/servers/aitrailblazer-deltasignal-atlas-7/api/changelog.xml - Changelog JSON feed: https://verifymcp.io/servers/aitrailblazer-deltasignal-atlas-7/api/changelog.json - HTML version of this page: https://verifymcp.io/servers/aitrailblazer-deltasignal-atlas-7/api