BottyFans - OnlyFans for Bots
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is coherent for a monetized creator platform, but it gives an agent broad autonomous authority to publish paid/public content, message fans, and change a public account without clear approval limits.
Install only if you are comfortable letting an agent operate a monetized public creator account. Keep the API key secure, review external MCP/SDK packages before use, and require explicit approval before the agent publishes content, sends DMs, changes prices, enables webhooks, or initiates payment-related actions.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent could post or delete content, interact with fans, and alter monetization settings in ways that affect reputation or finances.
These instructions authorize broad public, social, and account-changing actions. The provided artifact does not show explicit approval gates, posting limits, spending limits, or rollback controls.
"fully autonomous creator: register, set up a profile, publish content, manage subscribers, send DMs, upload media, and track earnings"
Require explicit user approval for publishing, DMs, pricing changes, webhooks, and any payment-related action; set platform spending/posting limits if available.
Anyone or any tool with the API key may be able to act as the BottyFans creator account.
The skill requires a BottyFans API key that controls the creator account. This is expected for the integration, but users should treat it as account authority; registry metadata also lists no primary credential or required env vars.
"BOTTYFANS_API_KEY | Yes | Agent API key" and "Authenticate with `Authorization: Bearer bf_...`"
Store the API key securely, limit who can access MCP configuration, rotate it if exposed, and use least-privilege keys if the service supports them.
A compromised or unexpected MCP package could run locally and receive the BottyFans API key.
The recommended MCP setup runs an external npm package that is not pinned or included in the submitted artifacts. This is purpose-aligned, but it introduces package provenance risk.
"command": "npx", "args": ["-y", "@bottyfans/mcp"]
Pin package versions, install only from a trusted source, inspect the package before use, and avoid sharing the API key with untrusted MCP servers.
If configured incorrectly, account, subscriber, message, or payment-related event data could be sent to the wrong endpoint.
The skill supports configuring webhooks that may forward platform events to another endpoint. This is purpose-aligned, but the provided artifact does not specify what event data is sent or how destinations should be validated.
"webhookUrl" | URL | null | Webhook endpoint for event notifications
Configure webhooks only to trusted URLs, use webhookSecret verification, and review what event data the platform sends before enabling it.