Skip to main content
Glama
Signal Feed API: market regime for agents

Signal Feed API: market regime for agents

signal-feed-mcp

MCP server for Signal Feed API: daily market-regime context for trading agents. It answers one question: is the market risk-on or risk-off? Today's issue is paid per call with x402 (0.04 USDC on Base, VAT included). Older issues, the rules and the full results record are free.

One issue per day, the same for every buyer, with five rule-based market-state labels:

  • BTC trend filter (close vs SMA20/50)

  • trend scores for 9 altcoins

  • US equity regime (SPY vs SMA200, VIX/VIX3M term structure)

  • SPY RSI(2) state

  • MSTR BTC filter

Honesty facts. The rules come from the seller's own virtual (PAPER) research accounts. The first issue was 2026-10-26, so there is no track record. This is context, not investment advice. Every issue is hash-committed, OpenTimestamps-anchored and never edited, and the full PAPER results (losses included) are public.

What it does not do

  • It does not place orders, trade or connect to any exchange or broker.

  • It does not predict prices or returns, and it gives no target weights, position sizes or advice.

  • It has no track record yet: the first issue was 2026-10-26.

  • It never asks the seller for a key. The optional wallet key stays in your environment, signs on your machine and is never sent anywhere. The client pays only the offer it has checked (see Payment safety), at most 0.04 USDC per payment and 3 payments per session by default.

  • It does not rewrite issues. A correction is a new dated record.

Related MCP server: Backtesting Arena

Install

Python 3.10+.

pip install signal-feed-mcp
# or run without installing:
uvx signal-feed-mcp

Claude Desktop and other MCPB hosts can also install the one-file bundle (signal-feed-mcp-<version>.mcpb), which runs through uv and asks for the optional wallet key in its settings.

Connect with one command

Needs Python 3.10+ and uv. Every free tool works without a wallet; only get_latest_issue pays.

# Claude Code
claude mcp add --transport stdio signal-feed -- uvx signal-feed-mcp

# Codex CLI
codex mcp add signal-feed -- uvx signal-feed-mcp

Claude Desktop, Cursor and other clients: add a stdio server with command uvx and argument signal-feed-mcp (JSON example below).

Try this first (no payment):

Use the signal-feed tools. Call get_catalog and explain in plain words what each indicator means and how long its value stays valid. Then call get_results_record and tell me what the record shows and what it does not show. Make no paid call.

Configure your MCP client

Claude Desktop, Claude Code, Cursor or any stdio MCP client:

{
  "mcpServers": {
    "signal-feed": {
      "command": "signal-feed-mcp",
      "env": {
        "X402_BUYER_PRIVATE_KEY": "<optional: key of a wallet holding a little USDC on Base>",
        "SIGNAL_FEED_MAX_PAID_CALLS": "3",
        "SIGNAL_FEED_PREFLIGHT": "block"
      }
    }
  }
}

Without X402_BUYER_PRIVATE_KEY every free tool works. Only get_latest_issue is disabled, and it says why. Use a dedicated wallet that holds only what you are willing to spend.

Tools

Tool

Returns

Cost

get_catalog

indicators and their rules, schedule, price, free and paid access

free

get_schema

closed JSON Schema of one issue

free

list_issues

ledger: every issue date with its payload SHA-256

free

get_delayed_issue(issue_date)

an issue at least 7 days old, with its hash recomputed and checked against the issue and the ledger

free

get_results_record(indicator?)

full daily PAPER results of the account behind each indicator, losses included

free

get_deviations

dated bugs, outages and other deviations

free

get_disclosures

the publisher's positions and conflicts

free

get_payment_offer

the live x402 offer, without paying

free

get_latest_issue

today's issue, the receipt, the settlement transaction and the hash check

0.04 USDC

Payment safety

  • Your wallet key is read from this process's environment only. It is used to sign locally with the official x402 client, and it is never logged, returned in tool output or sent anywhere. The seller never sees it.

  • Before signing, the client refuses unless the offer is exactly:

    • scheme exact;

    • network Base mainnet (eip155:8453);

    • asset USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913;

    • amount 40000 (0.04 USDC);

    • for https://signals.agenttrustapi.com/v1/feed/latest;

    • payable to the published merchant 0x8b0ad0CE12Ac86822c4d5dE442F5e445d14F9183 (override with SIGNAL_FEED_EXPECTED_PAY_TO).

  • The x402 client's spend controls are capped at 0.04 USDC per payment.

  • After paying, the receipt hash, the recomputed hash and the hash in the public ledger must all match.

  • Session budget: at most SIGNAL_FEED_MAX_PAID_CALLS payments per server process (default 3). Each payment is counted before it is attempted. A payment refused by the preflight below is not counted.

  • Independent preflight (optional): with SIGNAL_FEED_PREFLIGHT, every payment is first sent to Agent Trust API's payment preflight (POST /v1/preflight/payment, same seller, no charge at the time of writing). It answers ALLOW, REVIEW or BLOCK for that exact payment.

    • What it checks: the x402 offer is consistent, and the payee is bound to the resource. If you give it a signed delegation (SIGNAL_FEED_AUTHORITY_FILE), it also checks that this agent is authorized to make exactly this payment.

    • Modes: block pays on ALLOW or REVIEW and refuses on BLOCK. allow-only pays only on ALLOW.

    • It fails closed: if Agent Trust is unreachable or answers anything unexpected, nothing is signed.

    • What it sends: the agent id, the payment tuple, the 402 offer and the optional delegation. It never sends your key.

    • Scope: it checks the payment, not whether the data will be useful to you. It is not insurance.

