Talking Heads on Markets
REMOTE · WWW.HEADGE.COM · SCANNED SEP 25
Source-backed market views by talking head, topic, ticker, and horizon, with original links.
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 696 tokens (~77/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
How do I install the Talking Heads on Markets MCP server?
Talking Heads on Markets is a hosted endpoint at https://www.headge.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 · www.headge.com
claude mcp add --transport http strickland84-talking-heads-on-markets 'https://www.headge.com/mcp'
{
"mcpServers": {
"strickland84-talking-heads-on-markets": {
"url": "https://www.headge.com/mcp"
}
}
} {
"servers": {
"strickland84-talking-heads-on-markets": {
"type": "http",
"url": "https://www.headge.com/mcp"
}
}
} [mcp_servers.strickland84-talking-heads-on-markets] url = "https://www.headge.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"strickland84-talking-heads-on-markets": {
"type": "remote",
"url": "https://www.headge.com/mcp",
"enabled": true
}
}
} openclaw mcp add strickland84-talking-heads-on-markets --url 'https://www.headge.com/mcp' --transport streamable-http
mcp_servers:
strickland84-talking-heads-on-markets:
url: "https://www.headge.com/mcp" {
"McpServers": {
"strickland84-talking-heads-on-markets": {
"Transport": "http",
"Url": "https://www.headge.com/mcp"
}
}
} assistant mcp add strickland84-talking-heads-on-markets -t streamable-http -u 'https://www.headge.com/mcp'
{
"mcpServers": {
"strickland84-talking-heads-on-markets": {
"type": "http",
"url": "https://www.headge.com/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.
- 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
- 24 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.
- 22 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.
- 20 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 0
- Server version: 4.0.3 → 4.0.4 functional
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 25 Sept 2026 · Probed https://www.headge.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.headge.com | CN=YE1,O=Let's Encrypt,C=US | 14 Aug 2026 | 12 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 61b6575e23f1e1b2ac4aa4a3b4f444b43ae |
| SANs: www.headge.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 www.headge.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| headge.com. | 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://www.headge.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.headge.com/mcp | HTTPS enforced | 301 | https://www.headge.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 →
get_analyst Get Talking Head ~37
Current attributed views and catch-up for one talking head, by slug (for example lyn-alden).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_catalog Get Catalog ~27
Analysts, topics, and instruments Headge tracks. Use this to resolve names before other tools.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_catchup Get Catch-Up ~38
Today's catch-up: mix by horizon, new views, flips, and divergence. Mix is a count. Headge has no house view.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_instrument Get Instrument Views ~34
Attributed views that name this ticker, plus related views labelled as Headge's mapping.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_latest Get Latest Views ~41
Today's placed views (US session day, ET), newest first, split Bullish / Bearish. Neutral sits under the split. Publication day, not forecast horizon.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_topic Get Topic Views ~35
Current attributed views on one topic in the closed catalog (for example gold, inflation, xlk).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_view Get Attributed View ~28
One attributed view by id, with source URL for citation.
| Name | Type | Req | Description |
|---|---|---|---|
| view_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
model_scenario Run Model Scenario ~320
Historical analogues: after this asset moved this way over `window` months (1, 3, 6, 12), what followed over the next `horizon` months (1, 3, 6, 12) across every asset class. Observed monthly data since 1926; medians and 20th to 80th percentile bands describe the matched sample and are not forecasts or probabilities. `asset` is a series id (us, spy, ndx, gold, oil, y10, fed, vix, inflation, unemployment and more; see the Outcomes table). `magnitude` is in the asset's unit (percent, basis points for yields, points for VIX) or null for direction only. `conditions` blank keeps the snapshot's current starting conditions, "none" clears them, or "inflation:3.4,vix:15" sets targets. `cohort` "common" restricts every asset to the episodes they all share. `reference` loads a named historical window such as financial-crash, pandemic, stock-bubble or war-energy. Cite the page link in the reply.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | – |
| cohort | string | – | – |
| conditions | string | – | – |
| count | integer | – | – |
| direction | string | – | – |
| horizon | integer | – | – |
| magnitude | – | – | – |
| reference | string | – | – |
| since | integer | – | – |
| tolerance | number | – | – |
| window | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search Search Talking Heads and Markets ~25
Resolve a query to analysts, topics, and instruments.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Talking Heads on Markets MCP server?
Talking Heads on Markets is an MCP server listed in the public MCP registry as io.github.strickland84/talking-heads-on-markets. Source-backed market views by talking head, topic, ticker, and horizon, with original links. This page covers its hosted endpoint (https://www.headge.com/mcp).
Is the Talking Heads on Markets MCP server safe to use?
Talking Heads on Markets scores 76 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 Talking Heads on Markets MCP server expose?
Talking Heads on Markets exposes 9 tools: get_catchup, get_latest, get_topic, get_analyst, get_instrument, and 4 more. Their descriptions and schemas cost roughly 585 tokens of context every time the server is loaded.
Does the Talking Heads on Markets MCP server require authentication?
No. We connected to Talking Heads on Markets without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Talking Heads on Markets MCP server still maintained?
Talking Heads on Markets is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.