_ registry / mcp http-sse · checked 2m ago

labelhead-artist-momentum

https://labelhead-mcp-public-production.up.railway.app

Registry code: b89cd5a485c2fda8

api record

Trending hip-hop artist momentum scores across four cultural dimensions.

from a public catalogue that lists it, not from the operator

endpoint
https://labelhead-mcp-public-production.up.railway.app/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 labelhead-artist-momentum live?
Yes — it answered the hub's last check (checked 2m ago). It answered 100% of checks over the last 30 days.
Is labelhead-artist-momentum free to use?
Yes — the hub reached it with no key and no payment.
What tools does labelhead-artist-momentum have?
3 tools: check_artist_momentum, get_scoring_explainer, get_trending_artists.
Is labelhead-artist-momentum 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
live
uptime, 30 days
99.5%

90 days 99.1%· all time 99.1%

latency
209ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 318 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get trending hip-hop artists
  • check an artist's momentum score
  • explain the artist scoring method
takes → gives
text → data
tools
3 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 3 tools
2 open 1 never probed 2 of 3 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_scoring_explainer reads open 14h ago

    Returns a detailed explanation of LabelHead's three-dimensional artist scoring methodology. Use this when you need to understand how composite scores are calculated, what each dimension measures, and how to interpret momentum labels.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_trending_artists reads open 14h ago

    Returns the current list of trending hip-hop and rap artists ranked by LabelHead's composite momentum score. Each artist is scored across three dimensions: Acceleration (30-day streaming/social velocity), Cultural Gravity (press velocity, playlist adds, sync placements), and Longevity (catalog depth and retention). Use this to identify which artists are building genuine momentum right now.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "number",
          "default": 10,
          "maximum": 10,
          "minimum": 1,
          "description": "Number of artists to return (max 10, default 10)"
        },
        "min_composite": {
          "type": "number",
          "maximum": 100,
          "minimum": 0,
          "description": "Minimum composite score filter (0–100)"
        },
        "momentum_label": {
          "enum": [
            "Rising",
            "Steady",
            "Cooling",
            "Breakout"
          ],
          "type": "string",
          "description": "Filter by momentum label"
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • check_artist_momentum reads unknown 14h ago

    Look up the current momentum score and signals for a specific artist by name. Returns the full three-dimensional score breakdown and notable signals driving their momentum.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "artist_name"
      ],
      "properties": {
        "artist_name": {
          "type": "string",
          "description": "Artist name to look up (e.g. 'Doechii', 'Kendrick Lamar', 'GloRilla')"
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 b89cd5a485c2fda8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b89cd5a485c2fda8/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/b89cd5a485c2fda8/badge.svg)](https://brick.blue/agent/b89cd5a485c2fda8?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
70%

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.