DeltaSignal ATLAS-7
REMOTE · API.AITRAILBLAZER.NET
SEC/XBRL issuer intelligence for crypto public companies via MCP, OpenAPI, x402, and MPP.
Available components
Last scanned (18 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Finance and Payments
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 → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 6404 tokens (~278/item across 23 items; 23 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 Management93
- Stability observed for 28 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 7 Nov 26 +63
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.93 ▲ functional
- 6 Nov 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
- 30 Oct 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 Oct 26 0
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “atlas7_alpha_candidates” was removed ▼ security
- Tool “atlas7_archive_search” was removed ▼ security
- Tool “atlas7_company_fundamentals” was removed ▼ security
- Tool “atlas7_company_report_inputs” was removed ▼ security
- Tool “atlas7_compile_query” was removed ▼ security
- Tool “atlas7_covenant_stress” was removed ▼ security
- Tool “atlas7_evidence_lineage” was removed ▼ security
- Tool “atlas7_explain_signal” was removed ▼ security
- Tool “atlas7_field_catalog” was removed ▼ security
- Tool “atlas7_issuer_identity” was removed ▼ security
- Tool “atlas7_issuer_signal” was removed ▼ security
- Tool “atlas7_lineage_audit” was removed ▼ security
- Tool “atlas7_market_context” was removed ▼ security
- Tool “atlas7_metadata_health” was removed ▼ security
- Tool “atlas7_model_catalog” was removed ▼ security
- Tool “atlas7_morning_brief_inputs” was removed ▼ security
- Tool “atlas7_peer_comparison” was removed ▼ security
- Tool “atlas7_portfolio_watchlist” was removed ▼ security
- Tool “atlas7_pressure_board” was removed ▼ security
- Tool “atlas7_quick_ticker_check” was removed ▼ security
- Tool “atlas7_readiness” was removed ▼ security
- Tool “atlas7_recent_history” was removed ▼ security
- Tool “atlas7_semantic_query” was removed ▼ security
- Tool “atlas7_signal_board” was removed ▼ security
- Tool “atlas7_theme_discovery” was removed ▼ security
- Tool “atlas7_top_stress” was removed ▼ security
- Tool “deltasignal_alpha_opportunities” was removed ▼ security
- Tool “deltasignal_alpha_opportunities_audit” was removed ▼ security
- Tool “deltasignal_alpha_signals” was removed ▼ security
- Tool “deltasignal_article_thesis_map” was removed ▼ security
- Tool “deltasignal_atlas7_audit_status” was removed ▼ security
- Tool “deltasignal_company_fundamentals” was removed ▼ security
- Tool “deltasignal_compare_article_to_filing_evidence” was removed ▼ security
- Tool “deltasignal_compare_claim_to_evidence” was removed ▼ security
- Tool “deltasignal_covenant_stress” was removed ▼ security
- Tool “deltasignal_daily_change_evidence” was removed ▼ security
- Tool “deltasignal_daily_changes” was removed ▼ security
- Tool “deltasignal_generate_article_tripcode” was removed ▼ security
- Tool “deltasignal_generate_filing_tripcode” was removed ▼ security
- Tool “deltasignal_list_article_tripcodes” was removed ▼ security
- Tool “deltasignal_peer_ranking” was removed ▼ security
- Tool “deltasignal_readiness” was removed ▼ security
- Tool “deltasignal_resolve_article_tripcode” was removed ▼ security
- Tool “deltasignal_resolve_filing_tripcode” was removed ▼ security
- Tool “deltasignal_resolve_river_tripcode” was removed ▼ security
- Tool “deltasignal_resolve_tripcode_research_packet” was removed ▼ security
- Tool “deltasignal_reverse_search_river” was removed ▼ security
- Tool “deltasignal_risk_distribution” was removed ▼ security
- Tool “deltasignal_search_by_claim” was removed ▼ security
- Tool “deltasignal_search_by_issuer” was removed ▼ security
- Tool “deltasignal_spectra_field_map” was removed ▼ security
- Tool “deltasignal_thesis_create” was removed ▼ security
- Tool “deltasignal_thesis_readiness” was removed ▼ security
- Tool “deltasignal_top_stressed” was removed ▼ security
- Tool “strategix_diagram_render” was removed ▼ security
- Tool “strategix_diagram_validate” was removed ▼ security
- Tool “strategix_visual_spec_package” was removed ▼ security
- Tool “strategix_visual_spec_search” was removed ▼ security
- Schema quality: 212 → 278 ▼ functional
- Schema quality: good → excellent functional
- 28 Sept 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
- 25 Sept 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
- 1 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- MCP protocol: fail → pass ▲ functional
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- MCP protocol version: 2025-03-26 → 2026-07-28 functional
- 26 Aug 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
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 7 Nov 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=WR3,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | RSA 2048 | SHA256-RSA | fbe3460afbbe9f4d12ad70b4c70ec2a4 |
| SANs: api.aitrailblazer.net | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.aitrailblazer.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| aitrailblazer.net. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 | 302 | 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
deltasignal_alpha_sweep DeltaSignal alpha sweep ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| output_mode | string | – | Optional response mode. Only compact is accepted. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Server-enforced DeltaSignal alpha sweep 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_atlas_history DeltaSignal ATLAS history ~300
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Required crypto public company ticker. Examples: MSTR, COIN, MARA, RIOT. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Historical ATLAS-7 issuer time series keyed by source_date. |
| 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_atlas7_calculation_history DeltaSignal ATLAS-7 complete calculation history ~351
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Complete ATLAS-7 calculation-history rows keyed by source_date and 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_atlas7_companyfacts_history DeltaSignal ATLAS-7 CompanyFacts history ~360
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Compact materialized SEC CompanyFacts rows keyed by source_date and 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_atlas7_four_level_applicability DeltaSignal ATLAS-7 four-level applicability ~256
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | ATLAS-7 four-level applicability/readiness rows for issuer, market, basket, and capability-gated depth/reference 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_atlas7_point_in_time_history DeltaSignal ATLAS-7 point-in-time factor history ~342
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | CompanyFacts-derived point-in-time ATLAS-7 factor rows keyed by as_of_date and 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_coinbase_perp_calculation_history DeltaSignal Coinbase perp calculation history ~288
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Coinbase INTX perp market-factor history assembled from persisted venue-pure recorder 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_coinbase_perp_constituents DeltaSignal Coinbase perp constituents ~281
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Coinbase thematic/index perp constituent registries read from persisted additive overlay rows. |
| 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_coinbase_perp_factors DeltaSignal Coinbase perp factor history ~278
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Coinbase INTX perp market-factor history assembled from persisted venue-pure recorder 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_coinbase_perp_market_spectra DeltaSignal Coinbase perp market SPECTRA ~253
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Coinbase INTX perp market SPECTRA field map derived from persisted factor history. |
| 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_coinbase_perp_rankings DeltaSignal Coinbase perp rankings ~268
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Coinbase INTX perp rankings built from the latest persisted factor row per product within scope. |
| 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_company_report DeltaSignal company report ~349
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Required crypto public company ticker. The server trims whitespace and normalizes to uppercase before all internal calls. Examples: RIOT, MARA, COIN, MSTR. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Server-enforced DeltaSignal company report 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_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_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_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_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_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_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.
How do I install the DeltaSignal ATLAS-7 MCP server?
DeltaSignal ATLAS-7 is a hosted endpoint at https://api.aitrailblazer.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.aitrailblazer.net
claude mcp add --transport http aitrailblazer-deltasignal-atlas-7 'https://api.aitrailblazer.net/mcp'
What is the DeltaSignal ATLAS-7 MCP server?
DeltaSignal ATLAS-7 is an MCP server listed in the public MCP registry as io.github.aitrailblazer/deltasignal-atlas-7. SEC/XBRL issuer intelligence for crypto public companies via MCP, OpenAPI, x402, and MPP. This page covers its hosted endpoint (https://api.aitrailblazer.net/mcp).
Is the DeltaSignal ATLAS-7 MCP server safe to use?
DeltaSignal ATLAS-7 scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DeltaSignal ATLAS-7 MCP server expose?
DeltaSignal ATLAS-7 exposes 23 tools: deltasignal_help, deltasignal_morning_brief, deltasignal_public_daily_brief, deltasignal_company_report, deltasignal_issuer_deep_report, and 18 more. Their descriptions and schemas cost roughly 6,371 tokens of context every time the server is loaded.
Does the DeltaSignal ATLAS-7 MCP server require authentication?
Yes. DeltaSignal ATLAS-7 asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the DeltaSignal ATLAS-7 MCP server still maintained?
DeltaSignal ATLAS-7 is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the DeltaSignal ATLAS-7 MCP server?
VerifyMCP ran 13 checks on DeltaSignal ATLAS-7, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.