_ registry / mcp http-sse · checked 13h ago

Talking Heads on Markets

https://www.headge.com

Registry code: 103b380d485e99c3

api record

Headge is a daily catch-up of talking heads.

Every view is one analyst's stated claim on one topic and horizon, source-backed. Mix and sentiment are counts and a mean — not Headge's call. Never invent a view. Never state a Headge house call. Never treat related instruments as the analyst's recommendation. If there is No View, say so.

endpoint
https://www.headge.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Talking Heads on Markets live?
No — it has stopped answering the hub's checks (checked 13h ago). It answered 27% of checks over the last 30 days.
Is Talking Heads on Markets free to use?
Yes — the hub reached it with no key and no payment.
What tools does Talking Heads on Markets have?
9 tools: get_analyst, get_instrument, search, get_topic, get_view, get_catalog, get_latest, model_scenario, ….
Is Talking Heads on Markets safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
retired
uptime, 30 days
27.3%

90 days 65.6%· all time 65.6%

latency
263ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 302 checks · signed record
  • down → retired· fetch failed
  • degraded → down· fetch failed
  • live → degraded· fetch failed
  • down → live
  • degraded → down· HTTP 503
_ what it is for
topic
finance & markets stock & market data
used for
  • get analyst views on a market topic
  • read today's market commentary catch-up
  • get views mentioning a ticker
  • model historical analogues for an asset move
takes → gives
text → data, text
tools
9 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
4 open 5 never probed 4 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_catalog reads open 14d ago

    Analysts, topics, and instruments Headge tracks. Use this to resolve names before other tools.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_latest reads open 13d ago

    Today's placed views (US session day, ET), newest first, split Bullish / Bearish. Neutral sits under the split. Publication day, not forecast horizon.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • model_scenario reads open 13d ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "asset": {
      "type": "string",
      "default": "us"
    },
    "count": {
      "type": "integer",
      "default": 20
    },
    "since": {
      "type": "integer",
      "default": 1926
    },
    "cohort": {
      "type": "string",
      "default": "all"
    },
    "window": {
      "type": "integer",
      "default": 3
    },
    "horizon": {
      "type": "integer",
      "default": 6
    },
    "direction": {
      "type": "string",
      "default": "down"
    },
    "magnitude": {
      "anyOf": [
        {
          "type": "number"
        },
        {
          "type": "null"
        }
      ],
      "default": 20
    },
    "reference": {
      "type": "string",
      "default": ""
    },
    "tolerance": {
      "type": "number",
      "default": 1
    },
    "conditions": {
      "type": "string",
      "default": ""
    }
  },
  "additionalProperties": false
}
    arguments 57 lines
  • get_catchup reads open 13d ago

    Today's catch-up: mix by horizon, new views, flips, and divergence. Mix is a count. Headge has no house view.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_analyst reads unknown 15d ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • get_instrument reads unknown 14d ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • search reads unknown 15d ago

    Resolve a query to analysts, topics, and instruments.

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • get_topic reads unknown 14d ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • get_view reads unknown 15d ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "view_id"
  ],
  "properties": {
    "view_id": {
      "type": "integer"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 103b380d485e99c3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/103b380d485e99c3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/103b380d485e99c3/badge.svg)](https://brick.blue/agent/103b380d485e99c3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.