Regime Card
REMOTE · AGENT.REGIMECARD.COM
Market regime: US risk-on or risk-off? Live score, stress gate. USDC on Base, Polygon, Solana.
Available components
Last scanned (22 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1440 tokens (~180/item across 8 items; 8 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 Management23
- Stability observed for 7 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 20 Nov 26 0
- Schema quality: 1044 → 1440 ▼ functional
- New tool “scorecard” functional
- New tool “sector_leaders” functional
- 19 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 18 Nov 26 0
- Tool “brief” rewrote its description, which is the text the model reads security
- Tool “crypto_regime” rewrote its description, which is the text the model reads security
- Tool “lookup_symbols” rewrote its description, which is the text the model reads security
- Tool “stress_gate” rewrote its description, which is the text the model reads security
- “lookup_symbols” added an optional parameter “symbol” cosmetic
- “lookup_symbols” reworded the description of “symbols” cosmetic
- “lookup_symbols” made “symbols” optional cosmetic
- 16 Nov 26 +1
- Tool “brief” changed its title: Market risk brief: regime, stress gate and what happened next cosmetic
- Tool “crypto_regime” changed its title: Market regime for crypto: how BTC and altcoins did in markets like today's cosmetic
- Tool “live_reading” changed its title: Live market regime: risk-on or risk-off right now cosmetic
- Tool “lookup_symbols” changed its title: Stock and crypto returns by market regime cosmetic
- Tool “stress_gate” changed its title: Market stress gate: credit, volatility, rates cosmetic
5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 15 Nov 26 0
- Tool “brief” rewrote its description, which is the text the model reads security
- Tool “crypto_regime” rewrote its description, which is the text the model reads security
- Tool “live_reading” rewrote its description, which is the text the model reads security
- Tool “lookup_symbols” rewrote its description, which is the text the model reads security
- Tool “sample_reading” rewrote its description, which is the text the model reads security
- Tool “stress_gate” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.1 → 1.0.2 functional
- Server version: 1.0.0 → 1.0.1 functional
- “lookup_symbols” reworded the description of “symbols” cosmetic
- 14 Nov 26 73
First indexed and scored.
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 21 Nov 2026 · Probed https://agent.regimecard.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=regimecard.com | CN=WE1,O=Google Trust Services,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 6fbb434639ae106f13829acc689001ee |
| SANs: regimecard.com, agent.regimecard.com, *.agent.regimecard.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent.regimecard.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| regimecard.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent.regimecard.com/mcp | Verified | 200 | |
| http (plaintext) | http://agent.regimecard.com/mcp | HTTPS enforced | 301 | https://agent.regimecard.com/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 →
brief Market risk brief: regime, stress gate and what happened next ~137
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.03 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
crypto_regime Market regime for crypto: how BTC and altcoins did in markets like today's ~127
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.05 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
live_reading Live market regime: risk-on or risk-off right now ~169
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_symbols Stock and crypto returns by market regime ~233
How has this stock or crypto typically done in markets like today's? Returns, for one stock or crypto symbol per call (any US stock, plus the covered crypto list), its typical return and how often it rose over 1 to 12 months from the current regime. Stocks add sensitivity versus the S&P 500 and up to 5 peer symbols. A symbol with no price data is free, not covered. $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 one holding.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | One stock or crypto symbol: any US stock, or a coin on the covered crypto list, for example "NVDA" or "BTC". Upper or lower case. One symbol per call. |
| symbols | array | – | The earlier form of the same input: a list with exactly one stock or crypto symbol, for example ["NVDA"]. |
No output schema declared.
No examples provided.
sample_reading Latest settled market regime (free) ~100
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scorecard S&P 500 scorecard: what followed past readings in this regime ~184
What has the S&P 500 done after past readings in this regime? Returns the scorecard row for the regime of the last settled close, as regimecard.com publishes it on its history page: the S&P 500's typical return and how often it rose in the 5 and 20 trading days after past readings in that regime, and a bad outcome as a downside measure. Any of the five regimes can be asked for by key. $0.01 per call in USDC on Base, Polygon or Solana (x402). Updated after each US close. The row follows the last settled close, whose date is asOf. Useful when an agent needs base rates for the S&P 500 in the current market regime.
| Name | Type | Req | Description |
|---|---|---|---|
| regime | string | – | One of the five regimes, by its key. Without it, the regime of the last settled close. |
No output schema declared.
No examples provided.
sector_leaders Sectors and their stocks, ranked by returns in this market regime ~212
Which sectors and stocks have done best and worst in markets like today's? Returns the ten sectors of the regimecard.com stocks page ranked by their stocks' median typical return over 1, 2 or 3 months from the current regime, each with its five highest and five lowest. With one sector named, every stock in it, ranked. It covers the stocks with Regime Card pages. Any other US stock can be checked one at a time with /v1/lookup. $0.05 per call in USDC on Base, Polygon or Solana (x402). One sector: $0.03 per call. Settled figures, updated after each US close: the ones the stock pages on regimecard.com print. Useful when an agent needs sector rotation context for the current market regime.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon | string | – | Without it, 3m. |
| sector | string | – | One sector: all its covered stocks, ranked, at the one-sector price. Without it, every sector. |
No output schema declared.
No examples provided.
stress_gate Market stress gate: credit, volatility, rates ~151
Is it time to reduce risk or hedge? Credit, volatility and rate stress in one call. Returns the Regime Card stress gate: the overall state (Calm, Elevated or Stressed), how many of its three components are confirmed (N of 3), and the state of each component (Credit, Volatility, Rates: Clear or Confirmed). The levels behind the states stay private. $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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Regime Card MCP server?
Regime Card is a hosted endpoint at https://agent.regimecard.com/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 · agent.regimecard.com
claude mcp add --transport http com-regimecard-market-regime 'https://agent.regimecard.com/mcp'
What is the Regime Card MCP server?
Regime Card is an MCP server listed in the public MCP registry as com.regimecard/market-regime. Market regime: US risk-on or risk-off? Live score, stress gate. USDC on Base, Polygon, Solana. This page covers its hosted endpoint (https://agent.regimecard.com/mcp).
Is the Regime Card MCP server safe to use?
Regime Card scores 75 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 Regime Card MCP server expose?
Regime Card exposes 8 tools: sample_reading, live_reading, stress_gate, lookup_symbols, crypto_regime, and 3 more. Their descriptions and schemas cost roughly 1,313 tokens of context every time the server is loaded.
Does the Regime Card MCP server require authentication?
No. We connected to Regime Card without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Regime Card MCP server still maintained?
Regime Card is still listed as active in the MCP registry. We last reached this channel on 21 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 Regime Card MCP server?
VerifyMCP ran 13 checks on Regime Card, 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.