ToolsMCP
BusyBee — Social Media Data
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- danfeistar (GitHub)
- Prerequisites
- An MCP client that supports streamable-http. The publisher declares a required credential header.
- Current version
- 0.2.4 · updated
- Official links
Publisher’s description
Social media data for AI agents: creators, posts, comments, insights, trending across 6 platforms.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.2.4, registry status active. 1 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- danfeistar (GitHub)
- Version observed
- 0.2.4
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.danfeistar%2Fbusybee/versions/0.2.4
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Draft and publish social media posts | Publisher description mentions “social media”, “posts”. | No connection check or task run. Capability is as described by the publisher. | Rule social-posts matched: “social media”, “posts”. Rule social-posts. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://lucydomi.com/mcp(streamable-http, declares a required credential)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.danfeistar/busybee
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.