Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Talking Heads on Markets

REMOTE · WWW.HEADGE.COM

Source-backed market views by talking head, topic, ticker, and horizon, with original links.

Available components

−23 this week 0 Trust /100

Last scanned (11 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 3 Nov 2026.

Category Finance and Payments

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (7)

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 yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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 →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • TLS certificate hostname

    Registry says
    https://www.headge.com/mcp
    Package shows
    Certificate names *.up.railway.app, up.railway.app

    The certificate does not name the host we connected to. See the evidence →

Changelog

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.

  • 10 Nov 26 −5

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 9 Nov 26 −4

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 8 Nov 26 −5

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 7 Nov 26 −4

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 6 Nov 26 −5
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 0
    • Endpoint reachability: not serving MCP → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
  • 2 Nov 26 −53
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 30 Oct 26 −7
    • Authorization: partial → unverified ▼ security
Diagnostics

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 10 Nov 2026 · Probed https://www.headge.com/mcp

TLS invalid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Chain error: Hostname mismatch

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE2,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 618edc56941aa1165ddb080bf9f799eb7c1
SANs: *.up.railway.app, up.railway.app
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 www.headge.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
headge.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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 TLS failed
http (plaintext) http://www.headge.com/mcp HTTPS enforced 301 https://www.headge.com/mcp
MCP tools · 9 exposed · ~585 tokens

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 →

Tool Tokens
get_analyst ~37

Current attributed views and catch-up for one talking head, by slug (for example lyn-alden).

NameTypeReqDescription
slugstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

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.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_catchup ~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.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_instrument ~34

Attributed views that name this ticker, plus related views labelled as Headge's mapping.

NameTypeReqDescription
tickerstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_latest ~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.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_topic ~35

Current attributed views on one topic in the closed catalog (for example gold, inflation, xlk).

NameTypeReqDescription
slugstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_view ~28

One attributed view by id, with source URL for citation.

NameTypeReqDescription
view_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

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.

NameTypeReqDescription
assetstring––
cohortstring––
conditionsstring––
countinteger––
directionstring––
horizoninteger––
magnitude–––
referencestring––
sinceinteger––
tolerancenumber––
windowinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

search ~25

Resolve a query to analysts, topics, and instruments.

NameTypeReqDescription
qstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http strickland84-talking-heads-on-markets 'https://www.headge.com/mcp'
Common questions

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).

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?

Its publisher declares no required credentials for Talking Heads on Markets. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Talking Heads on Markets MCP server still maintained?

Talking Heads on Markets has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.