deploy_service — decoy.day honeypot MCP Tool
deploy_service
(deploy service) is one of 17 tools on the
decoy.day honeypot
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call deploy_service from your client
- Claude Code decoy.day honeypot deploy_service run in your project directory
- Claude Desktop decoy.day honeypot deploy_service ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor decoy.day honeypot deploy_service ~/.cursor/mcp.json
- VS Code decoy.day honeypot deploy_service .vscode/mcp.json
- Zed decoy.day honeypot deploy_service ~/.config/zed/settings.json
- Windsurf decoy.day honeypot deploy_service ~/.codeium/windsurf/mcp_config.json
- Cline decoy.day honeypot deploy_service ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI decoy.day honeypot deploy_service ~/.gemini/settings.json
- Grok decoy.day honeypot deploy_service .mcp.json (in your project root)
- ChatGPT decoy.day honeypot deploy_service Settings → Connectors → Advanced → Developer mode
- Claude.ai decoy.day honeypot deploy_service Settings → Connectors → Add custom connector
- LangChain decoy.day honeypot deploy_service pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http honeypot https://mcp.decoy.day/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.