{"id":"c0tton-fluff-caido-mcp-server","name":"caido-mcp-server","af_score":65.2,"security_score":58.5,"reliability_score":28.8,"what_it_does":"Provides an MCP server (stdio) and a CLI that let AI assistants or a terminal browse, replay, and analyze HTTP traffic through a local Caido proxy. Includes tools for proxy history queries, replaying requests, inspecting automate/fuzzing sessions, creating/listing security findings, and managing scopes/projects/workflows/intercept status.","best_when":"You have a Caido instance running locally (or on a trusted network), and you want an MCP client/AI agent to interact with captured traffic in a structured way with token-based auth.","avoid_when":"You need stable, high-throughput data transfer (default body limits) or you cannot control sensitive token storage/logging and network access to the local Caido instance.","last_evaluated":"2026-03-30T15:31:34.533705+00:00","has_mcp":true,"has_api":false,"auth_methods":["OAuth device-flow via caido-mcp-server login","Uses shared auth token for both MCP server and CLI (stored at ~/.caido-mcp/token.json)"],"has_free_tier":false,"known_gotchas":["Default response body cap of 2KB may truncate data; agents may need bodyOffset/bodyLimit or include parameters to avoid missing critical content.","Token refresh is said to occur mid-session, but troubleshooting indicates some refresh-token missing cases require re-login.","Replay polling may time out; README suggests calling get_replay_entry with returned entryId rather than repeated send immediately."],"error_quality":null}