_ registry / mcp http-sse · checked 37m ago

com.regimecard/market-regime

https://agent.regimecard.com

Registry code: 0605d0b69d73de14

api record

Regime Card describes US market conditions: a score from 0 (most risk-off) to 100 (most risk-on), one of five regimes, a stress gate, and how stocks and coins have typically done in the current regime. Start with the free sample. Paid calls cost a few cents in USDC over x402 and return data only after the payment settles. Every response says whether it is live or settled. It describes conditions and is not investment advice.

endpoint
https://agent.regimecard.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is com.regimecard/market-regime live?
Yes — it answered the hub's last check (checked 37m ago). It answered 100% of checks over the last 30 days.
Is com.regimecard/market-regime free to use?
No — it charges per call, from 0.01 USDC, quoted in its own 402 answers.
What tools does com.regimecard/market-regime have?
6 tools: live_reading, brief, crypto_regime, sample_reading, stress_gate, lookup_symbols.
Is com.regimecard/market-regime 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
561ms

last good check

priced tools
6

of 6 tools

_ answered our checks, 90 days 1 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 also stands behind 1 other origin: the chain figures are the gateway's, not this listing's alone. 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
2

distinct

settlements
2

last 2026-11-15

received on chain
0.02 USDC

counted from three payers (thin, concentrated, shared-payto)

_ what it can do 6 tools
6 paid 6 of 6 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.

  • live_reading 0.01 USDC paid 37m ago

    Is the US market risk-on or risk-off right now? Returns the live Regime Card reading: a score from 0 (most risk-off) to 100 (most risk-on) and one of five market regimes, from Risk-Off to Risk-On, built from eight cross-asset signals, beside the last settled close. $0.01 per call in USDC on Base, Polygon or Solana (x402). Recomputed hourly during the US session (10:00 AM to 4:00 PM ET) and marked "live". Outside the session it returns the settled reading, marked "settled". Useful when an agent needs a market sentiment or market conditions check for today, or a fear and greed alternative that reads credit, volatility, rates, currencies, commodities and sectors.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • brief 0.01 USDC paid 37m ago

    What is the stock market today, in one call? Returns the live market regime reading, the stress gate, and the scorecard row for the current regime: what the S&P 500 did in the 5 and 20 trading days after past readings in this regime (typical return, how often it rose, a bad outcome as a drawdown risk measure). A cross-asset macro signal. $0.01 per call in USDC on Base, Polygon or Solana (x402). Recomputed hourly during the US session. Useful when an agent wants one reading as a risk check before a trade or as a position sizing input.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • crypto_regime 0.01 USDC paid 37m ago

    Is crypto risk-on or risk-off, and what does bitcoin risk look like in markets like today's? Returns the current crypto market regime and each covered coin's typical return and how often it rose over 1, 2 and 3 months when the period started in this regime, as historical odds. $0.01 per call in USDC on Base, Polygon or Solana (x402). Regime updates after each US close, coins once a day. Useful when an agent needs the market regime for crypto across BTC and altcoins. Covers altcoin risk as well as bitcoin.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • sample_reading paid never probed

    What was the US market regime at the last close? Returns the newest settled Regime Card reading, the same one regimecard.com shows: a score from 0 to 100, one of five regimes, the eight cross-asset category labels, and the paid routes with their prices. Free. One reading per US trading day, settled at 4:30 PM ET. Useful as a free first look at the response shape and the paid routes.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • stress_gate paid never probed

    Is there market stress right now in credit, volatility or rates? Returns the Regime Card stress gate in one call: Calm, Elevated or Stressed, how many of its three components are confirmed (N of 3), and each component (Credit, Volatility, Rates) as Clear or Confirmed. States only, never the levels behind them. $0.01 per call in USDC on Base, Polygon or Solana (x402). Recomputed hourly during the US session. "stale" is true when a scheduled update is missing. Useful when an agent needs a market stress or market risk check on credit, volatility and rates before it acts.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • lookup_symbols paid never probed

    How has this stock or crypto typically done in markets like today's? Returns, for up to 20 stock or crypto symbols, each one's typical return and how often it rose over 1 to 12 months when the period started in the current regime, as historical odds. A symbol outside coverage comes back as not covered, never as an error. $0.01 per call in USDC on Base, Polygon or Solana (x402). Settled figures, updated after each US close (coins daily). The same figures as the symbol's page on regimecard.com. Useful when an agent needs stock returns by market regime or crypto returns by market regime for a watchlist or a portfolio.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "symbols"
      ],
      "properties": {
        "symbols": {
          "type": "array",
          "items": {
            "type": "string",
            "examples": [
              "NVDA",
              "XLK",
              "BTC"
            ],
            "maxLength": 10,
            "minLength": 1,
            "description": "One stock, ETF or crypto symbol."
          },
          "examples": [
            [
              "NVDA",
              "BTC",
              "ZZZZ"
            ]
          ],
          "maxItems": 20,
          "minItems": 1,
          "description": "Stock or crypto symbols, for example [\"NVDA\", \"XLK\", \"BTC\"]. At most 20. Upper or lower case. Repeats are answered once."
        }
      }
    }
    arguments 33 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 0605d0b69d73de14.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0605d0b69d73de14/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/0605d0b69d73de14/badge.svg)](https://brick.blue/agent/0605d0b69d73de14?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.