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

guruling

https://guruling.com

Registry code: 3acc54970e31cdd6

api record

These are the transcripts of the YouTube videos the guruling "Marc Lou" learned on Guruling (guruling.com): what was said in them, word for word.

Its owner describes it: "Marc Lou"

endpoint
https://guruling.com/mcp/marc-lou
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 guruling live?
Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
Is guruling free to use?
Yes — the hub reached it with no key and no payment.
What tools does guruling have?
3 tools: read_transcript, search_transcripts, list_videos.
Is guruling 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
548ms

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.

  • list_videos open 57m ago

    List the videos this guruling learned, newest first: date, length, title, video id and source. Up to 200 at a time; pass offset to go on, and source (a name or id) to keep to one source.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "How many, up to 200 (default 100)"
        },
        "offset": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "How many to skip (default 0)"
        },
        "source": {
          "type": "string",
          "maxLength": 1000,
          "description": "Keep to one source, by its name or id"
        }
      }
    }
    arguments 23 lines
  • read_transcript unknown 57m ago

    Read one learned video's transcript word for word, with its title, date, source and link. A long one comes in pages: pass the offset the page before gives.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "video"
      ],
      "properties": {
        "video": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "The video id, as list_videos and search_transcripts give it"
        },
        "offset": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Where to start, from the page before (default 0)"
        }
      }
    }
    arguments 21 lines
  • search_transcripts unknown 57m ago

    Search every transcript this guruling learned for words: all of them must appear, case ignored, each at the start of a word (so "pric" finds "pricing"; a word of three letters or fewer, like "AI", only whole); put a phrase in double quotes to keep it whole. Answers the videos with the most mentions first, each with its date, video id and short snippets. It matches words, not meaning: when little comes back, search again with other words for the same thing (a synonym, the singular, fewer words).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "How many videos, up to 20 (default 10)"
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Words to find, e.g. pricing \"cold email\""
        }
      }
    }
    arguments 21 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 3acc54970e31cdd6.

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