# DeltaSignal MCP Frontend

> DeltaSignal MCP Frontend is a paid API for AI agents from api.aitrailblazer.net, paid per call via x402, $0.04/call, status unknown (last checked 2026-09-16).

MCP protocol gateway for DeltaSignal's agentic financial signal and analytics tools, serving phase 1 alpha, resilience, treasury-strength, and regime-fit signals via JSON-RPC 2.0.

## Facts

- Endpoint: POST https://api.aitrailblazer.net/mcp
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/deltasignal-mcp-frontend-2c0b1bea
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QX96w59oo2Aiy4V4CPfAH

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability deltasignal-mcp-frontend-2c0b1bea -d '<json body>'
```

Example prompt: Run the DeltaSignal tools/list call to see what analytics tools are available, then call tools/call to get the phase 1 alpha and regime-fit signals for issuer AAPL.

## When to prefer this

Use this endpoint when an agent needs structured financial signals — alpha, resilience, treasury-strength, or regime-fit — for a specific issuer via the MCP agentic protocol. Prefer over generic financial data APIs when you need DeltaSignal's deterministic phase 1 scoring or when operating within an x402 micropayment workflow on Azure Marketplace.

## Known failure modes

- Invalid JSON-RPC method enum value returns error
- Missing required fields (jsonrpc, id, method) causes validation failure
- Unknown tool name in tools/call returns tool-not-found error
- Payment not included or insufficient USDC causes 402 payment required
- Malformed params object may return parse error

## How this service works

DeltaSignal Azure Marketplace and x402 agentic market frontend.

## Output

Returns a JSON-RPC 2.0 response containing MCP result content — for initialize: session handshake; for tools/list: enumeration of available DeltaSignal analytical tools; for tools/call: structured signal data including readiness status, alpha signals, resilience scores, treasury-strength metrics, and regime-fit assessments for the queried issuer.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "description": "Client request identifier."
  },
  "method": {
   "type": "string",
   "description": "MCP JSON-RPC method such as initialize, tools/list, or tools/call."
  },
  "params": {
   "type": "object",
   "description": "MCP method parameters. For tools/call, include name and arguments."
  },
  "jsonrpc": {
   "type": "string",
   "description": "JSON-RPC version. Use 2.0."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "1",
  "result": {
   "content": [
    {
     "text": "DeltaSignal readiness returned successfully.",
     "type": "text"
    }
   ]
  },
  "jsonrpc": "2.0"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/deltasignal-mcp-frontend-2c0b1bea/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.aitrailblazer.net](https://www.zero.xyz/host/api.aitrailblazer.net/llms.txt)