finance.maddog/mcp
REMOTE · API.MADDOG.FINANCE · SCANNED SEP 20
Price-action reads with measured accuracy: day-type odds, breakouts, public scoreboard
Available components
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 4 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1142 tokens (~285/item across 4 items; 4 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 Management83
- Stability observed for 25 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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'
{
"mcpServers": {
"finance-maddog-mcp": {
"url": "https://api.maddog.finance/mcp"
}
}
} {
"servers": {
"finance-maddog-mcp": {
"type": "http",
"url": "https://api.maddog.finance/mcp"
}
}
} [mcp_servers.finance-maddog-mcp] url = "https://api.maddog.finance/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"finance-maddog-mcp": {
"type": "remote",
"url": "https://api.maddog.finance/mcp",
"enabled": true
}
}
} openclaw mcp add finance-maddog-mcp --url 'https://api.maddog.finance/mcp' --transport streamable-http
mcp_servers:
finance-maddog-mcp:
url: "https://api.maddog.finance/mcp" {
"McpServers": {
"finance-maddog-mcp": {
"Transport": "http",
"Url": "https://api.maddog.finance/mcp"
}
}
} assistant mcp add finance-maddog-mcp -t streamable-http -u 'https://api.maddog.finance/mcp'
{
"mcpServers": {
"finance-maddog-mcp": {
"type": "http",
"url": "https://api.maddog.finance/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 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. | present | 28624 | 8 | Verified |
| maddog.finance. | absent | 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.
price_action_read Price action read (day type + range breakout) ~295
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). Historical frequencies, not forecasts.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Ticker: NVDA, SPY, ES=F, EURUSD, BTC-USD, 0700.HK, 600519. Index names like SPX do not resolve — use SPY or ES=F. |
| window | string | – | Omit to follow the freshest bars. rth = US day session; asia = 09:00-16:00 Beijing; gap = the Asia-close-to-US-open stretch. gap/asia are for 24-hour instruments only. |
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.
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 73 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 4 tools: price_action_read, close_curve, get_scoreboard, request_free_key. Their descriptions and schemas cost roughly 840 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.