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

busybee

https://lucydomi.com

Registry code: a7bcd78f936a815d

api record

BusyBee Data gives you one normalized way to read public social media data.

Pick a platform first (tiktok / instagram / youtube / twitter / douyin / xiaohongshu), then use search_creators to find accounts, search_posts to find content, get_comments + get_comment_insights to understand what audiences say.

endpoint
https://lucydomi.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 busybee live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is busybee free to use?
Yes — the hub reached it with no key and no payment.
What tools does busybee have?
10 tools: search_creators, get_creator, get_post, search_posts, list_creator_posts, get_comments, get_comment_insights, check_balance, ….
Is busybee 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
525ms

last good check

priced tools
0

of 10 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 10 tools
3 open 7 never probed 3 of 10 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.

  • check_balance open 2h ago

    查当前 API Key 的账户信息与余额（美元）。调用前可以先看一眼，避免跑到一半余额不足。

    mcp-tool

    {
  "type": "object",
  "title": "check_balanceArguments",
  "properties": {}
}
    arguments 5 lines
  • get_trending open 2h ago

    拉平台热搜/热榜（目前支持抖音）。适合做选题和热点追踪。

    mcp-tool

    {
  "type": "object",
  "title": "get_trendingArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 20
    },
    "platform": {
      "type": "string",
      "title": "Platform",
      "default": "douyin"
    }
  }
}
    arguments 16 lines
  • list_platforms open 2h ago

    列出可用的平台、每个平台支持哪些操作，以及该怎么选。首次使用先调这个。

    mcp-tool

    {
  "type": "object",
  "title": "list_platformsArguments",
  "properties": {}
}
    arguments 5 lines
  • search_creators unknown never probed

    按关键词搜索社媒账号/达人。返回 id、handle、昵称、粉丝数、简介——拿到 handle 或 id 后再用 get_creator / list_creator_posts 深入。

    mcp-tool

    {
  "type": "object",
  "title": "search_creatorsArguments",
  "required": [
    "platform",
    "keyword"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    },
    "keyword": {
      "type": "string",
      "title": "Keyword"
    },
    "platform": {
      "type": "string",
      "title": "Platform"
    }
  }
}
    arguments 23 lines
  • get_creator unknown never probed

    查单个账号的详情（粉丝数、简介、作品数）。creator 填 handle（如 @nasa 去掉@）或平台 id。

    mcp-tool

    {
  "type": "object",
  "title": "get_creatorArguments",
  "required": [
    "platform",
    "creator"
  ],
  "properties": {
    "creator": {
      "type": "string",
      "title": "Creator"
    },
    "platform": {
      "type": "string",
      "title": "Platform"
    }
  }
}
    arguments 18 lines
  • get_post unknown never probed

    查单条内容的详情。post_id 填平台的内容 id；TikTok/抖音也可传视频链接里的数字 id。

    mcp-tool

    {
  "type": "object",
  "title": "get_postArguments",
  "required": [
    "platform",
    "post_id"
  ],
  "properties": {
    "post_id": {
      "type": "string",
      "title": "Post Id"
    },
    "platform": {
      "type": "string",
      "title": "Platform"
    }
  }
}
    arguments 18 lines
  • search_posts unknown never probed

    搜索内容：给关键词，返回帖子/视频列表（统一字段：作者、文案、时间、点赞/评论/播放）。适合“某个话题最近在火什么”。

    mcp-tool

    {
  "type": "object",
  "title": "search_postsArguments",
  "required": [
    "platform",
    "keyword"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 20
    },
    "keyword": {
      "type": "string",
      "title": "Keyword"
    },
    "platform": {
      "type": "string",
      "title": "Platform"
    }
  }
}
    arguments 23 lines
  • list_creator_posts unknown never probed

    拉某个账号最近发布的作品列表。creator 填 handle 或平台 id。

    mcp-tool

    {
  "type": "object",
  "title": "list_creator_postsArguments",
  "required": [
    "platform",
    "creator"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 20
    },
    "creator": {
      "type": "string",
      "title": "Creator"
    },
    "platform": {
      "type": "string",
      "title": "Platform"
    }
  }
}
    arguments 23 lines
  • get_comments unknown never probed

    拉某条内容的评论列表（统一字段：评论人、内容、点赞、时间）。拿到评论后用 get_comment_insights 出结论。

    mcp-tool

    {
  "type": "object",
  "title": "get_commentsArguments",
  "required": [
    "platform",
    "post_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 20
    },
    "post_id": {
      "type": "string",
      "title": "Post Id"
    },
    "platform": {
      "type": "string",
      "title": "Platform"
    }
  }
}
    arguments 23 lines
  • get_comment_insights unknown never probed

    评论洞察：先拉样本评论再本地聚合，直接给结论——情绪分布、提问占比、高频词、高赞评论。比原始评论更适合回答“用户到底在说什么”。

    mcp-tool

    {
  "type": "object",
  "title": "get_comment_insightsArguments",
  "required": [
    "platform",
    "post_id"
  ],
  "properties": {
    "sample": {
      "type": "integer",
      "title": "Sample",
      "default": 60
    },
    "post_id": {
      "type": "string",
      "title": "Post Id"
    },
    "platform": {
      "type": "string",
      "title": "Platform"
    }
  }
}
    arguments 23 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 a7bcd78f936a815d.

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