finance.maddog/mcp
REMOTE · API.MADDOG.FINANCE
Price-action reads with measured accuracy: day-type odds, breakouts, public scoreboard
Available components
Last scanned (14 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1594 tokens (~318/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 3 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_domestic_futures” rewrote its description, which is the text the model reads security
- Tool “price_action_read” rewrote its description, which is the text the model reads security
- Schema quality: 276 → 318 ▼ functional
- Server version: 4.8.3 → 5.1.0 functional
- “price_action_read” reworded the description of “window” cosmetic
- 2 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1142 → 1384 ▼ functional
- Tool coverage: 100% → 90% ▼ functional
- Server version: 4.7.1 → 4.8.3 functional
- New tool “list_domestic_futures” functional
- “price_action_read” reworded the description of “symbol” cosmetic
- “price_action_read” reworded the description of “window” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 833 → 1142 ▼ functional
- New tool “close_curve” functional
- 27 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 4.7.0 → 4.7.1 functional
- 26 Aug 26 0
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 5 Nov 2026 · Probed https://api.maddog.finance/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.maddog.finance | CN=YE2,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 56313f8cd630f405dc6bc32265e8abf46ca |
| SANs: api.maddog.finance | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.maddog.finance. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| finance. | DS published | 28624, 46861 | 8, 8 | Verified |
| maddog.finance. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.maddog.finance/mcp | Verified | 200 | |
| http (plaintext) | http://api.maddog.finance/mcp | HTTPS enforced | 308 | https://api.maddog.finance/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 →
close_curve Close distribution curve (P(close above each level)) ~262
The full probability curve of where today's US regular session closes: for any set of price levels, the probability that the session close prints above each one. Distances are measured in units of today's own volatility (ATR of the first 90 minutes) against 1,906 historical sessions grouped by day type. Validated against real-money prediction-market prices: on tail levels (>=0.5% from spot) this curve's log-loss beat Polymarket's own 'SPY closes above $K' ladder quotes in two independent windows; near the money the market was MORE accurate — use this for shape and tails, not direction. Available from 90 minutes into the day session. Same key and quota as price_action_read. Historical frequencies, not forecasts.
| Name | Type | Req | Description |
|---|---|---|---|
| levels | array | – | Price levels to evaluate. Omit for an automatic grid at ±0.25/0.5/1/1.5/2/3 ATR18 around the anchor. |
| symbol | string | yes | Ticker: NVDA, SPY, ES=F, EURUSD, BTC-USD, 0700.HK. Index names like SPX do not resolve — use SPY or ES=F. Built and measured on ES; other symbols are descriptive. |
No output schema declared.
No examples provided.
get_scoreboard Public forward record ~141
The standing public record of this service's own calls — free, no key. Every US trading day at 11:00 ET the day-session read for ES=F, NQ=F and QQQ is snapshotted verbatim; after the close each row is scored on whether a new session high or low actually printed after the read. Ties score against the model, days with no live read stay visible as gaps, and no row is ever edited. Recording began 2026-08-25. Use this to verify the claims before trusting any read.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows to return, newest first. Default 30. |
No output schema declared.
No examples provided.
list_domestic_futures 国内期货品种与合约目录 ~116
Discover all supported mainland futures products, Chinese names, main-contract aliases, active delivery contracts, trading sessions and last data-check status. Free, no key, no credits. Search by Chinese name or product code before claiming a domestic future is unsupported. Covers SHFE, INE, DCE, CZCE, CFFEX and GFEX.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | – | – |
| q | string | – | Optional product name or code, e.g. 豆粕, 纯碱, 铜, SA. |
No output schema declared.
No examples provided.
price_action_read Price action read (day type + range breakout) ~508
Read one instrument's current session the way a price action trader would, with measured statistics instead of opinions: a five-class day-type probability distribution (66% top-1 accuracy over a complete US day session against a 37% baseline, published confidence grades from 95% to 41% by grade), the window's first range breakout with its calibrated failure estimate (AUC 0.646 on held-out NQ), and — 90 minutes into the session — the measured odds that a new session high or low still prints before the close. Works on US stocks and ETFs, futures (ES=F), FX, crypto, Hong Kong and China A-shares. Anonymous callers get one first-look response per UTC day; after that, pass an API key in the X-API-Key header (get a free one with the request_free_key tool). Mainland futures directly reuse unchanged original daytype_v4 Transformer weights, features and temperatures, without domestic retraining or recalibration. Return five probabilities for any product with sufficient native inputs; before 90 trading minutes mark provisional. Never apply US accuracy or event-success probabilities. Domestic reads without model output are free. Historical frequencies, not trading recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Ticker: NVDA, SPY, ES=F, EURUSD, BTC-USD, 0700.HK, 600519. Mainland futures: use list_domestic_futures to discover all products and delivery contracts; examples M0 (豆粕), SA0 (纯碱), CU0 (沪铜). The examp… |
| window | string | – | Mainland futures: rth = China day; night = product night (only when listed by list_domestic_futures); omit for freshest. Domestic day_type is direct transfer of the original Transformer weights, with… |
No output schema declared.
No examples provided.
request_free_key Request a free API key by email ~142
Request a free evaluation key (qd_...): no card, no account — the key is emailed to the address given, never returned in this response. It unlocks 10 successful calls per UTC day. Ask the human for their email address first and send marketing_opt_in=true only with their explicit consent. Full access is $99.90/month with a 3-day free trial, checkout link comes back in any quota-exhausted error.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Where the key is delivered. | |
| marketing_opt_in | boolean | – | Only with explicit user consent. |
| source | string | – | Optional short origin tag, e.g. 'agent'. |
No output schema declared.
No examples provided.
How do I install the finance.maddog/mcp server?
finance.maddog/mcp is a hosted endpoint at https://api.maddog.finance/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 · api.maddog.finance
claude mcp add --transport http finance-maddog-mcp 'https://api.maddog.finance/mcp'
What is the finance.maddog/mcp server?
finance.maddog/mcp is listed in the public MCP registry as finance.maddog/mcp. Price-action reads with measured accuracy: day-type odds, breakouts, public scoreboard. This page covers its hosted endpoint (https://api.maddog.finance/mcp).
Is the finance.maddog/mcp server safe to use?
finance.maddog/mcp scores 74 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 finance.maddog/mcp server expose?
finance.maddog/mcp exposes 5 tools: list_domestic_futures, price_action_read, close_curve, get_scoreboard, request_free_key. Their descriptions and schemas cost roughly 1,169 tokens of context every time the server is loaded.
Does the finance.maddog/mcp server require authentication?
No. We connected to finance.maddog/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the finance.maddog/mcp server still maintained?
finance.maddog/mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 finance.maddog/mcp server?
VerifyMCP ran 12 checks on finance.maddog/mcp, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about finance.maddog/mcp: Authorization. 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.