{"id":"dnakov-frida-mcp","name":"frida-mcp","homepage":null,"repo_url":"https://github.com/dnakov/frida-mcp","category":"ai-ml","subcategories":[],"tags":["mcp","frida","dynamic-instrumentation","python","stdio-server","ai-agent-tools","reverse-engineering"],"what_it_does":"Provides an MCP (Model Context Protocol) stdio server that exposes Frida dynamic instrumentation capabilities (process/device management, script injection, and an interactive JS REPL) to MCP-compatible AI clients such as Claude Desktop.","use_cases":["Automated dynamic analysis of mobile/desktop apps via Frida","AI-assisted process/device discovery and instrumentation workflows","Interactive JavaScript hooking and interception via an MCP client","Injecting and monitoring custom Frida scripts from an agent workflow","Guided workflows for reverse engineering and runtime inspection"],"not_for":["Production-grade, least-privilege security-sensitive deployments without additional hardening","Environments where users cannot authorize or safely run Frida instrumentation","Use cases requiring a hosted, network-accessible API with built-in auth/rate limiting"],"best_when":"Used locally by trusted operators/agents who need AI-driven control of Frida instrumentation through an MCP-compatible client.","avoid_when":"Avoid in multi-tenant systems or where arbitrary code execution/hooking is not explicitly controlled, since the tool enables powerful runtime instrumentation.","alternatives":["Other Frida control frameworks (non-MCP)","Direct Frida Python/CLI scripting","MCP servers that provide limited, sandboxed instrumentation APIs rather than full REPL/JS execution"],"af_score":59.0,"security_score":24.8,"reliability_score":33.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:35:08.320473+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["None explicitly documented for MCP transport; local stdio server implied"],"oauth":false,"scopes":false,"notes":"No authentication/authorization model is described in the provided README/manifest content; MCP access appears to rely on who can run/connect to the local stdio server."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source MIT package; no pricing model described."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":59.0,"security_score":24.8,"reliability_score":33.8,"mcp_server_quality":80.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":90.0,"rate_limit_clarity":10.0,"tls_enforcement":0.0,"auth_strength":10.0,"scope_granularity":10.0,"dependency_hygiene":55.0,"secret_handling":60.0,"security_notes":"No auth model, authorization, or secret-handling guidance is documented in the provided materials. The tool’s capabilities (interactive JS execution, hooking/interception, process control) substantially increase risk if exposed to untrusted agents/users. Transport appears to be stdio (not TLS-relevant), so security depends on local OS permissions and client access control. Dependency hygiene is partially unknown; declared dependencies are common libraries but no CVE/security posture is provided.","uptime_documented":0.0,"version_stability":55.0,"breaking_changes_history":40.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["This enables powerful instrumentation (process attach/spawn/kill, JS REPL, script injection); agents must treat inputs as high-risk.","Because it is likely a local stdio MCP server, connection lifecycle and process permissions matter (agent must start/stop/handle the server process correctly).","Long-running operations (e.g., script injection/monitoring) may require proper orchestration and timeouts; retry behavior and idempotency are not documented."]}}