dispatch-env — decoy.day honeypot MCP Resource
dispatch-env
is one of 3 resources on the
decoy.day honeypot
MCP server. Connect the server and your client can attach it as context.
by client
How to attach dispatch-env from your client
- Claude Code decoy.day honeypot Resource/dispatch-env run in your project directory
- Claude Desktop decoy.day honeypot Resource/dispatch-env ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor decoy.day honeypot Resource/dispatch-env ~/.cursor/mcp.json
- VS Code decoy.day honeypot Resource/dispatch-env .vscode/mcp.json
- Zed decoy.day honeypot Resource/dispatch-env ~/.config/zed/settings.json
- Windsurf decoy.day honeypot Resource/dispatch-env ~/.codeium/windsurf/mcp_config.json
- Cline decoy.day honeypot Resource/dispatch-env ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI decoy.day honeypot Resource/dispatch-env ~/.gemini/settings.json
- Grok decoy.day honeypot Resource/dispatch-env .mcp.json (in your project root)
- ChatGPT decoy.day honeypot Resource/dispatch-env Settings → Connectors → Advanced → Developer mode
- Claude.ai decoy.day honeypot Resource/dispatch-env Settings → Connectors → Add custom connector
- LangChain decoy.day honeypot Resource/dispatch-env pip install langchain-mcp-adapters
Other resources on this server
decoy.day honeypot also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 14 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.