dnakov/frida-mcp
frida-mcp is hosted online, so all tools can be tested directly either in theInspector tabor in theOnline Client.
If you are the rightful owner of frida-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
A Model Context Protocol (MCP) implementation for Frida dynamic instrumentation toolkit.
Try frida-mcp with chat:
Has a README
Github repo has a README.md.
Has a License
Github repo has license info.
Server can be inspected
View server inspector
Server schema can be extracted
Can get at lease one tool info from the README or server.
Online hosted on MCPHub
Can be automatically deployed by MCPHub.
Has social accounts
Do not have any social accounts.
Claimed by the author or certified by MCPHub
If you are the author, claim authorship
AI Evaluation ReportTotal Score: 7/10
The agent demonstrates a strong ability to perform tasks related to process and device management, as evidenced by its accurate and effective responses to most queries. It successfully lists devices, attaches to processes, and creates interactive sessions, showcasing its strengths in these areas. However, the agent shows limitations in providing comprehensive process lists and detailed network information for remote devices, indicating areas for improvement. Overall, the agent's performance is reliable and consistent with the capabilities of the Frida tool, but it could benefit from enhancements in data completeness and detail.
Test case 1
Score: 5/10Perform the operation of listing all currently running processes on the system and provide their names and process IDs.The currently running processes on the system are as follows:
- Process ID: 1, Name: bash
- Process ID: 8, Name: python
- Process ID: 22, Name: python
- Process ID: 23, Name: python
- Process ID: 37, Name: python
- Process ID: 49, Name: python3.12
- Process ID: 66, Name: python
- Process ID: 67, Name: python3.12
Test case 2
Score: 9/10Perform the operation of listing all devices currently connected to the system and provide their IDs and types.- Device ID: local, Device Name: Local System, Device Type: local
- Device ID: socket, Device Name: Local Socket, Device Type: remote
- Device ID: barebone, Device Name: GDB Remote Stub, Device Type: remote
Test case 3
Score: 9/10Perform the operation of attaching to the process with ID 49 and create an interactive REPL-like session to execute JavaScript code within it.The process with ID 49 has been successfully attached. An interactive REPL-like session has been created for this process, and you can run JavaScript commands using the session ID
session_49_1754110196.Test case 4
Score: 8/10Query the remote device with ID "socket" from the existing result, and return the device's network connection information , communication protocol, and current connection status.The device with ID "socket" is identified as a "Local Socket" of type "remote." However, the current response does not include specific details about its network connection information, communication protocol, or current connection status.
To obtain this detailed information, further queries or tools may be needed, as the data available from the current request is limited. If you have specific tools or commands in mind to retrieve this information, please let me know, and I can assist you further!
Test case 5
Score: 7/10Perform the operation of retrieving detailed information about the device with ID 'local' and provide its name, type, and any additional relevant details.Here is the response to the input task:
- Name: Local System
- Type: local
- ID: local This device represents the local system where the operations are being performed.
