name: caido description: "Connect to a Caido MCP instance for proxy traffic inspection and request comparison."
Caido
Use this when a bug bounty task needs Caido MCP traffic, project history, request inspection, or request comparison.
If Ryushe says "look at the request my proxy resolves to localhost from that runtime.
For replaying a known request shape, do not require Caido MCP by default. Prefer direct HTTP replay with curl, httpx, or a focused script. Use the agent's local MCP/proxy replay only when direct replay fails because the server expects browser/proxy-like behavior, such as Cloudflare/bot challenges, TLS/header fingerprint issues, browser-only flow state, or missing JS-generated tokens.
MCP URL
Default to:
http://localhost:3333/mcp
If the user gives a hostname or IP address, use:
http://<hostname-or-ip>:3333/mcp
If the user gives a full URL, use that exact URL.
Workflow
- Resolve the MCP URL from the user's request.
- Check connectivity before assuming Caido is available.
- If the task mentions PwnFox, a colored browser/profile/session, or a phrase
like "Red session", load
/pwnfoxand filter history byX-PwnFox-Color: <color>. - If unreachable, report whether it looks like host, firewall, bind-address, or port exposure trouble.
- For comparisons, keep Caido projects isolated and compare equivalent workflows request-by-request.
- For one live owned-session request capture or intercept/modify testing, route to
/single-request-grabberafter Caido connectivity is confirmed. - For live browser exploration, route to
/chromium-test; the browser should attach to the agent's local proxy so browser-generated requests are observable.