BusyBee — Social Media Data
REMOTE · LUCYDOMI.COM
Social media data for AI agents: creators, posts, comments, insights, trending across 6 platforms.
Available components
Last scanned (21 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 4 Nov 2026.
Category News and Social
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 −26
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- 23 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://lucydomi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lucydomi.com | CN=YE2,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5d512357f0bbd4b5e848a455630d7c94be1 |
| SANs: *.lucydomi.com, lucydomi.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lucydomi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lucydomi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="busybee"
Bearer realm="busybee"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=() |
| www-authenticate | Bearer realm="busybee" |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lucydomi.com/mcp | Auth required | 401 | |
| http (plaintext) | http://lucydomi.com/mcp | HTTPS enforced | 301 | https://lucydomi.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_balance ~36
查当前 API Key 的账户信息与余额（美元）。调用前可以先看一眼，避免跑到一半余额不足。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_comment_insights ~84
评论洞察：先拉样本评论再本地聚合，直接给结论——情绪分布、提问占比、高频词、高赞评论。比原始评论更适合回答“用户到底在说什么”。
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | – |
| post_id | string | yes | – |
| sample | integer | – | – |
No output schema declared.
No examples provided.
get_comments ~63
拉某条内容的评论列表（统一字段：评论人、内容、点赞、时间）。拿到评论后用 get_comment_insights 出结论。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| platform | string | yes | – |
| post_id | string | yes | – |
No output schema declared.
No examples provided.
get_creator ~55
查单个账号的详情（粉丝数、简介、作品数）。creator 填 handle（如 @nasa 去掉@）或平台 id。
| Name | Type | Req | Description |
|---|---|---|---|
| creator | string | yes | – |
| platform | string | yes | – |
No output schema declared.
No examples provided.
get_post ~54
查单条内容的详情。post_id 填平台的内容 id；TikTok/抖音也可传视频链接里的数字 id。
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | – |
| post_id | string | yes | – |
No output schema declared.
No examples provided.
get_trending ~47
拉平台热搜/热榜（目前支持抖音）。适合做选题和热点追踪。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| platform | string | – | – |
No output schema declared.
No examples provided.
list_creator_posts ~48
拉某个账号最近发布的作品列表。creator 填 handle 或平台 id。
| Name | Type | Req | Description |
|---|---|---|---|
| creator | string | yes | – |
| limit | integer | – | – |
| platform | string | yes | – |
No output schema declared.
No examples provided.
list_platforms ~32
列出可用的平台、每个平台支持哪些操作，以及该怎么选。首次使用先调这个。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_creators ~70
按关键词搜索社媒账号/达人。返回 id、handle、昵称、粉丝数、简介——拿到 handle 或 id 后再用 get_creator / list_creator_posts 深入。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
| limit | integer | – | – |
| platform | string | yes | – |
No output schema declared.
No examples provided.
search_posts ~71
搜索内容：给关键词，返回帖子/视频列表（统一字段：作者、文案、时间、点赞/评论/播放）。适合“某个话题最近在火什么”。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
| limit | integer | – | – |
| platform | string | yes | – |
No output schema declared.
No examples provided.
How do I install the BusyBee — Social Media Data MCP server?
BusyBee — Social Media Data is a hosted endpoint at https://lucydomi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · lucydomi.com
claude mcp add --transport http danfeistar-busybee 'https://lucydomi.com/mcp'
What is the BusyBee — Social Media Data MCP server?
BusyBee — Social Media Data is an MCP server listed in the public MCP registry as io.github.danfeistar/busybee. Social media data for AI agents: creators, posts, comments, insights, trending across 6 platforms. This page covers its hosted endpoint (https://lucydomi.com/mcp).
Is the BusyBee — Social Media Data MCP server safe to use?
BusyBee — Social Media Data scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BusyBee — Social Media Data MCP server expose?
BusyBee — Social Media Data exposes 10 tools: list_platforms, search_creators, search_posts, get_creator, list_creator_posts, and 5 more. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.
Does the BusyBee — Social Media Data MCP server require authentication?
Yes. BusyBee — Social Media Data asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the BusyBee — Social Media Data MCP server still maintained?
BusyBee — Social Media Data is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.