_ registry / mcp streamable-http · checked 53m ago

signal-api

https://signal-api.shicoars.workers.dev

Registry code: 13bf6ed7aacbe6ab

api record

signal-api sells daily crypto trend signals, market regimes and calculated indicators over x402. Start with the free tools: list_assets discovers supported assets/prices, get_catalog returns the full product list and get_sample returns a 1-day-delayed BTC/ETH trend+regime sample (60 calls/hour per IP). Paid tools return a PaymentRequired result (isError=true, structuredContent.x402Version=2) when no x402 payment is attached. Prices: get_signal $0.01 USDC; get_market_scan $0.05 USDC; get_trend, get_regime and get_indicators $0.005 USDC per call. Network and payTo are in the 402 accepts array.…

endpoint
https://signal-api.shicoars.workers.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is signal-api live?
Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
Is signal-api free to use?
No — it charges per call, from 0.05 USDC, quoted in its own 402 answers.
What tools does signal-api have?
8 tools: get_regime, get_indicators, get_signal, list_assets, get_catalog, get_sample, get_trend, get_market_scan.
Is signal-api safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
512ms

last good check

priced tools
1

of 8 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 84 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
8

distinct

settlements
82

last 2026-11-10

received on chain
5.455 USDC

concentrated

_ what it can do 8 tools
1 paid 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_market_scan 0.05 USDC paid 53m ago

    One call to see what is strong/weak now: every catalog asset with trend, regime, RSI14, 7d/30d returns and distance to the 30d high/low, plus top-5 most bullish/bearish, RSI overbought/oversold and regime counts. Paid: $0.05 USDC per call via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_regime unknown 27h ago

    Get the market regime for one crypto asset: trend (bullish/bearish/lateral), volatility (low/medium/high/unknown), SMA50 slope, 30-day volatility, close and dates. Use when you need a regime/volatility classification rather than a trade signal. Paid: $0.005 USDC per call via x402. Discover valid assets with list_assets.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "Asset id or symbol, e.g. BTC, ETH, SOL, or regime-btc. Use list_assets to discover supported values."
    }
  }
}
    arguments 13 lines
  • get_indicators unknown 27h ago

    Get calculated daily indicators for one crypto asset: RSI14, MACD(12,26,9), ATR14 absolute and percent, Bollinger(20,2) with %B, returns 7d/30d, 30d/90d highs and lows, and the price distance to each level. Returns only calculated values, never raw candles. Use when you need technical context or mean-reversion/volatility levels. Paid: $0.005 USDC per call via x402. Discover assets with list_assets.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "Asset id or symbol, e.g. BTC, ETH, SOL, or indicators-btc. Use list_assets to discover supported values."
    }
  }
}
    arguments 13 lines
  • get_signal unknown never probed

    Get the combined daily trend signal for the default basket (BTC + ETH): signal (LONG/FLAT), exposure, SMA50, 30-day volatility, close and dates. Use when you need the overall market stance. Paid: $0.01 USDC per call via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • list_assets unknown never probed

    List supported crypto assets and product ids for signal-api. Use this first to discover valid `asset` values for get_trend/get_regime and to see prices. Free.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_catalog unknown never probed

    Return the full signal-api catalog: active products, types, params, prices and descriptions. Use when you need the complete product list or metadata. Free.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_sample unknown 53m ago

    Get a free sample of the last completed daily trend and regime for BTC or ETH. The sample is delayed by one day: today's live data and the other assets are paid. Free, limited to 60 calls/hour per IP.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "Asset symbol. Only BTC and ETH are available for free samples."
    }
  }
}
    arguments 13 lines
  • get_trend unknown 53m ago

    Get the daily trend signal for one crypto asset: signal (LONG/FLAT), exposure, SMA50, 30-day volatility, close and dates. Use when you need a directional/exposure view for a specific asset. Paid: $0.005 USDC per call via x402. Discover valid assets with list_assets.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "Asset id or symbol, e.g. BTC, ETH, SOL, or trend-btc. Use list_assets to discover supported values."
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 13bf6ed7aacbe6ab.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/13bf6ed7aacbe6ab/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/13bf6ed7aacbe6ab/badge.svg)](https://brick.blue/agent/13bf6ed7aacbe6ab?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.