_ registry / mcp streamable-http · checked 59m ago

losercore-playlist

https://losercoreplaylist.com

Registry code: 008a96b7741bb8db

api record

Public creative metadata and local video-project preparation only. No Spotify audio or song lyrics are supplied. No cloud AI tasks, payments, account data or stored media are exposed. Projects are drafts for the browser workspace, not rendered videos.

endpoint
https://losercoreplaylist.com/mcp
protocol
streamable-http ·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 losercore-playlist live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is losercore-playlist free to use?
Yes — the hub reached it with no key and no payment.
What tools does losercore-playlist have?
3 tools: get_creation_template, prepare_video_project, search_playlist.
Is losercore-playlist 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
100%

90 days 100%· all time 100%

latency
934ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
1 open 2 never probed 1 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.

  • search_playlist open 59m ago

    Search four starter tracks by song, artist or mood. This is a dated starter selection, not a live or complete Spotify catalogue. Returns metadata and listening links only.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 4,
          "maximum": 12,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "default": "",
          "maxLength": 120
        }
      }
    }
    arguments 17 lines
  • get_creation_template unknown 59m ago

    Return one of two original adult-character scene prompts for a PS2-inspired concept. This prepares text only and never submits or charges an AI generation request.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "template"
      ],
      "properties": {
        "template": {
          "enum": [
            "beanie-loser",
            "turn-on-the-playlist"
          ],
          "type": "string"
        }
      }
    }
    arguments 16 lines
  • prepare_video_project unknown 59m ago

    Prepare a free local-workspace JSON draft from 1–12 song/artist title cards and three original captions. Save the project field as JSON, then import it on the linked workspace. It does not render a video, fetch audio or provide song lyrics.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tracks"
      ],
      "properties": {
        "tracks": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "title",
              "artist"
            ],
            "properties": {
              "title": {
                "type": "string",
                "maxLength": 240,
                "minLength": 1
              },
              "artist": {
                "type": "string",
                "maxLength": 240,
                "minLength": 1
              }
            }
          },
          "maxItems": 12,
          "minItems": 1
        },
        "captions": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 200,
            "minLength": 1
          },
          "default": [
            "online again, emotionally buffering",
            "the room is quiet / the playlist is not",
            "one more track before sleep"
          ],
          "maxItems": 3,
          "minItems": 3
        },
        "language": {
          "enum": [
            "en",
            "id",
            "zh",
            "ja"
          ],
          "type": "string",
          "default": "en"
        }
      }
    }
    arguments 58 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 008a96b7741bb8db.

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