DeltaSignal ATLAS-7
REMOTE · API.AITRAILBLAZER.NET · SCANNED AUG 3
SEC/XBRL issuer intelligence for crypto public companies via MCP, OpenAPI, x402, and MPP.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability51
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.aitrailblazer.net
claude mcp add --transport http aitrailblazer-deltasignal-atlas-7 https://api.aitrailblazer.net/mcp
[mcp_servers.aitrailblazer-deltasignal-atlas-7] url = "https://api.aitrailblazer.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aitrailblazer-deltasignal-atlas-7": {
"type": "remote",
"url": "https://api.aitrailblazer.net/mcp",
"enabled": true
}
}
} openclaw mcp add aitrailblazer-deltasignal-atlas-7 --url https://api.aitrailblazer.net/mcp --transport streamable-http
mcp_servers:
aitrailblazer-deltasignal-atlas-7:
url: "https://api.aitrailblazer.net/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://api.aitrailblazer.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.aitrailblazer.net | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 24 Apr 2026 | 24 Oct 2026 | RSA 2048 | SHA256-RSA | e672c64c21c75f3646b8042d9ab0c69 |
| SANs: api.aitrailblazer.net | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
DNSSEC insecure
Validation of api.aitrailblazer.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| aitrailblazer.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.aitrailblazer.net/mcp | Verified | 200 | |
| http (plaintext) | http://api.aitrailblazer.net/mcp | HTTPS enforced | 301 | https://api.aitrailblazer.net/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
deltasignal_covenant_stress DeltaSignal covenant stress ~460
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Covenant stress detail when ticker is supplied, or list-mode response with data and meta when ticker is omitted. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_covenant_stress_natural DeltaSignal covenant stress Natural Language brief ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | — | Optional YYYY-MM-DD source/evidence period selector. |
| style | string | — | Rendering style. Style changes tone and density only, not facts. |
| ticker | string | yes | Required crypto public company ticker. Examples: RIOT, MARA, COIN, MSTR. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Natural Language Covenant Stress response. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_daily_change_evidence DeltaSignal daily change evidence ~240
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Issuer-specific paginated daily-change evidence. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_daily_changes DeltaSignal daily changes ~139
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Latest promoted DeltaSignal daily change snapshot for monitoring workflows, with separate compute and CompanyFacts artifact freshness fields. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_generate_article_tripcode DeltaSignal article TripCode generate ~573
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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 | yes | Article title. Required for the article payload, but not hashed when research_slug is supplied. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Generated TF-SUB article/narrative research resolver object. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_generate_filing_tripcode DeltaSignal SEC/XBRL TripCode generate ~427
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Generated SEC/XBRL TripCode resolver object. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_help DeltaSignal help ~294
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Free DeltaSignal MCP discovery and orientation response. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_issuer_deep_report DeltaSignal issuer deep report ~422
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Required crypto public company ticker. Examples: GME, MSTR, RIOT, MARA, COIN. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Server-enforced DeltaSignal issuer deep report evidence bundle with report-readiness contract and missing-evidence matrix. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_list_article_tripcodes DeltaSignal article TripCode discovery ~337
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Discovered TF-SUB article nodes from TF-RIVER continuity. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_morning_brief DeltaSignal morning brief ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| output_mode | string | — | Optional response mode. Only compact is accepted in Phase 1. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Server-enforced DeltaSignal morning brief composite response. The data object preserves successful subtool payloads plus a deterministic internal call ledger. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_morning_brief_natural DeltaSignal Morning Brief Natural Language brief ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Natural Language Morning Brief response rendered from backend-composed compact evidence. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_peer_ranking DeltaSignal peer ranking ~233
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.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | — | Optional YYYY-MM-DD filing period. Omit for the latest peer ranking. |
| ticker | string | yes | Required crypto public company ticker. Examples: COIN, MSTR, MARA, RIOT, HUT, CLSK. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Peer ranking and percentile context for one crypto public company. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_pressure_board DeltaSignal pressure board ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| output_mode | string | — | Optional response mode. Only compact is accepted. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Server-enforced DeltaSignal pressure board composite response. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_public_daily_brief DeltaSignal public daily brief ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| output_mode | string | — | Optional response mode. Only compact is accepted in Phase 1. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | 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 | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_quick_ticker_check DeltaSignal quick ticker check ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| output_mode | string | — | Optional response mode. Only compact is accepted. |
| ticker | string | yes | Required crypto public company ticker. The server trims whitespace and normalizes to uppercase before all internal calls. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Server-enforced DeltaSignal quick ticker check composite response. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_readiness DeltaSignal readiness ~169
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Readiness and data-freshness diagnostics for the live DeltaSignal ATLAS-7 data plane. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_resolve_article_tripcode DeltaSignal article TripCode resolve ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tripcode | string | yes | Required TF-SUB article TripCode, for example TF-SUB-DA79A58372. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Resolved TF-SUB article/narrative research object from Azure Blob. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_resolve_filing_tripcode DeltaSignal SEC/XBRL TripCode resolve ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tripcode | string | yes | Required SEC/XBRL TripCode, for example TF-XBRL-HUT-2026Q1-A8F31C2D9B. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Resolved SEC/XBRL TripCode object. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_resolve_river_tripcode DeltaSignal River TripCode resolve ~301
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Resolved TF-RIVER issuer thesis graph. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_resolve_tripcode_research_packet DeltaSignal TripCode research packet ~424
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Required TF-SUB article TripCode from a DeltaSignal article subtitle, for example TF-SUB-9DA70A7F98. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | One TripCode-centered subscriber research packet across TF-SUB, TF-RIVER, TF-XBRL, and TF-DS continuity. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_reverse_search_river DeltaSignal River reverse search ~470
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Reverse search across one issuer River. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_risk_distribution DeltaSignal risk distribution ~147
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Risk-tier distribution for the active DeltaSignal issuer universe. Tier names are object keys such as HIGH, MODERATE, LOW, and UNCLASSIFIED. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_search_by_claim DeltaSignal River claim search ~301
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Claim search result. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_search_by_issuer DeltaSignal River issuer search ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Issuer River discovery result. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_spectra_field_map DeltaSignal SPECTRA field map ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Required crypto public company ticker symbol. Examples: RIOT, MARA, COIN, MSTR, HUT, CLSK. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | SPECTRA historical field-map contract for one issuer. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_synthetic_etf_audit DeltaSignal Synthetic ETF audit payload ~419
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Audit-grade DeltaSignal Synthetic ETF payload. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_synthetic_etf_pressure_state DeltaSignal Synthetic ETF pressure state ~294
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Composite DeltaSignal Synthetic ETF pressure-state envelope. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_thesis_create DeltaSignal accountless thesis create ~302
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Required user-authored thesis text. |
| ticker | string | yes | Required issuer ticker. Examples: MSTR, RIOT, MARA, COIN. |
| watch_conditions | array | — | Optional structured watch conditions extracted from the thesis. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | 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 | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_thesis_readiness DeltaSignal thesis readiness ~344
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Required user-authored thesis text. It should state what must remain true, what weakens it, and what falsifies it. |
| ticker | string | yes | Required issuer ticker. Examples: MSTR, RIOT, MARA, COIN. |
| watch_conditions | array | — | Optional structured watch conditions extracted from the thesis. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Deterministic thesis readiness score. This response uses no ATLAS evidence and only decides whether the thesis is suitable for monitoring. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_top_stressed DeltaSignal top stressed issuers ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Ranked stressed issuer screen. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
deltasignal_top_stressed_natural DeltaSignal top stressed Natural Language brief ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Natural Language Top Stressed response. |
| mcp_summary | string | yes | Concise high-signal summary of the tool response. Maximum 140 characters. |
| provenance | object | yes | Traceability information for the MCP tool response. |
| suggested_follow_ups | array | yes | 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. |
No examples provided.
strategix_diagram_render StrategiX deterministic diagram render ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | object | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
strategix_diagram_validate StrategiX diagram contract validation ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | object | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
strategix_visual_spec_package StrategiX visual-spec HTML package ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | object | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
strategix_visual_spec_search StrategiX visual-spec compact search ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| artifacts | array | — | Optional caller-supplied compact metadata records to search. |
| limit | integer | — | Maximum results. Defaults to 10. |
| query | string | yes | Search query across compact metadata and built-in MVP fixture records. |
Structured output declared, but exposes no named fields.
No examples provided.