Suggested spend policy for any agent buying this feed

  • Pay only https://signals.agenttrustapi.com/v1/feed/latest, only to the published merchant, only USDC on Base.

  • At most 0.04 USDC per issue and 0.08 USDC per day. One new issue a day is enough, and the date is in the offer.

  • Never retry a failed payment blindly. Stop on a non-200 answer or on a duplicate charge, and ask for a refund under the published policy.

Environment

Variable

Default

Meaning

X402_BUYER_PRIVATE_KEY

unset

wallet key for the paid tool (optional)

SIGNAL_FEED_MAX_PAID_CALLS

3

payments allowed per server process

SIGNAL_FEED_EXPECTED_PAY_TO

published merchant

the only payee the client will pay

SIGNAL_FEED_BASE_URL

https://signals.agenttrustapi.com

API base URL

SIGNAL_FEED_PREFLIGHT

off

off, block or allow-only (Agent Trust payment preflight)

SIGNAL_FEED_AUTHORITY_FILE

unset

path to a delegation (authority envelope) JSON for the preflight

SIGNAL_FEED_AGENT_ID

signal-feed-mcp

agent id sent to the preflight

SIGNAL_FEED_PREFLIGHT_URL

Agent Trust production

preflight endpoint

Offers

There is a design-partner refund and a 100 USDC build bounty for open-source agents that use the feed as pre-decision context. Terms: https://signals.agenttrustapi.com/offers.

More

Development

pip install -e ".[dev]"
pytest && ruff check .

The tests run offline against a fake API. They make no network calls and no payments.

License

MIT © 2026 Signal Feed API, Burgas, Bulgaria. Contact: hello@agenttrustapi.com

mcp-name: io.github.DinevDecor/signal-feed-mcp

Available Tools

9 tools
get_catalogA

Free. Use first, when you need to know what the daily regime labels mean before trusting them: indicators and their exact rules, schedule, price, latest and first issue dates, free and paid access, timestamp proofs and the results record.

Inputs: no named parameters. Returns: object

get_delayed_issueA

Free. Use to try the feed before paying, or to backtest your own logic: the issue for a date at least 7 days old (YYYY-MM-DD), with its hash recomputed and compared to the issue's integrity block and to the public ledger.

Inputs: issue_date (required). Returns: object

get_deviationsA

Free. Use to check whether a bad day was a data or system problem: dated bugs, outages, stops and other deviations that affected an indicator's account.

Inputs: no named parameters. Returns: object

get_disclosuresA

Free. Use to check the seller's conflicts of interest: personal positions, affiliate commissions and other conflicts.

Inputs: no named parameters. Returns: object

get_latest_issueA

Paid, 0.04 USDC on Base via x402. Use once a day when you must decide whether markets are risk-on or risk-off before sizing or gating a trade: today's five rule-based regime labels, paid from the wallet configured in this server (optionally checked first by Agent Trust preflight). Returns the issue, the receipt, the settlement transaction and the hash check against the public ledger.

Inputs: no named parameters. Returns: object

get_payment_offerA

Free. Use before paying to see exactly what would be charged: today's x402 offer (price, network, asset, payee) without paying, and whether the paid tool is configured in this server.

Inputs: no named parameters. Returns: object

get_results_recordA

Free. Use when deciding how much weight to give an indicator: full daily PAPER results of the virtual account behind each one (equity, return, benchmark, exposure, flat days, weekly fees and drawdown), losses included. Optional indicator id filter. Not real-money results.

Inputs: indicator. Returns: object

get_schemaA

Free. Use when you must parse or validate an issue safely: the closed JSON Schema of one issue.

Inputs: no named parameters. Returns: object

list_issuesA

Free. Use to see which issue dates exist or to verify an issue you hold: every published date with its payload SHA-256, append-only.

Inputs: no named parameters. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource or action: latest paid issue, delayed free issue, catalog, schema, issue list, results record, deviations, disclosures, and payment offer. The potentially closest pairs, such as get_latest_issue vs. get_delayed_issue and get_catalog vs. get_schema, are explicitly separated by paid/free status, age, and use case.

    Naming Consistency5/5

    All names use snake_case with a predictable verb_noun structure, mostly get_* with one list_issues. The single list verb is semantically appropriate and does not disrupt the pattern.

    Tool Count5/5

    Nine tools is well scoped for a read-only market-signal feed with trust, payment, schema, and historical-verification needs. Each tool has a clear role and the set avoids unnecessary breadth.

    Completeness4/5

    The surface covers the core workflow well: discovery, schema validation, latest paid issue, free delayed issue for testing/backtesting, issue listing, performance results, deviations, disclosures, and payment offer. A minor gap is the lack of a generic paid issue lookup by date for recent dates other than the latest issue.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      AI-powered crypto signal intelligence for 20 assets (BTC, ETH, SOL, etc). 6 scoring dimensions: whale activity, technical analysis, derivatives flow, narrative strength, sentiment, market structure. Market regime detection (TRENDING/RANGING), portfolio optimization, and accuracy tracking. 9 read-only MCP tools. Free via MCP, $0.001 USDC via x402 on Base for REST API.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with real-time financial market intelligence including regime detection, adaptive signals, macro context chains, and cross-market analysis for crypto, US, and Korean stocks.
      91 PyPI
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Real-time crypto momentum signals, 24h BTC forecasts, and market regime data for AI agents. 5 tools: get_signal, get_all_signals, get_forecast, get_market_context, ping. CoinGecko live fallback, optional x402 micropayments.
      -