Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ConAcademy/buttplug-mcpInstalling this writes the configuration, not the program: `/opt/homebrew/bin/buttplug-mcp` has to be on your PATH already, or the server will not start.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/conacademy/buttplug-mcp/buttplug)<a href="https://agentmods.dev/mcp/conacademy/buttplug-mcp/buttplug"><img src="https://agentmods.dev/badge/mcp/conacademy/buttplug-mcp/buttplug/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/conacademy/buttplug-mcp/buttplug"><img src="https://agentmods.dev/badge/mcp/conacademy/buttplug-mcp/buttplug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
buttplug scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"buttplug": {
"command": "/opt/homebrew/bin/buttplug-mcp",
"args": [
"--ws-port",
"12345"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A f30ca7d1de7e
buttplug is an MCP server published in the GitHub repository ConAcademy/buttplug-mcp (136 stars, last pushed 1y ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
camera-mcp-server
MCP server "camera-mcp-server" as configured in ChenLaoshiYF/yunleng. Runs locally from the camera-mcp-server Python package.
tactus
A content-agnostic MCP server that exposes intimate hardware control to AI agents by wrapping Buttplug/Intiface. Runs locally from the tactus-mcp npm package. Needs 2 environment variables to run.
androidtvmcp
Android TV Remote Control to MCP Bridge. Runs locally from the androidtvmcp Python package.
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package. Needs 1 environment variable to run.
unifi-access-mcp
UniFi Access MCP Server. Runs locally from the unifi-access-mcp Python package. Needs 6 environment variables to run.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.2). Needs 6 environment variables to run.